Windows 10 TP network bridge causes major fault

[dhrida]

This is similar to ticket number 13912. When VB is installed in the latest beta of Windows 10 technical preview, the host machine halts upon restart. The only thing working is the mouse, nothing else works.

The computer works fine if the network cards are disabled in Windows, but this leaves end users unable to access any network.

[klkvsk]

Can confirm, just ran into this issue on freshly installed Windows 10 TP build 9926 with latest updates installed. First after VirtualBox installation all network interfaces stopped working (although my wifi was showing as "connected"). Then after reboot I got black screen with only mouse pointer on it.

If you too stuck with black screen, here's way to fix your computer:

1. boot in safe mode WITHOUT networking
2. enable Windows Installer service to work in safe mode, in cmd:

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\MSIServer" /VE /T REG_SZ /F /D "Service"
net start msiserver

3. Win+X, "Programs and Features", uninstall VirtualBox

[jaitaiwan]

I can confirm that I've also seen what appears to be the same issue. I've listed out the replication steps on the microsoft forum: ​http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_devices/virtualbox-causes-start-up-failure-and-bsod/7ec70dbc-954c-4a08-99ce-8ef21ed9a092?tm=1427031595500

[shawngates]

See this thread

Windows 10 TP 10041 - if have virtualbox with bridged networking on windows 10 Host and then upgrade from 9926 to 10041, bridge networking option disappears from guest OS settings in Vbox and 10041 host OS networking stack gets hosed.

​https://forums.virtualbox.org/viewtopic.php?f=6&t=66682

[dhrida]

I would like to update this. So far, I have found that this actually crashes Windows 10 only on wireless network adapters. I have tried this on 4 different computers, each with different network adapters... Dell Vostro 360, Sony VAIO VPCSA, Toshiba NP880z, and a Dell Precision T7600. These all have different network cards, but if I disable all wifi adapters, the problem is solved.

I think it must be something to do with the way the VirtualBox bridge recognizes adapter type because even if you install the virtualbox network bridge driver and disable it only on your wifi adapter, everything is perfectly fine. The problem doesn't occur on wired network adapters at all. I noticed this because my workstation has no wireless network card.

The only problem is I don't have enough knowledge of the virtualbox source code to be able to find out where it does this.