Zwave Stick installation broke VM?

I’m running Hass.IO on a VM and everything has been working great. I bought a HUSBZB-1 Zwave and attempted to install the drivers. Windows doesn’t like the drivers but I was able to do this after I disabled driver signature enforcement by followed this guide:(https://www.youtube.com/watch?v=71YAIw7_-kg)

I checked my ports in Device Manager and all looked good - Communication Port (Com1), HUBZ Zigbee Com Port (Com4), HUBZ Z-Wave Com Port (Com3). However when I go to start my VM I get this error:

Failed to open a session for the virtual machine Hass IO .

Failed to open image ‘F:\HassIO.vdi’ for writing due to wrong permissions (VERR_VD_IMAGE_READ_ONLY).

AHCI: Failed to attach drive to Port1 (VERR_VD_IMAGE_READ_ONLY).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

So did my Zwave stick installation mess up Port1? I tried unplugging the stick but get the same VM error. Is there an easy way to fix this? Maybe just making another VM and starting over? I have a snapshot of HA.

Did u get an answer? I’m trying to have Virtualbox 6 on Windows 10 64 bits run the hass.io vdi vm run with HUSBZB-1 but I still get errors, either in Home Assistant or in Virtualbox.
Here is what I tried:

  • in Virtuabox: serial COM3 (zwave) and COM4 (zigbee) ; /dev/ttyUSB0 not accepted (getting error 0x80004005 like u)
  • in HA configuration.yaml:
zwave:
  usb_path: /dev/ttyUSB0
zha:
  usb_path: /dev/ttyUSB1
  database_path: zigbee.db
  radio_type: ezsp
  device_config: !include zigbee.yaml

That was a while ago and I don’t remember how I got it working. I switched from a VM to Ubuntu a while back but went back and looked at my old VM config:

zwave:
  usb_path: /dev/ttyUSB0
  network_key: "0xA4,0x98,0x15,0xP7,0x16,0xXD,0x44,0x90,0xD0,0xZ8,0xAF,0xEE,0x3E,0x48,0x2E,0xAC"
zha:
  usb_path: /dev/ttyUSB1
  database_path: /config/zigbee.db

I wish I could be more help. I think I had to start over with a fresh install. I was only 2 weeks into HA so there probably was an easier way to fix it.

Tks. Will try again and switch to a fresh install if needed.