VirtualBox OS X update broke USB drives in Windows 7 VMs
Posted: 2. Sep 2012, 20:43
Hello,
I installed the VirtualBox update 4.1.20 r80170 last night and I can no longer mount external USB drives on my Windows 7 VM.
Host:
- MacBook Pro 15-inch Retina, 2.7 GHz quad core i7, 16GB ram, 768GB drive
- OS X 10.8.1
Guest:
- 2 core, 4GB ram, 100GB dynamically allocated disk
- Windows 7 Ultimate will all current updates
USB Drives that won't mount in Windows 7 VM, but work fine on Mac and on Bootcamp Windows 7 Home Premium boot:
- Cruzer Micro 16GB thumb drive
- Cruzer Micro 32GB thumb drive
- Western Digital My Passport 750GB drive formatted as exFAT with latest firmware installed and SmartWare disabled
- Western Digital My Passport 250GB drive formatted as exFAT with latest firmware installed and SmartWare disabled
The drivers are listed as installed when looking under Computer->Manage->Device Manager, but the device status is "This device cannot start. (Code 10)".
The drives had mounted/worked in the VM just fine prior to the update to 4.1.20.
I saw some similar items in the forums, but none seemed relevant to the 4.1.20 update.
Thanks
Bob Blackard
I installed the VirtualBox update 4.1.20 r80170 last night and I can no longer mount external USB drives on my Windows 7 VM.
Host:
- MacBook Pro 15-inch Retina, 2.7 GHz quad core i7, 16GB ram, 768GB drive
- OS X 10.8.1
Guest:
- 2 core, 4GB ram, 100GB dynamically allocated disk
- Windows 7 Ultimate will all current updates
USB Drives that won't mount in Windows 7 VM, but work fine on Mac and on Bootcamp Windows 7 Home Premium boot:
- Cruzer Micro 16GB thumb drive
- Cruzer Micro 32GB thumb drive
- Western Digital My Passport 750GB drive formatted as exFAT with latest firmware installed and SmartWare disabled
- Western Digital My Passport 250GB drive formatted as exFAT with latest firmware installed and SmartWare disabled
The drivers are listed as installed when looking under Computer->Manage->Device Manager, but the device status is "This device cannot start. (Code 10)".
The drives had mounted/worked in the VM just fine prior to the update to 4.1.20.
I saw some similar items in the forums, but none seemed relevant to the 4.1.20 update.
Thanks
Bob Blackard