Page 1 of 5
SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 30. Jul 2011, 22:27
by foxdoismil
The solution is on the 4th post in this thread
viewtopic.php?f=6&t=43541&p=195871#p195973
Host OS: Windows 7 Home Premium
Host Computer: Notebook HP Pavilion dv7-3165dx
Host Processor: AMD Turion
Virtualbox Version: 4.1.0.r73009
I can't use USB and get the following message:
Problem description:
Failed to access the USB subsystem
Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND).
The service might not be installed in the host computer.
Result Code: E_FAIL (0x00004005)
Component: Host
Interface: IHost {dab4a2b8-c735-4f08-94fc-9bec84182e2f}
Callee: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}
I checked google and this forum a lot and it seens to be a recurring problem with no easy solution.
The basic things like intall/uninstall/reinstall and additions/Extension Pack installations/upgrades have already been done. (But I will reinstall if required)
I will sincerelly apreciate any help provided.
Re: Failed to access the USB subsystem on Windows 7 host
Posted: 31. Jul 2011, 02:16
by virtualblt
I just installed virtualbox and enountered the exact same problem. I have been getting around it by writing everything from my usb drives to DVDs, but that's a pain. Can anyone can point me to a technote or let me know how to fix this?
Re: Failed to access the USB subsystem on Windows 7 host
Posted: 31. Jul 2011, 17:10
by virtualdon
Three more instances of this problem documented here (assuming I have copied the posting address correctly):
http://forums.virtualbox.org/viewtopic.php?f=6&t=43270
A fix would be appreciated.
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 1. Aug 2011, 04:25
by foxdoismil
This problem is related to a USB Driver conflict in the Host computer. It occurs due to a filter made by AMD.
This issue can occur because unknown USB drivers are installed on the Windows machine HOST or due to conflicting USB software or registry entries.
These are procedures to clear this problem. Most important is the item "D" to manually uninstall the AMD USB filter.
A. Ensure that your host computer is using the original, Microsoft USB drivers:
- 1. Right-click (My) Computer and click Manage.
2. In the left pane of the Computer Management window, select Device Manager.
3. Expand Universal Serial Bus Controllers.
4. Right-click USB Root Hub and click Properties.
5. On the Driver tab, click Roll Back Driver.
B. Confirm that you are not using any conflicting USB services such as monitors (sniffers) on your host. For more information, see Configuring Windows Hosts for Use with USB Monitors (Sniffers) (1679).
C. If you have an AMD processor, there may be a conflicting USB controller. It is recommended to remove the AMD USB Filter Driver from the Windows Device Manager:
Warning: This can cause other USB devices to fail. Be sure to make a System Restore point before attempting this step. Alternatively, rather than trying a system restore, you can restore the USB controller you deleted in this step by clicking Scan for New Hardware in Device Manager. For more information about System Restore, see these Microsoft articles:
* Windows XP:
http://www.microsoft.com/windowsxp/usin ... store.mspx
* Windows Vista, 7:
http://www.microsoft.com/windows/window ... store.aspx
To remove the conflicting USB controller:
- 1. Right-click (My) Computer and click Manage.
2. In the left pane of the Computer Management window, click Device Manager.
3. Expand Universal Serial Bus Controllers.
4. Locate the AMD USB Filter Driver.
5. Right-click it and choose Uninstall.
6. Click Uninstall the driver software for the device.
7. Restart your computer
D. If you are unable to remove the AMD USB controller through the Device Manager, you can also uninstall it manually.
You should backup the Windows registry before modifying it. For more information, see the Microsoft Knowledge Base article 322756.
To manually remove the AMD USB controller:
- 1. Open the Windows registry, by clicking Start > Run and typing regedit.
2. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000} .
3. In the right hand panel, if the the UpperFilters entry exists, delete it.
4. Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ .
5. Delete the usbfilter string.
6. Close the Registry
7. Delete this file: %system32%\drivers\usbfilter.sys.
8. Reboot your computer.
E. You can also use the ATI Catalyst Install Manager to uninstall AMD USB controller.
To do so:
- 1. Open Control Panel.
2. Open Add/Remove Programs (XP) or Programs and Features (Vista/7).
3. Double-click ATI Catalyst Install Manager or click Change.
4. Select Uninstall Manager.
5. Choose a Custom.
6. Select the AMD USB controller as the component to uninstall.
7. Reboot if prompted.
References:
Search for "Host USB device connections disabled" (This is the very same problem occurring with VMware)
http://kb.vmware.com/selfservice/micros ... Id=1016809
Hope this may help. Please report if you could fix your box.
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 2. Aug 2011, 01:08
by virtualdon
The above solution fixed my problems with USB for both a Linux Mint 11 and a Windows 2K guest.
I used the ATI install Manager to remove the AMD USB filter software - usbfilter.sys
I then re-installed the USB Extension Pack. Apparently, it did not install correctly with the above AMD USB filter in place.
Then, it was clear sailing. I added one USB flash drive to Virtualbox and it was immediately recognized by the above two guests.
Thank you foxdoismil for this fix. I appreciate you taking the time to post the fix for everyone to see.
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 4. Aug 2011, 20:02
by mark rumsey
Worked for me too. Uninstalling drivers doesn't really count as a fix in my books, so I assume this will be seen as a workaround until the next release or the one after.
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 19. Aug 2011, 10:18
by misha
To all having the "VERR_FILE_NOT_FOUND Failed to access USB subsystem" issue on Windows hosts: Please try this test build
http://www.virtualbox.org/download/test ... tiArch.exe that contains a fix for this issue and let me know whether it fixes the issue for you.
Besides that the "VERR_FILE_NOT_FOUND" dialog should not appear now, device capturing should work as well (unlike pre-4.1), so please test whether you can attach any USB devices to VMs as well.
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 19. Aug 2011, 22:18
by tvarilek
The test build resolves the problem. Thank you.
I am able to add USB devices to and remove them from the VMs.
I am running an AMD Phenom II X4 975 processor.
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 20. Aug 2011, 00:14
by panzerswine
2 of my usb ports work and 2 tell me it's busy, same as the released version
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 20. Aug 2011, 03:43
by ElQuia
NOT SOLVED
After installing 4.1.3 from this post, I do not get any more the error:
Could not load the Host USB Proxy Service
(VERR_FILE_NOT_FOUND). Ther service might not be
installed on the host computer
BUT, when the VM starts (be that XP or linux) (host is 7 x64) and host starts "installing device driver" guest freezes and host freezes totally, system stops responding and I have to do a cold reset.
Rolling back to 4.1.0 and VERR_FILE_NOT_FOUND error, with NO USB. But at least guests dont freeze my system.
Guys, guys, guys.....
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 20. Aug 2011, 09:44
by misha
ElQuia wrote:NOT SOLVED..
Wha custom USB software do you have installed on your host? Please dump here the contents of the "UpperFilters" value for the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}" registry key.
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 20. Aug 2011, 10:01
by misha
panzerswine wrote:2 of my usb ports work and 2 tell me it's busy
Please provide detailed description of your problem.
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 20. Aug 2011, 14:49
by ElQuia
misha wrote:ElQuia wrote:NOT SOLVED..
Wha custom USB software do you have installed on your host? Please dump here the contents of the "UpperFilters" value for the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}" registry key.
@misha here it goes:
Code: Select all
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}
Class Name: <NO CLASS>
Last Write Time: 110808 - 14:47
Value 0
Name: Class
Type: REG_SZ
Data: USB
Value 1
Name: ClassDesc
Type: REG_SZ
Data: @%SystemRoot%\System32\SysClass.Dll,-3025
Value 2
Name: <NO NAME>
Type: REG_SZ
Data: Universal Serial Bus controllers
Value 3
Name: IconPath
Type: REG_MULTI_SZ
Data: %systemroot%\system32\setupapi.dll,-20
Value 4
Name: NoInstallClass
Type: REG_SZ
Data: 1
Value 5
Name: LowerLogoVersion
Type: REG_SZ
Data: 5.2
Value 6
Name: UpperFilters
Type: REG_MULTI_SZ
Data: tpdevflt
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0000
Class Name: <NO CLASS>
Last Write Time: 110807 - 19:07
Value 0
Name: Controller
Type: REG_BINARY
Data:
00000000 01 .
Value 1
Name: InfPath
Type: REG_SZ
Data: usbport.inf
Value 2
Name: InfSection
Type: REG_SZ
Data: OHCI.Dev
Value 3
Name: InfSectionExt
Type: REG_SZ
Data: .NT
Value 4
Name: ProviderName
Type: REG_SZ
Data: Microsoft
Value 5
Name: DriverDateData
Type: REG_BINARY
Data:
00000000 00 80 8c a3 c5 94 c6 01 - ...£Å.Æ.
Value 6
Name: DriverDate
Type: REG_SZ
Data: 6-21-2006
Value 7
Name: DriverVersion
Type: REG_SZ
Data: 6.1.7601.17586
Value 8
Name: MatchingDeviceId
Type: REG_SZ
Data: pci\cc_0c0310
Value 9
Name: DriverDesc
Type: REG_SZ
Data: Standard OpenHCD USB Host Controller
Value 10
Name: EnumPropPages32
Type: REG_SZ
Data: usbui.dll,USBControllerPropPageProvider
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0001
Class Name: <NO CLASS>
Last Write Time: 110807 - 19:07
Value 0
Name: Controller
Type: REG_BINARY
Data:
00000000 01 .
Value 1
Name: InfPath
Type: REG_SZ
Data: usbport.inf
Value 2
Name: InfSection
Type: REG_SZ
Data: EHCI.Dev
Value 3
Name: InfSectionExt
Type: REG_SZ
Data: .NT
Value 4
Name: ProviderName
Type: REG_SZ
Data: Microsoft
Value 5
Name: DriverDateData
Type: REG_BINARY
Data:
00000000 00 80 8c a3 c5 94 c6 01 - ...£Å.Æ.
Value 6
Name: DriverDate
Type: REG_SZ
Data: 6-21-2006
Value 7
Name: DriverVersion
Type: REG_SZ
Data: 6.1.7601.17586
Value 8
Name: MatchingDeviceId
Type: REG_SZ
Data: pci\cc_0c0320
Value 9
Name: DriverDesc
Type: REG_SZ
Data: Standard Enhanced PCI to USB Host Controller
Value 10
Name: EnumPropPages32
Type: REG_SZ
Data: usbui.dll,USBControllerPropPageProvider
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0002
Class Name: <NO CLASS>
Last Write Time: 110807 - 19:07
Value 0
Name: InfPath
Type: REG_SZ
Data: usbport.inf
Value 1
Name: InfSection
Type: REG_SZ
Data: ROOTHUB.Dev
Value 2
Name: InfSectionExt
Type: REG_SZ
Data: .NT
Value 3
Name: ProviderName
Type: REG_SZ
Data: Microsoft
Value 4
Name: DriverDateData
Type: REG_BINARY
Data:
00000000 00 80 8c a3 c5 94 c6 01 - ...£Å.Æ.
Value 5
Name: DriverDate
Type: REG_SZ
Data: 6-21-2006
Value 6
Name: DriverVersion
Type: REG_SZ
Data: 6.1.7601.17586
Value 7
Name: MatchingDeviceId
Type: REG_SZ
Data: usb\root_hub
Value 8
Name: DriverDesc
Type: REG_SZ
Data: USB Root Hub
Value 9
Name: EnumPropPages32
Type: REG_SZ
Data: usbui.dll,USBHubPropPageProvider
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0003
Class Name: <NO CLASS>
Last Write Time: 110807 - 19:07
Value 0
Name: InfPath
Type: REG_SZ
Data: usbport.inf
Value 1
Name: InfSection
Type: REG_SZ
Data: ROOTHUB.Dev
Value 2
Name: InfSectionExt
Type: REG_SZ
Data: .NT
Value 3
Name: ProviderName
Type: REG_SZ
Data: Microsoft
Value 4
Name: DriverDateData
Type: REG_BINARY
Data:
00000000 00 80 8c a3 c5 94 c6 01 - ...£Å.Æ.
Value 5
Name: DriverDate
Type: REG_SZ
Data: 6-21-2006
Value 6
Name: DriverVersion
Type: REG_SZ
Data: 6.1.7601.17586
Value 7
Name: MatchingDeviceId
Type: REG_SZ
Data: usb\root_hub20
Value 8
Name: DriverDesc
Type: REG_SZ
Data: USB Root Hub
Value 9
Name: EnumPropPages32
Type: REG_SZ
Data: usbui.dll,USBHubPropPageProvider
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0004
Class Name: <NO CLASS>
Last Write Time: 110807 - 19:07
Value 0
Name: InfPath
Type: REG_SZ
Data: usb.inf
Value 1
Name: InfSection
Type: REG_SZ
Data: Composite.Dev
Value 2
Name: InfSectionExt
Type: REG_SZ
Data: .NT
Value 3
Name: ProviderName
Type: REG_SZ
Data: Microsoft
Value 4
Name: DriverDateData
Type: REG_BINARY
Data:
00000000 00 80 8c a3 c5 94 c6 01 - ...£Å.Æ.
Value 5
Name: DriverDate
Type: REG_SZ
Data: 6-21-2006
Value 6
Name: DriverVersion
Type: REG_SZ
Data: 6.1.7601.17586
Value 7
Name: MatchingDeviceId
Type: REG_SZ
Data: usb\composite
Value 8
Name: DriverDesc
Type: REG_SZ
Data: USB Composite Device
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0005
Class Name: <NO CLASS>
Last Write Time: 110807 - 19:05
Value 0
Name: DriverFlags
Type: REG_DWORD
Data: 0x1
Value 1
Name: InfPath
Type: REG_SZ
Data: usbstor.inf
Value 2
Name: InfSection
Type: REG_SZ
Data: USBSTOR_BULK
Value 3
Name: InfSectionExt
Type: REG_SZ
Data: .NT
Value 4
Name: ProviderName
Type: REG_SZ
Data: Microsoft
Value 5
Name: DriverDateData
Type: REG_BINARY
Data:
00000000 00 80 8c a3 c5 94 c6 01 - ...£Å.Æ.
Value 6
Name: DriverDate
Type: REG_SZ
Data: 6-21-2006
Value 7
Name: DriverVersion
Type: REG_SZ
Data: 6.1.7601.17577
Value 8
Name: MatchingDeviceId
Type: REG_SZ
Data: usb\class_08&subclass_06&prot_50
Value 9
Name: DriverDesc
Type: REG_SZ
Data: USB Mass Storage Device
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0006
Class Name: <NO CLASS>
Last Write Time: 110807 - 19:05
Value 0
Name: DriverFlags
Type: REG_DWORD
Data: 0x1
Value 1
Name: InfPath
Type: REG_SZ
Data: usbstor.inf
Value 2
Name: InfSection
Type: REG_SZ
Data: USBSTOR_BULK
Value 3
Name: InfSectionExt
Type: REG_SZ
Data: .NT
Value 4
Name: ProviderName
Type: REG_SZ
Data: Microsoft
Value 5
Name: DriverDateData
Type: REG_BINARY
Data:
00000000 00 80 8c a3 c5 94 c6 01 - ...£Å.Æ.
Value 6
Name: DriverDate
Type: REG_SZ
Data: 6-21-2006
Value 7
Name: DriverVersion
Type: REG_SZ
Data: 6.1.7601.17577
Value 8
Name: MatchingDeviceId
Type: REG_SZ
Data: usb\class_08&subclass_06&prot_50
Value 9
Name: DriverDesc
Type: REG_SZ
Data: USB Mass Storage Device
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0007
Class Name: <NO CLASS>
Last Write Time: 110815 - 19:28
Value 0
Name: InfPath
Type: REG_SZ
Data: usb.inf
Value 1
Name: InfSection
Type: REG_SZ
Data: BADDEVICE.Dev
Value 2
Name: InfSectionExt
Type: REG_SZ
Data: .NT
Value 3
Name: ProviderName
Type: REG_SZ
Data: Microsoft
Value 4
Name: DriverDateData
Type: REG_BINARY
Data:
00000000 00 80 8c a3 c5 94 c6 01 - ...£Å.Æ.
Value 5
Name: DriverDate
Type: REG_SZ
Data: 6-21-2006
Value 6
Name: DriverVersion
Type: REG_SZ
Data: 6.1.7601.17586
Value 7
Name: MatchingDeviceId
Type: REG_SZ
Data: usb\unknown
Value 8
Name: DriverDesc
Type: REG_SZ
Data: Unknown Device
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0008
Class Name: <NO CLASS>
Last Write Time: 110807 - 19:05
Value 0
Name: DriverFlags
Type: REG_DWORD
Data: 0x1
Value 1
Name: InfPath
Type: REG_SZ
Data: usbstor.inf
Value 2
Name: InfSection
Type: REG_SZ
Data: USBSTOR_BULK
Value 3
Name: InfSectionExt
Type: REG_SZ
Data: .NT
Value 4
Name: ProviderName
Type: REG_SZ
Data: Microsoft
Value 5
Name: DriverDateData
Type: REG_BINARY
Data:
00000000 00 80 8c a3 c5 94 c6 01 - ...£Å.Æ.
Value 6
Name: DriverDate
Type: REG_SZ
Data: 6-21-2006
Value 7
Name: DriverVersion
Type: REG_SZ
Data: 6.1.7601.17577
Value 8
Name: MatchingDeviceId
Type: REG_SZ
Data: usb\class_08&subclass_06&prot_50
Value 9
Name: DriverDesc
Type: REG_SZ
Data: USB Mass Storage Device
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0009
Class Name: <NO CLASS>
Last Write Time: 110807 - 20:31
Value 0
Name: DriverFlags
Type: REG_DWORD
Data: 0x1
Value 1
Name: InfPath
Type: REG_SZ
Data: usbstor.inf
Value 2
Name: InfSection
Type: REG_SZ
Data: USBSTOR_BULK
Value 3
Name: InfSectionExt
Type: REG_SZ
Data: .NT
Value 4
Name: ProviderName
Type: REG_SZ
Data: Microsoft
Value 5
Name: DriverDateData
Type: REG_BINARY
Data:
00000000 00 80 8c a3 c5 94 c6 01 - ...£Å.Æ.
Value 6
Name: DriverDate
Type: REG_SZ
Data: 6-21-2006
Value 7
Name: DriverVersion
Type: REG_SZ
Data: 6.1.7601.17577
Value 8
Name: MatchingDeviceId
Type: REG_SZ
Data: usb\class_08&subclass_06&prot_50
Value 9
Name: DriverDesc
Type: REG_SZ
Data: USB Mass Storage Device
Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0010
Class Name: <NO CLASS>
Last Write Time: 110807 - 22:31
Value 0
Name: DriverFlags
Type: REG_DWORD
Data: 0x1
Value 1
Name: InfPath
Type: REG_SZ
Data: usbstor.inf
Value 2
Name: InfSection
Type: REG_SZ
Data: USBSTOR_BULK
Value 3
Name: InfSectionExt
Type: REG_SZ
Data: .NT
Value 4
Name: ProviderName
Type: REG_SZ
Data: Microsoft
Value 5
Name: DriverDateData
Type: REG_BINARY
Data:
00000000 00 80 8c a3 c5 94 c6 01 - ...£Å.Æ.
Value 6
Name: DriverDate
Type: REG_SZ
Data: 6-21-2006
Value 7
Name: DriverVersion
Type: REG_SZ
Data: 6.1.7601.17577
Value 8
Name: MatchingDeviceId
Type: REG_SZ
Data: usb\class_08&subclass_06&prot_50
Value 9
Name: DriverDesc
Type: REG_SZ
Data: USB Mass Storage Device
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 21. Aug 2011, 13:02
by dmix75
misha wrote:To all having the "VERR_FILE_NOT_FOUND Failed to access USB subsystem" issue on Windows hosts: Please try this test build
http://www.virtualbox.org/download/test ... tiArch.exe that contains a fix for this issue and let me know whether it fixes the issue for you.
Besides that the "VERR_FILE_NOT_FOUND" dialog should not appear now, device capturing should work as well (unlike pre-4.1), so please test whether you can attach any USB devices to VMs as well.
Test Build resolved my problem as well. Thank you.
AMD A6-3100MX
Re: SOLVED: Failed to access the USB subsystem on Windows 7 host
Posted: 22. Aug 2011, 12:23
by misha
ElQuia wrote:
...
Value 6
Name: UpperFilters
Type: REG_MULTI_SZ
Data: tpdevflt
...
The tpdevflt seems to come from one of TrustPort Security products. What TrustPort Security products (and which version exactly) do you have installed? Also what USB devices are you trying to filter (i.e. attach to guest)?
Please also specify the host OS version you use.