Windows 10/ 1511 VM aborts on start - VERR_INTNET_FLT_I

[dermoritz]

Yesterday Windows 10 upgraded to 1511 and now my VM (Enterprise Linux) aborts the start with:

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).


Fehlercode:
E_FAIL (0x80004005)
Komponente:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

From the log:

00:00:03.022449 IntNet#0: szNetwork={HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter} enmTrunkType=3 szTrunk={\DEVICE\{879CB852-1BAA-4E18-8857-A11DED40FC2E}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:03.022511 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DrvIntNet.cpp(1753) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.022531 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter'
00:00:03.022572 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DevE1000.cpp(7715) int __cdecl e1kR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.022576 VMSetError: Failed to attach the network LUN
00:00:03.022588 PDM: Failed to construct 'e1000'/1! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:03.029518 GIM: HyperV: Resetting MMIO2 regions and MSRs
00:00:03.158571 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).
00:00:03.158664 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:03.159064 Console: Machine state changed to 'PoweredOff'
00:00:03.197015 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))
00:00:03.410313 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:03.410344 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={7303a66d-433b-25a4-f9a8-fcadf87e0c2a} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0

What i did so far (nothing helped):
- uninstalled reinstalled VBox (currently 5.0.11 pre-release)
- tried to uninstall/reinstall network adapter drivers (from another post, but in my case it is no bridge adapter but "NAT")
- tried to set all VBox executables to compatibility mode (Win 7 and 8) and set "run as administrator"

So do you have any further tips?

thanks in advance

[michaln]

So do you have any further tips?

Besides "don't use unstable Windows builds if you want to get work done"? Not yet, sorry.

[dermoritz]

what does unstable mean? it was automatically downloaded and installed on re-start. I have normal Win 10 pro (no early adopter stuff)
Besides this. I tried to create a new machine with ubuntu. This one is working fine. So the problem must be caused by some setting. But reproducing the network setting didn't help.

[mpack]

Isn't it obvious what unstable means? I never leave automatic updates enabled, hence my PC is stable: therefore it does the same thing every day, until I tell it to do something else.

I suspect that Michal is exasperated by this new development model for Windows 10 - push updates out as fast as possible, let the muggles test it and complain to the wrong people when it breaks.

[frank]

Is this related to ticket 14832?

[dermoritz]

Yes! you saved my day (and yesterday ).
The workaround stated there works:
You have to enable "VirtualBox NDIS6 Bridged NetworkingDriver" in "VirtualBox Host-Only Ethernet Adapter" 's properties.

[JustinH]

For respect to the OP, it seems the response was overly harsh. Is it somehow unreasonable to use released software? Regardless of your opinion of it, it is released to the public. Should we think that all released versions of VBox are ‘unstable’ and not use it? Maybe there is a real issue with that latest released build of W10 that VBox needs to react to?

Regards,
Justin

[mpack]

Should we think that all released versions of VBox are ‘unstable’ and not use it?

Yes, exactly. At least not if you care about reliability more than having the latest new thing. VirtualBox is a special case for me because I'm pretty much required to be up to date, but in general I would apply the same principles to all software (and all other technology for that matter). Windows was not being singled out for special treatment.

[frank]

In the meantime Microsoft also forces normal users to upgrade to build 10586 so need to handle this problem.

[willemd]

I have the same problem. Since the latest Windows Update, the host only NIC doesn't work anymore in my VMs. Turning NDIS6 on in Network Properties does not help. Will there be a bugfix for this problem?

[thunderspb]

I have the same problem. Since the latest Windows Update, the host only NIC doesn't work anymore in my VMs. Turning NDIS6 on in Network Properties does not help. Will there be a bugfix for this problem?

Don't use NDIS6, it's known bug with this driver, you can install old NDIS5 driver which will solve this issue.

Uninstall Virtualbox and reinstall it with parameter

Code: Select all

C:\Users\Me\Downloads>VirtualBox-5.0.10-104061-Win.exe -msiparams NETWORKTYPE=NDIS5

[Anvish]

Hi I had same Problem and here how I solved it... "THIS IS HOW I SOLVED THIS, IT MAY NOT WORK FOR YOU. BUT PLEASE GIVE A CHECK "

Am using Virtual box on Windows 10.

issue1.
Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Code d'erreur : E_FAIL (0x80004005)
Composant : Console
Interface : IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
Issue 2.
For me virtual box network adapter was not available

Solved as below
Uninstall and downloaded new version [reinstalled].
then able to find network adapter in Control Panel\Network and Internet\Network Connections [issue 2 addressed]. Still issue 1 persist, then.
Go to properties of network adapter -> Search for "Virtual box NDIS bridged networking driver" under tab Networking and column "this connection uses the following items" ->
Mark the check box if unchecked -> give ok -> then disable network adapter -> and enable the same.