Win7 USB error ==> Fixed in SVN

[Nathan]

I upgraded from VirtualBox 4.0.x (latest version of 4.0 series) to the latest version of 4.1 on Windows 7 Ultimate x64. When I go into any VirtualBox machine settings, I get and error window that says:

---

Failed to access the USB subsystem.

Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might not be installed on the host computer.

Details

ResultCode: E_FAIL (0x00004005)

Component: Host

Interface: IHost {dab4a2b8-c735-4f0894fc9bec84182e2f}

Callee: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

---

This happens every time I try to enter any settings, even while the machine is running. I have a forum thread at ​http://forums.virtualbox.org/viewtopic.php?f=6&t=43341&p=194903#p194903 and a screenshot of the error at ​http://dl.dropbox.com/u/16149550/CPU/ScreenShot001.png

I can provide more information if needed.

Here's a link to the only VBox.log that may have some info, because the error only shows up either when I'm entering VirtualBox machine settings before I start it, or when I enter the settings while the machine is running. I don't know if it'll have any info, but here it is:

​http://dl.dropbox.com/u/16149550/TroubleShooting/VBox.log

[misha]

VBox 4.1 behaves more consistent wrt to host USB device handling, i.e. it will display such message whenever it detects it won't be able to perform USB device capturing for any reason.
Despite that you were not seeing this message and was able to list USB devices in VBox pre-4.1, were you able to attach any USB device to guest?

[Nathan]

Replying to misha:

VBox 4.1 behaves more consistent wrt to host USB device handling, i.e. it will display such message whenever it detects it won't be able to perform USB device capturing for any reason.
Despite that you were not seeing this message and was able to list USB devices in VBox pre-4.1, were you able to attach any USB device to guest?

Yeah, I was previously able to attach my USB keyboard, just for experimentation. I think I also attached my printer.

[Nathan]

I just noticed that I am unable to attach any USB devices to any virtual machine, as well, in the current version.

[Lika]

I really got the same error with Host USB Proxy Service (VERR_FILE_NOT_FOUND). I tried to uninstall and reinstall to older version that was working fine. However, still I can't figure out.

[misha]

Replying to jik686:

I really got the same error with Host USB Proxy Service (VERR_FILE_NOT_FOUND). I tried to uninstall and reinstall to older version that was working fine. However, still I can't figure out.

Did attaching USB devices to guest also worked for you for VBox 4.0.x ?

[misha]

Replying to shark.basketball: I'm unable to reproduce your "VERR_FILE_NOT_FOUND" problem here. I can post you an instrumented build with verbose logging enabled so that you can collect and post us back the debug log for VBox USB subsystem initialization. If you are willing to test, just drop me a mail at mikhail dot sennikovsky at oracle dot com I then post you a link to the build and instructions on how to collect the log.

[Mehdi Amiri]

I have the same error message when I try to use the new version of virtual box (4.1.0). I did not have this error on the latest version 4.0.12. I’m using Windows 7 home premium 64. I have installed the new oracle extension packages too.

The error message is :

Failed to access the USB subsystem.
Could not load the USB Proxy service (VERR_FILE_NOT_FOUND).
The service might not be installed on the host computer.

Details are :

Result Code:  E_FAIL (0x00004005)
Component: Host
Interface: IHost {dab4a2b8-c735-4f08-94fc-9bec84182e2f}
Callee: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

---

I tried to remove the new version & install it again but the problem was not solved.

[misha]

Replying to amiri: same question as to everyone here: were you able to attach USB devices to a VM with VBox 4.0.x ? If not - then this is not a regression, just a more strict and consistent way of err handling.

[Mehdi Amiri]

Replying to misha:

Replying to amiri: same question as to everyone here: were you able to attach USB devices to a VM with VBox 4.0.x ? If not - then this is not a regression, just a more strict and consistent way of err handling.

Previously I didn't try to attache a USB to my guest system in my windows host (& I didn't get any errors on each machine settings), to give a correct answer to your question I uninstalled the new version and installed the older version again. With in Virtual Box 4.0.12, I can see my USB devices like my flash USB disk and etc but I can not attache them. For example I tried to attache my USB flash drive & I got the following error:

Failed to attache the USB device, .... Details:

Result Code:  E_INVALIDARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}

I hope this will help.

[kh151]

Same error for me - logged via earlier ticket 9293 - ​http://www.virtualbox.org/ticket/9293

[misha]

Replying to kh151:

Same error for me - logged via earlier ticket 9293 - ​http://www.virtualbox.org/ticket/9293

same question to you: were you able to attach USB devices to a VM with VBox 4.0.x ? If not - then this is not a regression, just a more strict and consistent way of err handling.

[Rob Brown]

Just a data point, I was having the same issue but thanks to misha's assistance I found that it was caused by some USB logging software I had installed (HHD Device Monitoring Studio). I've uninstalled DMS for now. Hopefully DMS and VB will play nicely sometime in the future, because DMS is very useful.

[coala]

After installation of VM 4.1 I found following issues what didn't appear earlier and were not resolved by ver. 4.1.2: 1) error with Host USB Proxy Service (VERR_FILE_NOT_FOUND), 2) bridged networking not functioning, 3) shared folders inaccessibles.

My system is Win7 x64 on AMD Athlon II.

Any ideas how to fix it, please?

[DH]

same issue here, but on x64 vista host. will post log file.

[DH]

vbox log file

[misha]

To all having VERR_FILE_NOT_FOUND issue on Windows hosts: Please try ​this test build 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.

[softcat]

The test build solves the problem perfectly on my system, the error dialog disappeares and I'm able to connect any USB device successfully.

[Nathan]

I can confirm that this fixes the problem. I now do not get the error popup when entering settings, and have successfully attached USB devices to virtual machines. Is this going to be fixed in the next public release as well?

[DH]

it works! you guys rock! :)

[Rob Brown]

The test build still doesn't work with HHD Software USB Monitor installed. That's with the test build's guest additions installed and 4.1.2 extension pack. Sounds like you've made some other people happy though!

[misha]

Replying to RobBrownNZ:

The test build still doesn't work with HHD Software USB Monitor installed. That's with the test build's guest additions installed and 4.1.2 extension pack. Sounds like you've made some other people happy though!

What do you mean by "with the test build's guest additions installed"? You need to install test build on host, guest additions, should not matter since its a purely host side problem.
Did you install the test build on host?

[misha]

Replying to RobBrownNZ:

The test build still doesn't work with HHD Software USB Monitor installed. That's with the test build's guest additions installed and 4.1.2 extension pack. Sounds like you've made some other people happy though!

Just tested it here with HHD Device Monitoring Studio v6.23 installed on Win7 host - usb device capturing working fine here.

[Rob Brown]

Replying to misha:

What do you mean by "with the test build's guest additions installed"? You need to install test build on host, guest additions, should not matter since its a purely host side problem.
Did you install the test build on host?

Aha, I didn't realise that the guest additions were irrelevant.

I uninstalled VB 4.1.2, installed HHD DMS, installed the VB test build, ran my guest, device capturing didn't work. Then I installed the test build's guest additions, rebooted my PC, ran my guest, and device capturing didn't work.

By "didn't work", there were no error messages but the device never became available to my guest. Trying to capture again gave an error message that the device was busy with another request.

My host is WinXP Professional SP3 32-bit. Guest is Ubuntu 64-bit 11.04, with updates.

I will try the process again, in case I got something wrong. Thanks again for your efforts.

[Rob Brown]

Replying to RobBrownNZ:

I will try the process again, in case I got something wrong. Thanks again for your efforts.

Nope, still no go. I also tried running the test build with DebugView running, but there was no output. I guess you'd expect that!

Not sure what else to say at this point; there's no error message produced so no hints. As I said though, I'm happy with the workaround of uninstalling DMS at the moment.

[misha]

Replying to RobBrownNZ: I'll try to repro it on XP host, what HHD DMS version are you running?

[Rob Brown]

6.23.00.3373

[Rob Brown]

Woah! OK, so now it's working. I _think_ that what I did was: uninstall DMS, install VB (test build), run VB and add a device, install DMS, run VB and add a device -> success. It certainly did not work when I installed DMS before VB.

There's something odd here. Perhaps the best thing would be for you to leave it and I'll do some more testing to see if I can isolate the exact sequence that doesn't work.

[Rob Brown]

I uninstalled VB and DMS. Manually removed items the uninstallations didn't, such as extension packs and drivers. Rebooted. Installed DMS, used it to capture some traffic. Installed VB, attached a couple of devices, everything worked fine. That's not what I expected! I must admit I'm out of ideas about how to make it fail again. I was extremely careful with the last testing I did (comment 22, above) so I know it really _did_ fail, but maybe that was just some sort of crud buildup in my PC that got cleared by the uninstall/install cycles I did?

[misha]

Replying to RobBrownNZ: I wonder if this was caused by VBox USBMon driver not being updated in your previous install that did not work for you.
In any way glad to hear it works ok now. Let me know if you see this issue again.

[John Biz]

when going from 4.0 to 4.1.2 I get this error. host = win 7 64 new install. if i disable the usb then error goes away. If i go back to 4.0 error goes away.

no effect: 1.made new VM 2.re-install 3.new-install

The Error: Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might not be installed on the host computer.

Result Code: E_FAIL (0x00004005) Component: Host Interface: IHost {dab4a2b8-c735-4f08-94fc-9bec84182e2f} Callee: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

[misha]

Replying to dx80486: Please try the test build with the fix mentioned in comment 15

[coala]

Replying to misha:

To all having VERR_FILE_NOT_FOUND issue on Windows hosts: Please try ​this test build 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.

Thanks a lot! The fix helped to resolve most of issues. USB devices are discovered, sharing folders work.

Problems with network connections were not resolved. External Internet connection works only at selection of virtual connection adapter (NAT mode) and its not possible to access shared folders then. Optiom of bridged WiFi networking works fine for Shared folders (home network is accessible) but it doesn't enable Internet connection. In current state of arts I have to switch between the 2 kinds of adapters (when both adapters are turned on only one is actually active). Is it problem with my computer configuration?

[Dirk Niemeier]

Replying to misha:

To all having VERR_FILE_NOT_FOUND issue on Windows hosts: Please try ​this test build 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.

Hi, the link doesn't exist any more. Is there an other build available to test the "solved" USB issue? TIA

Dirk

[Frank Mehnert]

Please check ​this one!

[Reg Talbot]

Replying to frank:

Please check ​this one!

I have the same problem (I'm running XP SP3 on a Win7 Home edition x64 Host) and the link appears not to be working. I'd be grateful for any help.

[Frank Mehnert]

VBox 4.1.4 contains the fix, please check and confirm if the bug is fixed for you!

[Reg Talbot]

Replying to frank:

VBox 4.1.4 contains the fix, please check and confirm if the bug is fixed for you!

Hi Frank; That seems to have done the trick. Many thanks.

[kh151]

Yep, checked with 4.1.2 that I couldn't see any USB devices under "Add Filter From Device", can see them all straight after installing 4.1.4.

[Frank Mehnert]

Thanks guys, in that case I will mark this defect as fixed.

[PO'd]

I just updated from 4.0.8 to 4.1.4 and am having this problem. host: winxp service pack 3

Previously I had no problem adding or using usb devices when on 4.0.8

Result Code: E_FAIL (0x00004005) Component: Host Interface: IHost {dab4a2b8-c735-4f08-94fc-9bec84182e2f} Callee: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

[Nick Galfas]

I also get this exact error after upgrading to 4.1.4

Fresh WinXP SP3 32bit host.

with the previous 4.1.3 version i didn't have this error

---

Result Code: E_FAIL (0x00004005) Component: Host Interface: IHost {dab4a2b8-c735-4f08-94fc-9bec84182e2f} Callee: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

[abafei]

Same think on lixux - debian squeeze and version 4.1.4:

Failed to access the USB subsystem. Could not load the Host USB Proxy Service (VERR_FILE_NOT_FOUND). The service might not be installed on the host computer.

Result Code: NS_ERROR_FAILURE (0x00004005) Component: Host Interface: IHost {dab4a2b8-c735-4f08-94fc-9bec84182e2f} Callee: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

[sebas]

Same think on lixux - debian squeeze and version 4.1.4

abafei, did you try to check if you were in vboxusers group ?

$ groups

I had the same issue (aptosid with vbox 4.1.2 and with 4.1.4), but I solved it with

# adduser sebas vboxusers

logout, login, then pb had disappeared

Why user "sebas" suddenly went out of vboxusers group (although I used vbox for a long time) I cannot say.

[B_Leibbrand]

Automatic upgrade to version 4.1.12_r77245 brougth the same problem. The previous version was a new install on my laptop and worked fine.

Resultaat Code: E_FAIL (0x00004005) Component: Host Interface: IHost {dab4a2b8-c735-4f08-94fc-9bec84182e2f} Callee: IMachine {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}

Before the upgrade I had my HTC HD2 phone connected as USB device (to synchronize outlook), so yes I used the USB.

BTO laptop quadcore / 8GB / Windows 7 prof 64 bits

Any steps for this version?

[Rob Brown]

B_Leibbrand: I think this is a new issue, because the symptom is different. When does the problem appear for you? For me, it occurs when I try to open "Settings" for guests that have USB enabled. Also see ​https://forums.virtualbox.org/viewtopic.php?f=6&t=48872

[B_Leibbrand]

Thanks RobBrownNZ, It's the same problem as you mention.

[Frank Mehnert]

Please reopen if still relevant with VBox 4.2.18.