Windows host-only adapter creation fails due to slow background processing

[Jiri Hruska]

I was debugging why Xamarin Android Player could not prepare a VM for me and determined the failure to be in the host-only adapter creation, isolating the problem to this:

C:\Program Files\Oracle\VirtualBox\>VBoxManage.exe hostonlyif create
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "int __cdecl handleCreate(struct HandlerArg *,int,int *)" at line 66 of file VBoxManageHostonly.cpp

After some time spent in the debugger, I've found the real error to be CO_E_CLASSSTRING (Invalid class string), naturally returned by some CLSIDFromString() API call. Interestingly enough, the input GUID string contained garbage only.

Further debugging revealed a data race in VBoxNetCfgWinCreateHostOnlyNetworkInterface(). By the time RegQueryValueExW(..., "NetCfgInstanceId", ...) is called, the network device might still not be fully constructed by another process and this registry value might not be present yet. Because the result of this operation is effectively ignored, the program silently continues and the function fails only later due to the GUID being invalid.

A proof from Process Monitor - it took the system ~0.4 seconds more to write the value:

03:11:01.9426053	VBoxSVC.exe	15024	RegQueryValue	HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0018\NetCfgInstanceId	NAME NOT FOUND	Length: 144
03:11:02.3592881	svchost.exe	1140	RegSetValue	HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0018\NetCfgInstanceId	SUCCESS	Type: REG_SZ, Length: 78, Data: {F4CCBF3A-4C8B-4FE7-A659-725C3DF52E69}

Waiting in the debugger for a while before the RegQueryValueExW() call helped and I was able to create host-only network adapters fine.

Setting as priority minor because:

• it happened on a pre-release OS (Windows 10 preview build 10052)
• it happened on a pre-release VirtualBox (5.0.0_BETA1 r99371).

On the other hand, I submitted a ticket anyway because:

• the race is still a bug and can possibly crash the program, it might have been working with a little bit of luck only
• it seems the relevant VBox code has not been changed for the current beta
• I hear there was some refactoring done in Windows 10 regarding network adapters, this might show up later for more people

[hheimbuerger]

Nice find, this is probably the cause for a number of known issues with VirtualBox 5 (final) and Windows 10 build 10240 (essentially the RTM) in the Docker community.

Specially, this exact error occurs when docker-machine or boot2docker-cli are trying to create their host-only network.

Example issue on docker-machine: ​https://github.com/docker/machine/issues/1521

Can we upgrade this ticket a bit? I'm personally waiting for this fix and very hope it will make it into the VirtualBox 5.0.1 release.

[ScottRoberts]

I am experiencing the same issue. I can get host-only networking going if I manually specify the IP address of the interface in Windows. I have been using Vagrant-generated configs. I'll be trying the process by manually creating a guest in the VirtualBox interface later today.

VirtualBox 5.0 on Win10 release 10240

I would also appreciate escalation, as I think this is going to pop up frequently starting in about a week as the Win10 release rolls out.

[ScottRoberts]

I should note, this problem exists for versions prior to VirtualBox 5, as well. I tried latest 4.3 version late last week, and also tried 4.3.12, I believe, based on what I'd seen on other threads regarding VirtualBox/Win 10 host-only networking issues.

When setting up a guest, the adapter gets created but the guest process can't access the settings to set the IP address. This is consistent when running VirtualBox as administrator or as a regular user, and whether I start the Vagrant script in an elevated or normal shell.

[iggim88]

Please escalate priority for this ticket. The same problem occurs on Windows 10 RTM:

Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp

[dvanhees]

Agreed, please escalate priority for this ticket! Everyone experience problems with this, especially in combination with Vagrant. This issue opened 4 months ago and is still minor, but today Windows 10 rolled out so it should definitely be a major issue imho... :(

[nathanleclaire]

I can confirm that this issue is happening for me on a version of Windows 10 which I have downloaded today, Virtualbox 5.0.0r101573.

$ /c/Program\ Files/Oracle/VirtualBox/VBoxManage.exe hostonlyif create
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp

Escalating priority on this issue seems apropos as the Windows 10 release is hitting general availability and I know that this issue breaks some functionality on our project (Docker Machine) completely.

[mmoore]

I'm also getting this error on Windows 10. Virtualbox 5.0.0r101573 as well.

Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp

[Aleserche]

Windows 10 (64-bit) + VirtualBox-4.3.12-93733 (and also tried 4.3.10, 5.0.0, 5.0.1)

Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "int __cdecl handleCreate(struct HandlerArg *,int,int *)" at line 66 of file VBoxManageHostonly.cpp

[erdemece]

I have the same problem

windows 10 + vagrant + virtualbox 5

please help

[educdev]

Same problem on Windows 10 official release + vagrant + vbox 4.3. Please escalate priority.

[cre91]

Same problem here, Windows 10 with Vagrant and VirtualBox 5.

==> default: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp

[Jiri Hruska]

Fix suggestion (WTFPL license)

[Jiri Hruska]

Nice traffic here, looks like the Windows 10 upgrade rollout has started or something.

I'm sure there is a proper fix prepared on some internal branch already, but adding some suggested patch anyway to keep the hordes happy ;)

[Richy Rich]

Same problem here with Windows 10 Thnx 4 the Patch Yirkha, but how do we apply a patch?I can't find a wiki page about how to apply a patch.

Thanks in advance

[Aleserche]

Replying to Richy Rich:

Same problem here with Windows 10 Thnx 4 the Patch Yirkha, but how do we apply a patch?I can't find a wiki page about how to apply a patch.

Thanks in advance

​http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.patch.html https://www.virtualbox.org/wiki/Build_instructions

[Richy Rich]

Many Thanks!!! Working on in at as we speak. Can't revert back to Windows 8.1 due to installation problems of 8.1! Thanks Microsoft, nice job in providing us an option that doesn't work :-)

[dvanhees]

Replying to Richy Rich:

Many Thanks!!! Working on in at as we speak. Can't revert back to Windows 8.1 due to installation problems of 8.1! Thanks Microsoft, nice job in providing us an option that doesn't work :-)

Hi Richy, any chance you can upload it somewhere when the build is finished? I don't have the required tools to build it myself :(

[Richy Rich]

I'm having trouble installing all the dependencies for building vb described over here: https://www.virtualbox.org/wiki/Windows%20build%20instructions Seems to me they are a bit outdated. I will share the build if all works well :-)

[Jiri Hruska]

Don't hold your breath, guys. To build working drivers on x64 versions of Windows, one must have a valid code signing certificate (or run the machine in test-signing mode).

[educdev]

Replying to Richy Rich:

I'm having trouble installing all the dependencies for building vb described over here: https://www.virtualbox.org/wiki/Windows%20build%20instructions Seems to me they are a bit outdated. I will share the build if all works well :-)

Great stuff!

[Richy Rich]

Sorry guys, but I'm running into to much trouble installing all the dependencies on Windows 10.. We'll have to pray a test build will be publshed soon :-(

[Harkenn]

I am able to reproduce this issue merely by using the GUI to create a new host-only adapter

​http://i.imgur.com/B8Jwk4b.png

[bhouston]

Just chiming in here to suggest that getting a VirtualBox build that works on Windows 10 properly should be a priority. There is a large thread here on the vagrant github tracker about this particular error:

​https://github.com/mitchellh/vagrant/issues/6059

[bogdanus]

Agree with bhouston.

I cant start my (local) websites on which i was working on.

We NEED this update asap! +1

[tarruda]

Same situation here: Did a fresh windows 10 install and couldn't create the host-only interfaces to run the imported development appliances. Currently blocked on work, it seems I will have to rollback to windows 7 in order to work, though I would like to avoid that route if possible.

If a prebuilt binary with the fix isn't going to be released soon, is it possible to provide an appliance with the software required for building virtualbox? Setting up the development environment manually will take a long time and completely pollute my laptop with software(visual studio, sdks...) I won't use for anything else.

For me, even a workaround to create the interface would be nice. I wonder if there's a debugger I can use to attach and set breakpoint before RegQueryValueExW like Yirkha suggested.

[bhouston]

This bug has also broken boot2docker -- details here: ​https://github.com/boot2docker/boot2docker/issues/1015

[JaneFa]

Im using Genymotion and virtualbox don't working! Fix it asap PLEAE! :( :( :(

[MichalK]

Replying to JaneFa:

Im using Genymotion and virtualbox don't working! Fix it asap PLEAE! :( :( :(

Me too. Any combinations of Genymotion and VirtualBox versions not working, because of this E_FAIL (0x80004005) error. Everything through the yesterday Windows 10 update fom 8.1.

Please help ASAP.

[Michael Thayer]

Just wanted to point out that we are aware of this, even if we can't adjust our own priority based on user requests. (Of course if this breaks your professional work flow you should probably be on a support contract. If you have one with Docker or Genymotion you should probably be talking to them.) As always, all user contributions aimed at solving the problem - including workarounds, which often also provide useful information to developers - are welcome, though in this case I think that someone internal is actively working on this.

[bogdanus]

michael, we are glad to hear that someone internal is actively working on this.

While someone is working on it can you maybe tell us if there is a quick workaround to create host-only interfaces in VB?

[Michael Thayer]

Sorry, nothing I am aware of - I do not even have a Windows system, so I can't say very much about this myself. Hopefully one of the other ticket subscribers can help there.

[bhouston]

Replying to bogdanus:

michael, we are glad to hear that someone internal is actively working on this.

While someone is working on it can you maybe tell us if there is a quick workaround to create host-only interfaces in VB?

There is a workaround for vagrant -- basically do not use scripting in VirtualBox to setup the network. Do it manually. Details here: ​https://github.com/mitchellh/vagrant/issues/6059#issuecomment-126655918

[tarruda]

Replying to michael:

As always, all user contributions aimed at solving the problem - including workarounds, which often also provide useful information to developers - are welcome, though in this case I think that someone internal is actively working on this.

The person who opened the issue already posted a small patch with a fix, the problem is that the development environment for building virtualbox is very complicated to setup. Perhaps one of virtualbox windows developers could post a temporary build with the patch applied?

Yirkha also posted a workaround: Place a breakpoint in the RegQueryValueExW system call and wait on it with a debugger(WinDbg?)for a few seconds, which would avoid the race condition. Unfortunately I can't detail the steps to perform this workaround because I'm not a windows developer. I tried attaching to VBoxSVC.exe(while the GUI is running) with WinDbg and setting a breakpoint using bp advapi32!RegQueryValueExW but it didn't work(the breakpoint was never hit).

[tarruda]

Replying to bhouston:

There is a workaround for vagrant -- basically do not use scripting in VirtualBox to setup the network. Do it manually. Details here: ​https://github.com/mitchellh/vagrant/issues/6059#issuecomment-126655918

I think this workaround is only valid if you already had the host-only network created(such as when upgrading from a windows 7/8 installation that had virtualbox configured). Fresh windows 10 installs won't have that option.

[tarruda]

FWIW I managed to debug VBoxSVC.exe with WinDbg and waited in the debugger to avoid the RegQueryValueExW race condition. As Yirkha suggested, the interface is apparently created(both GUI and VBoxManage report success), but when re-entering the VBox GUI preferences(or VBoxManage list hostonlyifs) the interface is gone. This leads me to believe that the attached patch will not work as expected, so I rolled back my laptop to windows 7.

If this bug is not going to be prioritized anytime soon, then the virtualbox website needs an urgent update to reflect the lack of windows 10 support. In fact, what encouraged me to upgrade to windows 10 was the ​the press release paragraph(4th) stating that windows 10 is supported both as host and guest by virtualbox 5.

[Jiri Hruska]

Workaround app (see ticket comments)

[Jiri Hruska]

Hi again,

as said before, all workarounds are welcome, so I made a simple app to fix this and allow people to ruin their weekend working. It's essentially doing the same delay workaround already suggested, but without having to touch a debugger and therefore it might be appealing even to the poor Android and web developers out there :P

Download the attached file VBox-Win10-fix-14040.exe, right click, launch it as administrator and leave it running during the creation of the VM network. Some logs will be created in the same directory during VirtualBox service process activity, which might prove helpful in case there are problems.

With this tool running, I am able to do "VBoxManage hostonlyif create" without problems. The created adapter then appears fine both in "VBoxManage list hostonlyifs" and in the GUI, and I am able to communicate through it sucessfully with a Linux guest (Windows 10 RTM 10240 + all ZDPs, VirtualBox 5.0.0 r101573).

Good luck!

P.S. Never, NEVER execute files from some random guy on the Internet, and especially not elevated!

[MichalK]

Works with Windows 10 10240 + VirtualBox 5.0.0 r101573 + Genymotion 2.5.2.

Thank You Yirkha!!!,

Poor Android Developer

[educdev]

Thanks Yirkha, your fix also works in combination with vagrant!

[dvanhees]

It works! Thanks!

[zailic]

Thank you Yirkha, you save my weekend! Your fix works brilliantly on W10 + VirtualBox 5.0.0 r101573

[Aleksei]

This workaround helped me to solve the problem with boot2docker.
Thank you Yirkha!

[Lubu08]

Hi Yirkha!,

It don't work with xamarin android player+ Win 10 10240+VirtualBox 5.0.0

Help me!

Thanks you!

[tarruda]

Yirkha, thanks for the fix. Unfortunately for me I already rolled back my installation to windows 7 and can't afford to go through the installation process again anytime soon.

This is off topic but I must say I'm impressed by your debugging skills. It's not easy to spot race conditions like this, I wouldn't even know where to begin. Did you use windbg to break on windows API calls? For me I used process monitor(as per your suggestion) and got the stack trace at the time of the failed RegQueryValueExW call, then I set a breakpoint at the call instruction just before, which allowed me to avoid the race condition(again, just following your instructions) but for some reason it was not enough because the adapter disappeared as soon as I exited the network preferences.

Also, are you a virtualbox developer? If not, how did you manage to build virtualbox so quickly. I mean, did you just happen to have a virtualbox build environment? For me, it seemed very hard to setup a build environment based solely on the information at https://www.virtualbox.org/wiki/Build_instructions. I'm interested in any tips you have for hacking virtualbox in case I need to do so in the future.

One last thing, could you share the source code of the workaround you uploaded? I'm sure it has useful tricks for anyone interested in learning about windows development.

[RussEby]

Wow, Thank you very much Yirkha,

The fix worked like a charm. (Win 10, Vagrant, Virtualbox 4.3)

I wish I could buy you a coffee/beer/tea because you helped me huge.

Thanks again,

Russ

[Jiri Hruska]

Hi again, I'm glad to see my fix has helped some of you - thank you for your kind words.

@Lubu08: I'm sorry, I can't assist in troubleshooting much. Maybe if you provided an exact list of steps you've taken, uploaded the created log files (if any) to e.g. Pastebin, perhaps tested it also outside of the Xamarin app, ... - but that would be still mostly off topic here. It should be taken as a temporary solution and a proof-of-concept only, I'm sure a proper hotfix will come from the VirtualBox team soon.

@tarruda: Yes, this is also kind of off topic here, so just real quick:

1. Finding the root cause is described in the ticket description. No magic, just a lot of time spent finding the failing call. VirtualBox being open source helps.
2. I don't know why the adapter could disappear from the GUI. Some time ago I had to launch it as administrator (it seemed some API needed to be called elevated), but I was able to do everything without these tricks now. Sorry to hear you were close, but had to go through downgrading anyway.
3. I'm not a VirtualBox developer, I'm not affiliated with Oracle and I did not manage to build VirtualBox (not now, anyway). All what the workaround app does is it registers as a debugger for VBoxSvc.exe and lets the OS trigger it every time a process with that name is started. Then while controlling that process, if the command line is right, there is a RegQueryValueEx() call, for value "NetCfgInstanceId", from VBoxSvc.exe itself, it sleeps for 3 seconds. When you close the app, it unregisters again and everything should be back to normal.
4. Even if I decided that the world needs to see more hacky code, I currently can't - I left it on my work PC. But the tool does not do anything special really, everything needed is described on the Internet in articles like ​How to: Launch the Debugger Automatically and ​Writing a basic Windows debugger.

[bogdanus]

Running this fix + vagrant i am getting error. Do i something wrong?

---

There was an error while executing VBoxManage, a CLI used by Vagrant for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "ipconfig", "VirtualBox Host-Only Ethernet Adapter", "--ip", "10.10.10.1", "--netmask", "255.255.255.0"]

Stderr: VBoxManage.exe: error: The host network interface with the given name could not be found VBoxManage.exe: error: Details: code E_INVALIDARG (0x80070057), component HostWrap, interface IHost, callee IUnknown VBoxManage.exe: error: Context: "FindHostNetworkInterfaceByName(Bstr(pszName).raw(), hif.asOutParam())" at line 204 of file VBoxManageHostonly.cpp

[ForNeVeR]

I got the following message with docker-machine 0.3.1 (bundled with Kitematic):

STDERR: VBoxManage.exe: error: Code E_INVALIDARG (0x80070057) - One or more arguments are invalid (extended info not available)
VBoxManage.exe: error: Context: "RemoveRedirect(Bstr(ValueUnion.psz).raw())" at line 1766 of file VBoxManageModifyVM.cpp

The @Yirkha's workaround actually *has* fixed something (i.e. it no more halts on network interface creation), but there's another bug I think that still causes the whole virtual machine to fail.

[Wilson Dias]

ENVIRONMENT WINDOWS 8.1 (Hardware: Dell Vostro Notebook - 16GB Ram)

HOST: WINDOWS 8.1 and VirtualBox 4.3.30-101610 Guest: Rac1 - Oracle Linux 6.6 - Oracle enterprise 12c Guest: Rac2 - Oracle Linux 6.6 - Oracle enterprise 12c Status: OK no issues

NVIRONMENT WINDOWS 10 (Hardware: Dell Vostro Notebook - 16GB Ram) HOST: Windows 10 and VirtualBox 4.3.30r101610

(did the upgrade from win8.1 to win10. No application where installed on win10)

Guest: Rac1 - Oracle Linux 6.6 - Oracle enterprise 12c Guest: Rac2 - Oracle Linux 6.6 - Oracle enterprise 12c Status: Linux and the Oracle Rac run in RAC1 and RAC2 but have problems accessing the internet via RAC1. Thru RAC1 Enterprise Manager Express run normally but not from RAC2. Oracle SQL Developer installed on the HOST does not access Oracle in RAC! Or RAC2.

This environment was all working when the host was Windows 8.1

Also I get the error: Error Message after updated to win10:

C:\Program Files\Oracle\VirtualBox>vboxmanage hostonlyif create 0%... Progress state: E_FAIL VBoxManage.exe: error: Failed to create the host-only adapter VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended in fo not available) VBoxManage.exe: error: Context: "int cdecl handleCreate(struct HandlerArg *,in t,int *)" at line 66 of file VBoxManageHostonly.cpp

[Jiri Hruska]

Source code of the workaround app: ​VBox-Win10-fix-14040.cpp

But never compile files from some random guy on the Internet, it is known it can hack your compiler and take over your hardware. Heck even viewing the file can crash your Chrome and send your credit card details to China!!1

[Jiri Hruska]

Workaround app for 32-bit systems (untested!)

[METEMEDO]

With the VBox-Win10-fix-14040-x86.exe I'm able to add the network in the VBox's preferences, but as soon as I press ok or close the window, it disappears.

[mortos]

Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 70 of file VBoxManageHostonly.cpp

Under Win 10 Pro x64, tried with both VBox 4.3.30-101610 and 5.0.0-101573, the workaround program got flagged by my AVG but after making an exception and running it didn't work, it indeed allowed me to create new adapters but then the machines will power off themselves with multiple VBox interface errors, I guess I'm just gonna wait.

[bskim45]

Perfectly works on windows10 x64, virtualbox 5.0.0 r101573. Thanks Yirkha!

[Galt]

I solved this problem in very simple way:

1)Go to the folder with virtualbox
2)Right click on VirtualBox.exe and set compatibility with windows 7 or windows 8.

Now virtual hosts added and not dissappeared after close window. This fix works with Genymotion 2.5.3 + VirtualBox 4.3.28. I think it able to work in VirutalBox 5.0.+
Good luck!

[michaln]

A test build is available at https://www.virtualbox.org/download/testcase/VirtualBox-5.0.1-101902-Win.exe . This should fix the host-only interface creation problem by introducing a 5-second timeout when querying the registry key. We would appreciate feedback (i.e. does it fix the host-only interface creation errors or not, is the timeout long enough).

Please note that since this is a test build, it was not fully tested and might introduce problems unrelated to the issue at hand.

Also please keep in mind that Windows 10 is not a supported host OS for any VirtualBox version at this point. We feel sorry for anyone who got themselves into trouble by upgrading their host OS without thinking, but please understand that paying customers always get priority and fixing public tickets can only be done on a best-effort basis.

[bhouston]

Thanks so much michaln. Trying it out now!

The official Oracle VB 5.0 press releases did mention Windows 10 support though:

"The 5.0 release supports the latest guest or host operating systems including: Mac OS X Yosemite, Windows 10, Oracle Linux, Oracle Solaris, other Linux operating systems, and legacy operating systems."

Source: ​https://www.oracle.com/corporate/pressrelease/oracle-vm-virtualbox-5-070915.html

[bhouston]

Micharln, your build works on my machine where as the previous VB release didn't. Thank you!

It is too bad that the only way to get Commercial support is via contacting Oracle to negotiate a Premium Support contract. Usually independent developers and small companies look for simpler options, such as a price per seat that one can just buy using a credit card.

[mortos]

Thanks michaln. Works flawlessly!

[bskim45]

By the way, those users of genymotion, try new release 2.5.3 from genymotion website. If it doesn't helps, try uninstall vbox and genymotion and reinstall it.

[daur88]

For those who's facing troubles with VirtualBox being unable to find a network adapter during Vagrant boot, try configuring the adapter via standard Windows Network and Sharing Center and commenting out corresponding instructions in your Vagrant config.yaml file.

[ForNeVeR]

@michaln thank you! That version has fixed my problems with docker-machine.

[michaln]

Thanks for the feedback!

Yes, the press release is unfortunately inaccurate; VirtualBox 5.0 will support Windows 10, but 5.0.0 does not (which is why Windows 10 is not listed in the manual).

This is not a place to discuss VirtualBox licensing -- the forum is. At any rate, it's not terribly relevant because it doesn't change the fact that Windows 10 is not an officially supported host OS yet (and that applies to paying customers just the same).

It is unfortunate that Microsoft made Windows 10 available on MSDN only after beginning to offer upgrades to end-users. Users started upgrading before developers had a chance to do anything. In the end, Windows users suffer but again, discussing Microsoft's policies here is pointless.

[p060477]

hi!

i've problems in network -bridge- win 10 host win xp guest and also i get no sound from the videos..and also i'm not able to reproduce video in flash player on youtube.com etcc.. with every browsers, ie, firefox,chrome with win 8.1 as host no problems

how can i solve?

[michaln]

p060477: You can not solve it by spamming a completely unrelated ticket. Please do not do that. It's not going to help you and it harms everyone else.

[diegofersan]

Hello, fix exe doesn't work for me.

FULL LOG

13:57:27.660 | --------         | Logging started
13:57:27.660 | VboxFix          | hAdvapi32 = 774E0000, pRegQueryValueExW = 774FED60
13:57:27.660 | Main             | Executing subprocess "C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe" -Embedding
13:57:27.661 | Main             | CreateProcess() failed (50).
13:57:27.661 | --------         | Logging stopped

Thanks

[Jiri Hruska]

(50 is ERROR_NOT_SUPPORTED, that's very weird.) Anyway, you should avoid the hacks now and rather try out the VirtualBox testbuild provided by the staff - see comment #55 above.

[jstangroome]

Hi michaln,

Regarding the new 5sec timeout before reading the registry key, is there perhaps a more appropriate mechanism to know when the information required will be available?

I'm not very familiar with this area of the Windows API but perhaps the code could poll SetupDiGetDeviceRegistryProperty for the SPDRP_INSTALL_STATE property and wait until the result is InstallStateInstalled and not InstallStateFinishInstall.

Or maybe call NdisReadConfiguration with the "NetCfgInstanceId" keyword instead of reading the registry key directly?

Just ideas.

Regards,

Jason

[michaln]

The 5-second timeout was a suggestion from Microsoft. No, it didn't sound terribly robust to me either, but it seems to do the trick.

[diegofersan]

Replying to michaln:

Thank you so much. I'm still having issues. Every time that I close Virtualbox GUI I need to run compatibility solution.

At least I can come back to work. Thanks again. :-)

[emanuelhborges]

I would like to add another trouble maker, in my case was Kaspersky 2015. After uninstall I was able to install Host-Only and run Genymotion.

[mortos]

Just wanted to give some feedback of the test build, I don't really know if this is a weird case or it's happening to anyone else, but I'm getting:

​https://cloud.githubusercontent.com/assets/2492303/9083846/624112c0-3b76-11e5-8728-981a3d3b366e.JPG and ​https://cloud.githubusercontent.com/assets/2492303/9083812/18108c30-3b76-11e5-9be5-be911585b50f.png

each time I start VM's after I have shutdown my system, running the test build setup and selecting repair seems to fix the problem for that session.

Hope this helps someone.

[michaln]

Just briefly:

Yes, Kaspersky is known to cause nasty problems, but that's something you need to bring up with them; it's not something we can fix. It's entirely unrelated to this ticket at any rate.

We've seen the "cannot rename this connection" dialogs and they should be harmless, certainly there should be no need for reinstalling. The dialog only shows up when creating 2nd or further interface. It's being worked on. (And that is related to this ticket.)

[rodrigoscna]

@daur88 How do I do what you suggested on #comment:60?

[Phalangion]

I was able to workaround by setting the following .exe's to Windows 8 compatibility mode:

• Virtualbox.exe
• VBoxManage.exe
• VBoxHeadless.exe

Doing just Virtualbox.exe as recommended by #comment:54 does not work. With all 3, though, I was able to start up VMs without any issues, or needing to run the fix.exe.

[Riebling]

Tried test build ending in 101902 and had success creating the network adapter once, but after deleting all host-only network adapters and trying again, it failed with the familiar error

Code E_FAIL (0x80004005)

Didn't work with test build version 5.0.x revision 101957 for me, either. Hoping there's a more robust fix enroute, since the manual workarounds don't really help when the whole purpose of using Vagrant is to automate everything with scripting.

Windows 10 Home (64 bit) VirtualBox 5.0.1r101957 and sometimes 5.0.1r101902 Vagrant 1.7.4

[iamjsed]

Replying to Phalangion:

I was able to workaround by setting the following .exe's to Windows 8 compatibility mode:

• Virtualbox.exe
• VBoxManage.exe
• VBoxHeadless.exe

Doing just Virtualbox.exe as recommended by #comment:54 does not work. With all 3, though, I was able to start up VMs without any issues, or needing to run the fix.exe.

This works for me! Thanks for sharing!

[devangmehta123]

I just wanted to add that the test build has fixed my issue. I am using virtualbox in combination with vagrant and I then get a warning related to guest additons and shared folders but that is a vagrant issue, not a virtualbox issue at this stage.

The only caveat in this is that I have to run my powershell (and hence vboxmanage and vagrant) with elevated privileges to make it work. That wasn't the case previously.

It is a mild annoyance which hopefully will be fixed with the proper release.

[Linker]

Hi I have applied the Yirkha fix and tried some new test builds like 5.0.1r102010 but unfortunately none of them fixed my problem , still genymotion can not create its infrastructure and problem exist in creating Host Only Networks . When I used Yirkha fix it says that VB created Host Only Adapter but when I close window and reopen it , it has gone .

Is there any hope that we have genymotion and Virtual box working together in Windows 10 ? Working with Google's Virtual Devices is pain in the ... !

Any other workaround would be appreciated !

[nathanleclaire]

I can confirm that the latest VirtualBox test build (102010) has fixed this issue for me! (Docker Machine v0.4.0 on Windows 10)

[jstangroome]

@michaln: regarding your previous comment: "It is unfortunate that Microsoft made Windows 10 available on MSDN only after beginning to offer upgrades to end-users. Users started upgrading before developers had a chance to do anything."

You may like to know that Windows 10 was made available to developers, etc in advance via ​https://insider.windows.com/ instead of MSDN.

I know it is not how Microsoft has historically handled new Windows releases but it would be worth registering if you would like early access to future releases that could impact VirtualBox.

[michaln]

jstangroome: Sorry to disappoint you but there's no way Oracle developers can sign up for the Insider program as individuals and use it for work. The license that Microsoft forces users to sign is simply not compatible with Oracle's policies (and there's no point arguing about that, so please don't).

So I'll repeat: If it's not on MSDN, we can't use it, and this time Microsoft was way behind with MSDN. Why Microsoft charges thousands of dollars for MSDN licenses and then makes MSDN subscribers wait is not something we can explain. Microsoft simply changed their release process too much and didn't quite think things through.

Too late to discuss this now really, and next time around it will be probably different again anyway.

[michaln]

Linker: I'm sorry to say that your problem sounds a bit different. I will also point out that Oracle cannot and will not support Genymotion products (the same goes for docker, vagrant, etc.). What that means in practice is that if you complain about Genymotion not working, you more or less guarantee that we will ignore it -- you need to complain to Genymotion instead. But if you take Genymotion out of the picture and explain what it is exactly that's not working with VirtualBox then we're certainly interested.

Notice that this ticket mentions an Android emulator but the bug report is strictly about VirtualBox. That is how it should be.

[gregor]

I installed the latest test build of VirtualBox (102010) on a fresh installation of Windows 10 final (10.0.10240), but still have issues with it. The creation of host-only adapters works without getting any error messages (even without using Yirkha's workaround utility). I can also confirm that the adapters are getting created and appear in Device Manager. Unfortunately, after closing the preferences dialog and reopening it, all host-only adapters are gone. I am also not able to assign host-only adapters to any VM as the Network Adapter "Name" drop down in the VM's settings dialog is empty. Starting VirtualBox with elevated privileges or in compatibility mode does not help either.

[kouik]

I can't work anymore ... Spent 2 days trying all your solutions, nothing works.

That sucks like hell.

[kouik]

There are some strange things i've noticed since i've update to windows 10.

When I do the vagrant up, Vagrant stop on the step ==> default: Clearing any previously set network interfaces... and a window pop-up from Windows saying that the connection cannot be renamed, and i can only click OK. The related informations about this generic Windows message is the following : ​https://support.microsoft.com/en-en/kb/269155

So, i suspect the windows update to have forgot some informations about the network card in my registery. On each vagrant up, I can see in my devices manager a new network device created, but the strange thing is that if I uninstall all of them, then run a vagrant up again, the name of the device created will be VirtualBox Host-Only Ethernet Adapter #4.

Why do the first adapter created always start by #4 ?

Another strange thing i've notice : Let's admit i've just uninstalled all the VirtualBox Host-Only Ethernet Adapters in devices manager. In VirtualBox, i right click the box that couldn't properly start, then settings, then network, then bridge access in the first dropdown, then i open the second dropdown, and this is what i see listed there :

• Intel(R) Internet Connection (2) I212-V
• VirtualBox Host-Only Ethernet Adapter #3
• Microsoft Kernel Debug Network Adapter
• VirtualBox Host-Only Ethernet Adapter #2
• VirtualBox Host-Only Ethernet Adapter

Wow !? Is this normal ? I can't see any #0, #1, #2 or #3 in devices manager, devices manager create items starting by #4, and virtual box list thoses ones. Wtf ...

Any idea guys ?

[kouik]

I have changed the IP of my vagrant project because i suspect to be attached to a ghost card stored somewhere on my computer, and is blocking the creation of the network card with the given IP because it is yet exist.

Changed

config.vm.network :private_network, ip: "192.168.50.4"

To

config.vm.network :private_network, ip: "192.168.56.4"

in my Vagrantfile.

Now the VM boots as expected.

Any idea on how to clean the ghost network cards number 0 to 3 on my computer ? Thanks a lot.

[kouik]

Another strange debugging attempt :

Running Windows 10 Home, VirtualBox 5.0.1, Vagrant 1.7.4 and i'm trying to vagrant up a project based on VVV (a vagrant box and toolset).

• Reinstalled Virtualbox
• Rebooted
• Removed any VirtualBox Host-Only Ethernet Adapter in devices managers
• Added Windows 7 compatibility mode to Virtualbox.exe, VBoxManage.exe, VBoxHeadless.exe, and UAC rights to vbox.

Now i tried to run my project, and i've needed to run vagrant up 4 times to get the VM finally booted.

First vagrant up

00:00:00.380457 File system of 'C:\Users\Thomas\VirtualBox VMs\vagrant_default_1439418635929_93763\Snapshots' (snapshots) is unknown
00:00:00.380465 File system of 'C:\Users\Thomas\VirtualBox VMs\vagrant_default_1439418635929_93763\box-disk1.vmdk' is ntfs
00:00:00.504390 VMSetError: F:\tinderbox\win-rel\src\VBox\Main\src-client\ConsoleImpl2.cpp(5244) int __cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool); rc=VERR_INTERNAL_ERROR
00:00:00.504406 VMSetError: Interface ('VirtualBox Host-Only Ethernet Adapter') is not a Host-Only Adapter interface
00:00:00.504907 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Interface ('VirtualBox Host-Only Ethernet Adapter') is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR)}, preserve=false aResultDetail=0
00:00:00.505024 Console: Machine state changed to 'PoweredOff'
00:00:00.512760 Power up failed (vrc=VERR_INTERNAL_ERROR, rc=E_FAIL (0X80004005))

Second vagrant up

00:00:01.446658 PcBios: Using LAN ROM 'C:\Program Files\Oracle\VirtualBox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/PXE-Intel.rom' with a size of 0xc000 bytes
00:00:01.700689 SUP: Loading failed for VBoxDDR0.r0 (C:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0) rc=VERR_LDR_MISMATCH_NATIVE
00:00:01.700819 PDMLdr: pdmR3LoadR0U: pszName="VBoxDDR0.r0" rc=VERR_LDR_MISMATCH_NATIVE szErr="SUPR3LoadModule: supLoadModule returned VERR_LDR_MISMATCH_NATIVE"
00:00:01.700855 VMSetError: F:\tinderbox\win-rel\src\VBox\VMM\VMMR3\PDMLdr.cpp(724) int __cdecl pdmR3LoadR0U(struct UVM *,const char *,const char *,const char *); rc=VERR_LDR_MISMATCH_NATIVE
00:00:01.700861 VMSetError: Cannot load R0 module C:\Program Files\Oracle\VirtualBox/VBoxDDR0.r0: SUPR3LoadModule: supLoadModule returned VERR_LDR_MISMATCH_NATIVE
00:00:01.700895 VMSetError: F:\tinderbox\win-rel\src\VBox\Devices\Bus\DevPCI.cpp(2160) int __cdecl pciR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_MODULE_NOT_FOUND
00:00:01.700961 VMSetError: Failed to register ourselves as a PCI Bus
00:00:01.700985 PDM: Failed to construct 'pci'/0! VERR_MODULE_NOT_FOUND (-610) - Module not found.
00:00:01.705324 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Cannot load R0 module C:\Program Files\Oracle\VirtualBox/VBoxDDR0.r0: SUPR3LoadModule: supLoadModule returned VERR_LDR_MISMATCH_NATIVE (VERR_LDR_MISMATCH_NATIVE).
00:00:01.705399 Failed to register ourselves as a PCI Bus (VERR_MODULE_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:01.705824 Console: Machine state changed to 'PoweredOff'
00:00:01.745224 Power up failed (vrc=VERR_MODULE_NOT_FOUND, rc=E_FAIL (0X80004005))

Third vagrant up

00:00:01.227386 PcBios: Using LAN ROM 'C:\Program Files\Oracle\VirtualBox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/PXE-Intel.rom' with a size of 0xc000 bytes
00:00:01.237860 SUP: Loaded VBoxDDR0.r0 (C:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0) at 0xfffff80074230000 - ModuleInit at 0000000000000000 and ModuleTerm at 0000000000000000 using the native ring-0 loader
00:00:01.237868 SUP: windbg> .reload /f C:\Program Files\Oracle\VirtualBox\VBoxDDR0.r0=0xfffff80074230000
00:00:01.499657 SUP: Loading failed for VBoxDD2R0.r0 (C:\Program Files\Oracle\VirtualBox\VBoxDD2R0.r0) rc=VERR_LDR_MISMATCH_NATIVE
00:00:01.499765 PDMLdr: pdmR3LoadR0U: pszName="VBoxDD2R0.r0" rc=VERR_LDR_MISMATCH_NATIVE szErr="SUPR3LoadModule: supLoadModule returned VERR_LDR_MISMATCH_NATIVE"
00:00:01.499799 VMSetError: F:\tinderbox\win-rel\src\VBox\VMM\VMMR3\PDMLdr.cpp(724) int __cdecl pdmR3LoadR0U(struct UVM *,const char *,const char *,const char *); rc=VERR_LDR_MISMATCH_NATIVE
00:00:01.499806 VMSetError: Cannot load R0 module C:\Program Files\Oracle\VirtualBox/VBoxDD2R0.r0: SUPR3LoadModule: supLoadModule returned VERR_LDR_MISMATCH_NATIVE
00:00:01.499835 AssertLogRel F:\tinderbox\win-rel\src\VBox\Devices\PC\DevAPIC.cpp(2366) int __cdecl apicR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *): RT_SUCCESS_NP(rc)
00:00:01.499853 VERR_MODULE_NOT_FOUND (-610) - Module not found.
00:00:01.499864 PDM: Failed to construct 'apic'/0! VERR_MODULE_NOT_FOUND (-610) - Module not found.
00:00:01.503853 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Cannot load R0 module C:\Program Files\Oracle\VirtualBox/VBoxDD2R0.r0: SUPR3LoadModule: supLoadModule returned VERR_LDR_MISMATCH_NATIVE (VERR_LDR_MISMATCH_NATIVE)}, preserve=false aResultDetail=0
00:00:01.504347 Console: Machine state changed to 'PoweredOff'
00:00:01.536964 Power up failed (vrc=VERR_MODULE_NOT_FOUND, rc=E_FAIL (0X80004005))
00:00:01.804825 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={The object is not ready}, preserve=false aResultDetail=0

4th vagrant up (this time it worked, i can successfully access my websites on my VM, end of log doesn't seems to show any error)

00:00:07.222407 VMMDev: Guest Additions information report: Version 4.3.10 r93012 '4.3.10_Ubuntu'
00:00:07.222454 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x00053100 (64-bit)
00:00:07.222515 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:00:07.222581 VMMDev: Guest reported fixed hypervisor window at 00000c00000 (size = 0x800000, rc = VINF_SUCCESS)
00:00:07.222813 VMMDev: Guest Log: vboxguest: major 0, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
00:00:07.965411 NAT: IPv6 not supported
00:00:07.968080 NAT: DHCP offered IP address 10.0.2.15
00:00:07.968876 NAT: DHCP offered IP address 10.0.2.15
00:00:09.882385 NAT: Link up
00:00:21.809390 NAT: DHCP released IP address 10.0.2.15
00:00:21.899532 NAT: DHCP offered IP address 10.0.2.15
00:00:21.899697 NAT: DHCP offered IP address 10.0.2.15
00:00:26.867638 NAT: Link up

Seriously pls guys ... we need some fixes ...

Hope it will help to get it fixed quicker. Thanks by advance.

[kouik]

Guys,

It really looks like a Firewall issue. Now that i have successfully started my VM once, i don't get errors anymore, and my VM get successfully booted.

I think that something on Windows, like a Windows firewall is blocking VirtualBox from loading some files but create some exception rules to allow it to be accessed, but this take to much time to do, and VB crash without waiting enough longer for the rule to be created. So, if we restart again with a vgrant up, we will crash again facing a new blocking file.

SOLUTION : Just be rudest than VirtualBox, and simply execute vagrant up until it works !

[kouik]

Addition : Don't use VirtualBox 5.0.0 or 5.0.1 with Windows 10. Even if you can pass the first issue, you will then notice than symlinks on the VM do not work with this VB version. Check that issue for more informations : https://www.virtualbox.org/ticket/14434

So, i rolled back to Virtual 4.3.30, ran vagrant up 4 times again, and my VM successfully booted again. I can now reboot and use the VM with one single vagrant up, i get no more errors messages, and symlinks on the VM are properly working.

What a headache...

[markenson]

Hi all!

The host only network feature over windows 10 is working fine to me at the version 5.0.2 [102096](​http://download.virtualbox.org/virtualbox/5.0.2/VirtualBox-5.0.2-102096-Win.exe).

[Frank Mehnert]

Thanks for the feedback! Indeed, the fix is part of VBox 5.0.2.

[gregor]

I can't confirm that this is fixed with version 5.0.2-102096 and Windows 10.0.10240 (final). Although I am able to create host-only adapters in the preference section without errors, but they all disappear when reopening preferences. None of the adapters can be assigned to a VM, as they do not appear in the adapter drop-down list (see screenshot https://www.virtualbox.org/attachment/ticket/14040/vbox5-win10-cant-assign-adapters.png). I can see the adapters in Windows device manager though.

[gregor]

Screenshot: empty host-only adapters drop-down

[michaln]

Gregor: Your problem is clearly different and either completely unrelated to this ticket (unable to create host-only adapters) or at best very tangentially related. Please create a separate ticket.

As it is, you're only spamming lots of users who had trouble with host-only adapter creation but don't have problems now. By mixing separate issues, you are also making problems harder, not easier, to fix.

[gregor]

@michaln:

I am finally able to create host-only adapters (even without Yirkha's utility), but they immediately disappear when I reopen the preferences dialog. So essentially, the adapters are not created/registered properly in VirtualBox. The same issue has been described several times in this ticket by other users already. As discussed, I have created the following follow-up ticket for this issue: https://www.virtualbox.org/ticket/14437

[Frank Mehnert]

The VERR_LDR_MISMATCH_NATIVE problem should be fixed with the most recent Windows test build (>= 102223).

[mjordan79]

For me, the bug is still present. I have already attached a log.

[BlueRaja]

I'm having a very similar error, I'm not sure if it's related: #14545

[Sae1962]

Hello! Is there a working version released for Windows 10? I checked the update page and found out that version 5.0.4 is still the latest for 64-bit processors, but it seems not working. Is there a workaround for Windows 10 concerning the error? Our project had been in an unclear state, but the kick-off will be next week. So, it would be nice to get a solution for Windows 10 to work with VMBox. Currently, I have two VMs installed, but both are "(=) Inaccessible".

[Sae1962]

Creating process for virtual machine message

[travassos]

Hi,

I still got the problem. When I try to install the vbox 5.0.10 on windows 10 I got this

pdateHostOnlyInterfaces: VBoxNetCfgWinUpdateHostOnlyNetworkInterface failed, hr = 0xe000020b
CreateHostOnlyInterface: calling VBoxNetCfgWinCreateHostOnlyNetworkInterface
Querying NetCfgInstanceId failed (0x00000000)
CreateHostOnlyInterface: VBoxNetCfgWinCreateHostOnlyNetworkInterface returns 0x80004005
CreateHostOnlyInterface: VBoxNetCfgWinCreateHostOnlyNetworkInterface failed, error = 0x80004005
CreateHostOnlyInterface: Almost done...
CreateHostOnlyInterface: Returns success (ignoring all failures)

I've looked in the registry and the Key NetCfgInstanceId exists in all network interfaces.

The error seems to be where the patch has been done but is not working yet.

Best regards

[travassos]

Hi,

Sorry guys i've found the problem. The Kaspersky Internet Security was the cause of the problem. I had to uninstall it, install virtualbox and then install again KIS.

Now all is working great. You can close this ticket!

Best regards

[Francis Hilaire]

Hi,

I found a solution preventing you to uninstall Kaspersky.

You have to install manually the VirtualBox Network drivers. You can found those drivers here :

C:\Program Files\Oracle\VirtualBox\drivers\network

There is two folders, go inside both of them and right click install on the *.inf files.

Now the installation of hosts only virtual networks adapters should be nice but don't boot up. You have to manually install a new service on your "VirtualBox Host-Only Network" adapter.

• go to the network adapters list
• right click on this network adapter choose "Properties"
• click on the "Install..." button and add a service
• choose The Manufacturer "Oracle Corporation" and the network service named "VirtualBox NDIS6 Bridged Networking driver".
• Validate all the windows, and all should be OK.

Sincerly,

[brazorf]

I'm still having this issue with Windows 10 and VirtualBox 5.2.18.

What i do

• disable avast antivirus
• disable zonealarm firewall
• launch the installer

The install seems to work apparently, but after it closes i have no adapters in my network.

What i can see, since i keep the device manager opened during the install process, is that for 3 times the installer creates the adapter (it shows up with a yellow warning sign), then deletes it, then creates it again. At the end, no device is added.

I've tried every single fix ive found in this thread, and on the internet. This is the output when i try to create the adapter from an elevated prompt:

C:\Windows\system32>"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" hostonlyif create
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Querying NetCfgInstanceId failed (0x00000002)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 94 of file VBoxManageHostonly.cpp

Please advice.