VMware Communities
AkiTuomi
Contributor
Contributor
Jump to solution

VMWare USB not recognized

Hi!

Suddenly my computer has started to complain that there is an unrecognized USB device connected. After doing some looking into it, it turns out it is the VMWare USB controller (vmusb.sys). Windows device manager tells me the error code is 43. After digging around, I found something hostd.log (pasted at bottom), which I guess could be related?

There seems to nothing particularly broken with anything. USB devices like mouse & keyboard work on the target host, I can share devices there etc.Would be nice to get rid of this problem though, because it causes USB connect/disconnect events all the time, which I have to had muted out.

Versions:

Windows Version 10.0.19045 Build 19045

VMWare Workstation 15.5.7 build-17171714

Any ideas?

2022-12-12T09:58:17.831+02:00 verbose hostd[14844] [Originator@6876 sub=AdapterServer opID=d68c5fc1 user=MicrosoftAccount\account] New request: target='vmodl.query.PropertyCollector:ha-property-collector', method='waitForUpdatesEx', session='52ceaf3a-99b8-b515-78f5-1160d073416f'
2022-12-12T09:58:17.831+02:00 warning hostd[07320] [Originator@6876 sub=PropertyCollector opID=d68c5fc1 user=MicrosoftAccount\account] Session 52ceaf3a-99b8-b515-78f5-1160d073416f has issued 2 concurrent blocking calls to the property collector. This is almost certainly an error in the logic of the client application.
2022-12-12T10:00:18.272+02:00 verbose hostd[08344] [Originator@6876 sub=Proxy Req 00005] The client closed the stream, not unexpectedly.
2022-12-12T10:00:18.322+02:00 verbose hostd[07312] [Originator@6876 sub=Proxy Req 00006] New proxy client <SSL(<io_obj p:0x06f0a400, h:1912, <TCP '127.0.0.1 : 443'>, <TCP '127.0.0.1 : 50269'>>)>
2022-12-12T10:00:18.322+02:00 verbose hostd[07320] [Originator@6876 sub=Proxy Req 00006] Resolved endpoint : [class Vmacore::Http::LocalServiceSpec:0x06fbeb78] _serverNamespace = /sdk action = Allow _port = 8307
2022-12-12T10:00:18.325+02:00 verbose hostd[07316] [Originator@6876 sub=Proxy Req 00006] Connected to localhost:8307 (/sdk) over <io_obj p:0x06f0b6c0, h:1816, <TCP '::1 : 50270'>, <TCP '::1 : 8307'>>
2022-12-12T10:00:18.327+02:00 verbose hostd[14844] [Originator@6876 sub=AdapterServer opID=d68c5fc2 user=MicrosoftAccount\account] New request: target='vmodl.query.PropertyCollector:ha-property-collector', method='waitForUpdatesEx', session='52ceaf3a-99b8-b515-78f5-1160d073416f'
2022-12-12T10:00:18.327+02:00 warning hostd[07352] [Originator@6876 sub=PropertyCollector opID=d68c5fc2 user=MicrosoftAccount\account] Session 52ceaf3a-99b8-b515-78f5-1160d073416f has issued 3 concurrent blocking calls to the property collector. This is almost certainly an error in the logic of the client application.
2022-12-12T10:01:17.252+02:00 verbose hostd[01376] [Originator@6876 sub=AdapterServer opID=d68c5fc0] IOException while sending the response: class Vmacore::IOException(System exception while trasmitting HTTP Response:
--> error id = 10053
--> )
--> [context]zKq7AUsEAQAAAAIFBgEXaG9zdGQAABgwIHZtYWNvcmUuZGxsAAAc6AUApJUFAD9DAgDxmAoAENUKAIC0CgCPswoAQ9QLAWFAQHZtd2FyZS1ob3N0ZC5leGUAAexCQAK8iwd2bW9taS5kbGwAAs4JCAJedQcCdZIHAjzkBwLjWwYAgMEZAIV5HQOfTwR1Y3J0YmFzZS5kbGwABPn+AUtFUk5FTDMyLkRMTAAFvnsGbnRkbGwuZGxsAAWOewY=[/context]

Reply
0 Kudos
1 Solution

Accepted Solutions
AkiTuomi
Contributor
Contributor
Jump to solution

This problem was resolved after managing to somehow restart hcmon service. The problem was that VMWare Workstation Server service and USB Arbitration Service were not starting. After twiddling with hcmon, I was able to get it started. 

To be honest, I am not 100% sure what it was that solved this issue in the end.

View solution in original post

Reply
0 Kudos
3 Replies
RDPetruska
Leadership
Leadership
Jump to solution

Have you tried doing a Repair on the Workstation application on the host?

Reply
0 Kudos
AkiTuomi
Contributor
Contributor
Jump to solution

Tried that, unfortunately it did not help.

Also, after repair, no USB devices are available for the VM anymore, they are all gone.

Reply
0 Kudos
AkiTuomi
Contributor
Contributor
Jump to solution

This problem was resolved after managing to somehow restart hcmon service. The problem was that VMWare Workstation Server service and USB Arbitration Service were not starting. After twiddling with hcmon, I was able to get it started. 

To be honest, I am not 100% sure what it was that solved this issue in the end.

Reply
0 Kudos