Hex-V2 Mac Book windows 10 on windows parallels desktop

[Bracus]

for some reason windows 10 randomly froze and I had to copy it and delete it and reinstall windows 10 on mac book pro through parallels. This has always worked and I’ve even ran into a similar glitch one time before and was able to figure it out. So don’t tell me it can’t be done! lol. Can someone let me know what to do though? When i reinstalled I think I had to delete VCDS from my mac book and reinstall the latest version from ross tech again. When i did this all my info must have been deleted and when i plug into my mac book the light blinks green, then red, then conintues to blink blue light and there is no information in VCDS anymore. When I go to test it says “ross-tech usb interface not found! USB library version 03.02.07 Interface not found”. it doesn’t give the usual options of updating firmware or anything. what am i missing here?

 

[Uwe]

Running VCDS in a VM such as Parallels is explicitly not supported. That doesn't mean it can't or won't work, but it does mean this thread doesn't belong in Product Support, and that Ross-Tech isn't in a position to help you because none of use computers named after fruits that fall from trees and inspire classical physicists.

Since there's no place that this truly fits, I'm moving it to The Bar.

Both LEDs on a HEX-V2 blinking blue means the HEX-V2 has enumerated on the host computer. So if I had to guess, it sounds like Windows in your VM isn't seeing your HEX-V2 when it's plugged in. I have no idea how to fix that. Check your Parallels documentation.

-Uwe-

 

[PetrolDave]

So if I had to guess, it sounds like Windows in your VM isn't seeing your HEX-V2 when it's plugged in. I have no idea how to fix that. Check your Parallels documentation.

I'm an inexperienced MacBook user but I seem to remember reading something that says that USB devices have to be explicitly assigned to the VM otherwise macOS will "own" them.

 

[gawied]

You need to explicitly assign your USB device to your VM, otherwise it will not be seen by your Windows VM.

See screenshot below - it needs to have a tick next to it to be assigned to your VM. If there is no tick next to it, just click on it and it will be assigned to your VM.