Please see my reply to the original post - this bug was fixed in the latest (4.5.7) version of the Machine Agent, so you could also upgrade to that version. Apologies for the inconvenience.
Hi Jose,
There is a bug in the Machine Agent version 4.5.4 that causes this error on Windows Server 2012 R2 - it was triaged and fixed in the latest version (4.5.7). It appears to be OS-specific, as we were not able to reproduce it on Windows Ser...