It looks like that it should be one vmtoolsd process running w/o any arguments and by the SYSTEM account. Then at login there should autostart another instance of vmtoolsd with "-n vmusr" argument an...
See more...
It looks like that it should be one vmtoolsd process running w/o any arguments and by the SYSTEM account. Then at login there should autostart another instance of vmtoolsd with "-n vmusr" argument and running by the logon user account. In my case this was disabled in the Autostart tab in Task Manager (W10 guest). Alternatively start vmtoolsd -n vmusr in command line after logon.
