VMware Player Error (Event 34, vmx86)

[chd584]

Hello,

I'm using VMware Player 5.0.2 (build 1031769) on a Windows 7 Professional (64-bit, SP1) workstation to run Windows XP Mode for a legacy USB scanner (HP ScanJet Pro 6200c).

Everything seems to be working fine, but I'd like some feedback on a system warning recorded in the Windows 7 Event Viewer:

Event 34, vmx86

The description for Event ID 34 from source vmx86 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

VMX86.SYS: begin DriverEntry built @ 02:18:19

VMware Player is installed to D:\Program Files (x86)\VMware\VMware Player.

I'm also getting "hcmon" warnings, but it is my understanding that this is due to a current lack of support for USB 3.0 on Windows hosts.

Thanks.

[DmitryBond]

The same problem on Windows 10 Pro with VmWare Workstation 12.1.1 build-3770994.

After mentioned error I also can see following records:

• EvtID=7000 from ServiceControlManager, msg="The vmx86 service failed to start due to the following error: The request is not supported."
• EvtID=7000 from ServiceControlManager, msg="The NetTcpActivator service depends on the NetTcpPortSharing service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it."
• EvtID=7000 from ServiceControlManager, msg="The VMAuthdService service depends on the vmx86 service which failed to start because of the following error: The request is not supported."

Usually after such messages I need to start vmx86 service manually from CMD.

So, for sure there are some problems in vmx86 service. And that is strange that issue was not addressed by VmWare during all this time.

[chrullrich]

It has been "addressed" in the sense that, unlike earlier versions, Workstation 12 will now attempt to start the thing, which leads to an elevation prompt. Before, starting a VM just failed with a helpful error message about the vmauthdservice not running.

Fixing the actual bug would be much better, of course.