sparkyhodgo
Bit poster
Hello, I believe I found a USB bug in Parallels 11.
I have 2012 Retina MacBook Pro running OSX 10.9.5, an NTFS-formatted Seagate Backup Fast external hard drive (USB 3.0), and a Windows 8.1 installation that I have long run in Bootcamp and Parallels. Until two days ago, I used Parallels 8 and everything ran great (even though Parallels 8 didn't even support Windows 8.1!). Just upgraded to Parallels 11 and now that same installation of Windows can't mount the external hard drive anymore. I can mount the drive in OSX just fine, and it will show up in the VM under Network locations, but if I try to connect the drive to the VM, I get is a drive letter but explorer.exe hangs trying to access the drive so I can't actually use it.
I rebooted into Bootcamp and verified that the drive runs perfectly (it does--I even checked for errors and it came up healthy):
You can see everything is A-ok.
But when I try to connect the same external hard drive to the same installation of Windows via Parallels 11, I get this:
In Parallels 11, the drive shows as a generic "local disk" and device manager sees it as a "WPD FileSystem Volume" (yet lists the exact same drivers). Usually it appears like the screenshot above, but sometimes device manager even shows it with the drive name, but then will tell me the drive can't start, error "Code 10", and sometimes it will show an error under Universal Serial Bus controllers. I've tried mounting/unmounting, disabling/reenabling, uninstalling the drive, searching for new drivers, and resetting the VM a dozen times, but no luck establishing a real mount of the drive.
Considering that the drive still works perfectly in Bootcamp, and that Parallels 8 ran the drive great before I upgraded two days ago, I'm pretty sure this is an issue with Parallels 11. Any solutions out there? Or does this need a Parallels patch?
I have 2012 Retina MacBook Pro running OSX 10.9.5, an NTFS-formatted Seagate Backup Fast external hard drive (USB 3.0), and a Windows 8.1 installation that I have long run in Bootcamp and Parallels. Until two days ago, I used Parallels 8 and everything ran great (even though Parallels 8 didn't even support Windows 8.1!). Just upgraded to Parallels 11 and now that same installation of Windows can't mount the external hard drive anymore. I can mount the drive in OSX just fine, and it will show up in the VM under Network locations, but if I try to connect the drive to the VM, I get is a drive letter but explorer.exe hangs trying to access the drive so I can't actually use it.
I rebooted into Bootcamp and verified that the drive runs perfectly (it does--I even checked for errors and it came up healthy):
You can see everything is A-ok.
But when I try to connect the same external hard drive to the same installation of Windows via Parallels 11, I get this:
In Parallels 11, the drive shows as a generic "local disk" and device manager sees it as a "WPD FileSystem Volume" (yet lists the exact same drivers). Usually it appears like the screenshot above, but sometimes device manager even shows it with the drive name, but then will tell me the drive can't start, error "Code 10", and sometimes it will show an error under Universal Serial Bus controllers. I've tried mounting/unmounting, disabling/reenabling, uninstalling the drive, searching for new drivers, and resetting the VM a dozen times, but no luck establishing a real mount of the drive.
Considering that the drive still works perfectly in Bootcamp, and that Parallels 8 ran the drive great before I upgraded two days ago, I'm pretty sure this is an issue with Parallels 11. Any solutions out there? Or does this need a Parallels patch?