Getting USB descriptor failed with error 995

[J.Dow]

My first clue was all my virtual machines ceased starting up. Since the last time it worked all that has been installed is VNC Client (from RealVNC), Windows Updates, and miscellaneous DirectShow filters that are under development here. This is with a formerly nicely working system. I noticed when I updated from 5.0.8 to 5.0.12 the network and usb services did not seem to get interrupted as was the usual case.

The Virtual Box server log shows the titular error in its logs:

Code: Select all

VirtualBox COM Server 5.0.12 r104815 win.amd64 (Dec 18 2015 16:07:28) release log
00:00:00.066003 main     Log opened 2015-12-22T04:17:31.645138100Z
00:00:00.066003 main     Build Type: release
00:00:00.066003 main     OS Product: Windows 7
00:00:00.066003 main     OS Release: 6.1.7601
00:00:00.066003 main     OS Service Pack: 1
00:00:00.100005 main     DMI Product Name: X8DA3
00:00:00.113006 main     DMI Product Version: 1234567890
00:00:00.113006 main     Host RAM: 24566MB total, 12905MB available
00:00:00.113006 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.113006 main     Process ID: 14224
00:00:00.113006 main     Package type: WINDOWS_64BITS_GENERIC
00:00:00.117006          Home directory: 'D:\Users\me/.VirtualBox'
00:00:00.118006          Loading settings file "D:\Users\me/.VirtualBox\VirtualBox.xml" with version "1.11-windows"
00:00:02.701154          Getting USB descriptor failed with error 995
00:00:04.701268          Getting USB descriptor failed with error 995
00:00:07.701440          Getting USB descriptor failed with error 995
00:00:07.959455          HostDnsMonitor: old information
00:00:07.959455            no server entries
00:00:07.959455            no search string entries
00:00:07.959455            no domain set
00:00:07.959455          HostDnsMonitor: new information
00:00:07.959455            server 1: 192.168.xxx.xxx    (Correct data was there.)
00:00:07.959455            no search string entries
00:00:07.959455            domain: xxxxxxxx      (Correct data was there.)
00:00:07.959455          HostDnsMonitorProxy::notify
00:00:08.146465          VD: VDInit finished
00:00:08.149466          Loading settings file "D:\VBox\Wibbler\Wibbler.vbox" with version "1.12-windows"
00:00:08.150466          Loading settings file "D:\VBox\Minty\Minty.vbox" with version "1.12-windows"
00:00:08.151466          Loading settings file "D:\VBox\SL6\SL6.vbox" with version "1.12-windows"
00:00:08.153466          Loading settings file "D:\VBox\FC17 64\FC17 64.vbox" with version "1.12-windows"
00:00:08.155466          Loading settings file "D:\VBox\Win7-32\Win7-32.vbox" with version "1.12-windows"
00:00:08.157466          Loading settings file "D:\VBox\Wednesday2\Wednesday2.vbox" with version "1.14-windows"
00:00:08.158466          Loading settings file "D:\VBox\Win8.1 thingie\Win8.1 thingie.vbox" with version "1.14-windows"
00:00:08.159466          Loading settings file "D:\VBox\SL6p5\SL6p5.vbox" with version "1.14-windows"
00:00:08.161466          Loading settings file "D:\VBox\Haiku v1 Alpha 4\Haiku v1 Alpha 4.vbox" with version "1.15-windows"
00:00:08.643494          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:08.643494          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:00:08.644494          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:08.644494          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:00:08.655495          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:08.655495          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:00:08.658495          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:08.658495          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:00:08.668495          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:08.668495          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:00:08.673496          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:08.673496          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:00:08.673496          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:08.673496          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:00:08.678496          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:08.678496          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:00:08.680496          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:08.680496          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:00:08.685496          ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Unknown exception
00:00:08.685496          F:\tinderbox\win-5.0\out\win.amd64\release\obj\VBoxAPIWrap\MediumWrap.cpp[2245] (long __cdecl MediumWrap::GetEncryptionSettings(unsigned short **,unsigned short **))}, preserve=false aResultDetail=0
00:01:21.061636 Watcher  ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={f30138d4-e5ea-4b3a-8858-a059de4c93fd} aComponent={MachineWrap} aText={The virtual machine 'Wibbler' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'D:\VBox\Wibbler\Logs\VBoxHardening.log'}, preserve=false aResultDetail=0
00:01:26.197930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'D:\VBox\Wibbler\XP Master.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.197930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'D:\VBox\Wibbler\D Drive.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.197930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'D:\VBox\Wibbler\E Drive.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.197930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'J:\WEDNESDAY2-C.VHD' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.198930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'D:\VBox\Minty\Linux Mint.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.198930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'D:\VBox\SL6\SL6.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.199930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'D:\VBox\FC17 64\FC17 64.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.199930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'D:\VBox\Win7-32\Snapshots/{43c2968a-7f30-4964-a3a6-0b3e0b390f6c}.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.199930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'D:\VBox\Win7-32\Win7-32.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.200930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'J:\WEDNESDAY2-DE.VHD' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.200930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'F:\VBoxish\Win8.1 thingie.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.200930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'D:\VBox\SL6p5\SL6p5.vhd' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.201930 main     ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'D:\VBox\Haiku v1 Alpha 4\Haiku v1 Alpha 4.vdi' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0
00:01:26.203930 Watcher  ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={0169423f-46b4-cde9-91af-1e9d5b6cd945} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0

Are there any good ideas floating around how I might get the virtual machines working again on this fully patched Windows 7 machine?

{^_^}

[mpack]

Please post a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[J.Dow]

Here are three logs. One failure for each of two disparate virtual machines (one WinXP and one Scientific Linux 6.5) and one success with the same WinXP machine.

I'll look through them myself to see if there is something that stands out. I am suspicious of a USB issue. But that's based on an old experience with VB. I have between 10 and 20 devices on several USB controllers and hubs. I brought up the VMs to give Software Defined Radios another go with virtual machines. They've failed miserably in the past, perhaps to poor handling of bulk transfers at high data rates.

--8<-- edit
Here is the error that eventually pops up from the GUI.
Failed to open a session for the virtual machine Wibbler.

The virtual machine 'Wibbler' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'D:\VBox\Wibbler\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Then I let it sit for a surprisingly long time and eventually the VM came up. I can restart the XP session OK. I'm stopping and restarting the VM. Much longer than former usual delays again. Failed to start. But waiting as after the above failure. Nothing. Trying again. Three errors all the same and a popup window.
Failed to open a session for the virtual machine Wibbler.

An unexpected process (PID=0x00003428) has tried to lock the machine 'Wibbler', while only the process started by LaunchVMProcess (PID=0x00002AC0) is allowed.

Result Code: E_ACCESSDENIED (0x80070005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}

Failed to open a session for the virtual machine Wibbler.

An unexpected process (PID=0x00003428) has tried to lock the machine 'Wibbler', while only the process started by LaunchVMProcess (PID=0x00002AC0) is allowed.

and the popup said:
Timed out after 600001ms waiting for child request #1 (CloseEvents)

where: supr3HardNTChildWaitFor what: 5 unknown Status 258 (0x102) (258) -
Unknown Status 258 (0x102)

And while I was copying that (and correcting for my slight dyslexia) the VM came up - it took about 4 or 5 minutes total at a guess.


Hm, that error message suggests there is something strange going on within the manager GUI. I note that the bare manager shows one VirtualBox.exe instances when I start the manager. Then it shows THREE virgualBox.exe processes a very careful ONE click on the start button within the manager GUI. And the errors suggest two or even all three of them are trying to spawn the VM.

If I kill ALL the VirtualBox.exe instances AND VBoxSVC.exe I still get three VirtualBox.exe come up for one manager. (And if I click off the last of the "Timed out" messages the VM is abruptly terminated.

OK, clicking off the first "Timed out" message takes down one of the VB.exe processes and spawns another instantly. I left the second message around. The VM seems to have come up just fine. Closing the second error gets me back to normal. I'll post a full log as a second attachment if I can. I can't so I'll post it as a follow-up message.

--8<--

Thanks for your time.

{^_^}

[J.Dow]

VBox.log mentioned above. I did NOT dismiss the "Timed out" message. Dismissing it instantly kills the VM session.

(It is the SECOND "Timed out" dialog, which renders oddly, which allows the VM to come up while it is still showing.)
{^_^}

[socratis]

More details may be available in 'D:\VBox\Wibbler\Logs\VBoxHardening.log'.

That, I haven't seen attached yet (although I have a pretty good suspicion of what its contents are going to be).

Having said thatre that, are you running Avira antivirus by any chance? Because your symptoms so far seem to be related to the Hardened Security issue. Take a look at this thread and see if anything familiar pops out. I would start at the end of the thread and work my way backwards...

Edit: "thatre" is not a word, "that, are" makes more sense...

[J.Dow]

You may have hit it in one. I am running Avira. I shall go check that thread ASAP.

{^_^}

[socratis]

The post from CornelisJ (viewtopic.php?f=6&t=67840&start=195#p347694) seems to work for people that have installed Avira. Take a look at it...

[J.Dow]

Nope, that is not the same problem. Besides, I have been successfully running with Avira through 5.0.8. The existing discussions seem to address 4.3 versions. I've been working with many versions well past that. I can't say all versions. I've skipped a few upgrades.

{^_^}

[socratis]

The way you're wording your answer, it seems that you assume this to be a VirtualBox issue, when in fact I believe it's an Avira issue, due to a recent Avira update. Did you try the remedy or you assumed it won't work?

[J.Dow]

Disabling my anti-virus is not a solution. And the discussion seems to indicate different problems than I am seeing.

And what is VirtualBox doing that gets it involved with the AntiVirus self-protection features? I have not given that a try because rebooting this machine shuts down too much of the infrastructure here. When I have that tried I will have to set it back to at least protect itself. (With HTTPS and POP3S or IMAPS the other protections are rather academic anyway.)

If the self-protection features specifically are the problem, then some analysis to indicate why the problem is not VirtualBox stepping in where places it has not business playing with is called for.

At least I have a sort of work around. Is anybody actually working with Avira to sort this problem out? Or are both sides sitting pointing at the other?

{o.o}

[loukingjr]

And what is VirtualBox doing that gets it involved with the AntiVirus self-protection features?

The reasons for VirtualBox's hardening feature has been explained ad nauseam in the forum.

At least I have a sort of work around. Is anybody actually working with Avira to sort this problem out?

That is something only the respective developers would know,

[J.Dow]

Actually I pointed my browser over to their help forum and found that Avira is working to solve the problem. They think they have the problem solved in their beta path. But it has not gotten out to distribution yet. I posted the sllightly less ugly workaround I discovered over there. We shall see what comes of it.

Meanwhile I'll hope that the two teams are working together. That usually results in a better fix.

Thanks for motivating me to dig around a little more than I had.

{^_^}

[loukingjr]

anytime