Solved strange USB Problem
Posted: 29. Oct 2008, 10:47
Hi Folks,
I am using VirtualBox for several weeks now, my original intention was to convert an existing Notebook based on Win2k to a virtual machine and use it on my new MacBook.
Since the MacBook is not yet available, I tried to create the VM within my standard working Box which is running Windows XP SP2.
I was running VB 2.0.2 and now upgraded to 2.0.4.
The software in the client includes ActiveSync to synchronize my Asus 693 PDA with Outlook, I also use PocketFMS and Destinator which are talking to the PDA. Furthermore, my Sony-Ericson 750 mobile gets syncronised with its own software.
When I ran the USB setup procedure, the devices (not known to the host) tried to install themselves on the host, but they were never seen by the VM, especiall VBoxManage list usbhosts showed no reaction most of the times. Sometimes, however, one of the devices appeared but I never managed to connect it with my Win2k client.
I created an empty partition and installed a lean WinXP there, installed VB, started the existing VDI and bingo: Everything was working fine!
At last, I found a hint here:
http://www.expansys-usa.com/ft.aspx?k=68804
which inspired me to further investigate the usb devices in the device manager:
When looking at an arbitrary USB device, klicking "Properties", then the "driver" tab, then "driver details", there was always one driver at the top which was named hpusbfd.sys.
As figured out in the link mentioned above, this driver came from an old Hewlett Packard scanner which has been gone since about a year (and the software deinstalled, of course!). But, this driver had been forgotten by the deinstallation and seems to block the VB usb driver from seeing devices when they get plugged in.
To help anyone who might not be able to jump to the link above or in case the link has been gone, here is a citation showing how to get rid of this:
-----------------
After comparing this screenshot of the working configuration drivers properties with the screenshot the non-working configuration drivers properties i saw that the non-working configuration was using a totally non-related file called hpusbfd.sys. This file came with the HP scanner i once installed.
It turned out that this file was well known for conflicting with other usb storage devices.
So i unregistered the file through the register by deleting the relevant register key and renamed the file following this guide:
(PS. This isn't a generic fix for all connecting problems. It's a specific fix to a specific problem. If you don't have the file hpusbfd.sys on your system then you are experiencing a different problem requiring a different fix. Don't follow this fix in that case as it will only do more harm then good.)
Click Start and then Run. The Run window opens.
In the Open: box type regedit.
Click OK. The Registry Editor window opens.
Click the plus ( +) sign next to HKEY_LOCAL_MACHINE.
Click the plus ( +) sign next to System.
Click the plus ( +) sign next to CurrentControlSet.
Click the plus ( +) sign next to Control.
Click the plus ( +) sign next to Class.
Click the plus ( +) sign next to {36FC9E60-C465-11CF-8056-444553540000}.
Note the number of keys that appear below the {36FC9E60-C465-11CF-8056-444553540000} key in the last step.
Click {36FC9E60-C465-11CF-8056-444553540000} so that it is highlighted.
Right-click the UpperFilters line in the right hand window, then click Delete.
Click Yes when prompted if you are sure that you want to delete the Upper Filters line.
Click File and then Exit to close the windows registry.
Click Start and then Search. The Search window opens.
Click All Files and Folders.
In the All or Part of the File Name box type HPUSBFD.sys.
In the Look In: drop-down box select Local Hard Drives.
Click Search.
Right-click on each file that Windows Search finds then click Rename.
Rename the files to HPUSBFD.old or HPUSBFDOLD.sys.
Close the Search dialog box.
Restart the computer.
-----------------
I followed this guidelines to get rid of the old driver and now I can use VB with my normal computer setup. Marvellous!
I hope this could help some people noticing similar problems!
Best regards,
Gerhard
I am using VirtualBox for several weeks now, my original intention was to convert an existing Notebook based on Win2k to a virtual machine and use it on my new MacBook.
Since the MacBook is not yet available, I tried to create the VM within my standard working Box which is running Windows XP SP2.
I was running VB 2.0.2 and now upgraded to 2.0.4.
The software in the client includes ActiveSync to synchronize my Asus 693 PDA with Outlook, I also use PocketFMS and Destinator which are talking to the PDA. Furthermore, my Sony-Ericson 750 mobile gets syncronised with its own software.
When I ran the USB setup procedure, the devices (not known to the host) tried to install themselves on the host, but they were never seen by the VM, especiall VBoxManage list usbhosts showed no reaction most of the times. Sometimes, however, one of the devices appeared but I never managed to connect it with my Win2k client.
I created an empty partition and installed a lean WinXP there, installed VB, started the existing VDI and bingo: Everything was working fine!
At last, I found a hint here:
http://www.expansys-usa.com/ft.aspx?k=68804
which inspired me to further investigate the usb devices in the device manager:
When looking at an arbitrary USB device, klicking "Properties", then the "driver" tab, then "driver details", there was always one driver at the top which was named hpusbfd.sys.
As figured out in the link mentioned above, this driver came from an old Hewlett Packard scanner which has been gone since about a year (and the software deinstalled, of course!). But, this driver had been forgotten by the deinstallation and seems to block the VB usb driver from seeing devices when they get plugged in.
To help anyone who might not be able to jump to the link above or in case the link has been gone, here is a citation showing how to get rid of this:
-----------------
After comparing this screenshot of the working configuration drivers properties with the screenshot the non-working configuration drivers properties i saw that the non-working configuration was using a totally non-related file called hpusbfd.sys. This file came with the HP scanner i once installed.
It turned out that this file was well known for conflicting with other usb storage devices.
So i unregistered the file through the register by deleting the relevant register key and renamed the file following this guide:
(PS. This isn't a generic fix for all connecting problems. It's a specific fix to a specific problem. If you don't have the file hpusbfd.sys on your system then you are experiencing a different problem requiring a different fix. Don't follow this fix in that case as it will only do more harm then good.)
Click Start and then Run. The Run window opens.
In the Open: box type regedit.
Click OK. The Registry Editor window opens.
Click the plus ( +) sign next to HKEY_LOCAL_MACHINE.
Click the plus ( +) sign next to System.
Click the plus ( +) sign next to CurrentControlSet.
Click the plus ( +) sign next to Control.
Click the plus ( +) sign next to Class.
Click the plus ( +) sign next to {36FC9E60-C465-11CF-8056-444553540000}.
Note the number of keys that appear below the {36FC9E60-C465-11CF-8056-444553540000} key in the last step.
Click {36FC9E60-C465-11CF-8056-444553540000} so that it is highlighted.
Right-click the UpperFilters line in the right hand window, then click Delete.
Click Yes when prompted if you are sure that you want to delete the Upper Filters line.
Click File and then Exit to close the windows registry.
Click Start and then Search. The Search window opens.
Click All Files and Folders.
In the All or Part of the File Name box type HPUSBFD.sys.
In the Look In: drop-down box select Local Hard Drives.
Click Search.
Right-click on each file that Windows Search finds then click Rename.
Rename the files to HPUSBFD.old or HPUSBFDOLD.sys.
Close the Search dialog box.
Restart the computer.
-----------------
I followed this guidelines to get rid of the old driver and now I can use VB with my normal computer setup. Marvellous!
I hope this could help some people noticing similar problems!
Best regards,
Gerhard