Virtual crashes Windows when stopping using a device & then blocks/hides USB device on host forever

3 posts / 0 new
Last post
jbattermann
Virtual crashes Windows when stopping using a device & then blocks/hides USB device on host forever

Good morning,

I was trying out VirtualHere on my Windows 11 (physical host/server with USB device connected) and Windows 10 (Virtual Machine client that should be using the Virtual Device) which worked just fine UNTIL I tried stopping the device on the Win10 VM/client.. which caused my Windows 11 host to hard crash and reboot (!!) and now the USB device is no longer listed in the Win11's device manager. I can however still see it in the VM / Win10 Client and re-use it, but again.. when I want to stop using it, Windows 11 / the host crashes.

VirtualHere...
a) keeps crashing my host and
b) blocks the USB device from working on the host and I have NO idea how to get rid of this USB device blocking/hiding mechanism

Calling .\vhusbdwin64.exe -u via and administrative command shell does NOT resolve this, the device in question IS listed (when looking at the hardware a little bit more lower level / HWInfo64 with its driver description still being "VirtualHere USB Server USB Driver".

What the heck? How can this software block my physical device despite NOT being used, crash the system when using the SW as it is supposed to work and NOT come with a working way to get rid of it?

So how DO I get rid of it and get my device back to be used on this / Win11 system?

Thanks,
-Joerg

jbattermann
*VirtualHere (in the title)

*VirtualHere (in the title) obviously, my bad...

Michael
.

Sorry about that, don't worry nothing is wrong with windows or the device, its just hidden because it crashed in the process of uncapture.

Run the virtualhere server from the windows play store instead, use the usb device via virtualhere then stop using. Does that resolve it? Can you see/use the device locally again?

In the meantime ill fix the -u argument to fix this not-properly uncaptured scenario.

Log in or register to post comments