Windows 10 Build 10041 - Bridged Network Can't See Ethernet

[Flook]

I just verified that by following exactly same "disable driver signature enforcement" procedure, the RC2 install works without a hitch.

p.s. "disable driver signature enforcement" procedure:

1. Settings/Update & Security/Recovery/Advanced Startup/Restart now/
2. Troubleshoot/Advanced options/Startup Settings/7/
3. Windows 8 compatibility install
4. Reboot using "disable driver signature enforcement" procedure

My version of Windows 10 build 10130 does not have the advanced startup section. I was able to get things working again by:
1. Uninstall VB
2. Uninstall hidden VB Network adapter
3. Reinstall VB with windows 8 compatibility and run as administrator checked
4. Good to go for me

[admars]

on 10162 build now, 3rd July VirtualBox-5.0.0_RC3-101436-Win.exe, it's installed ok, I can add a bridged network adapter at last, but the virtual machine won't start


Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {703510de-8d5e-411b-a25b-378b03382bac}

seems liek some kind of progress

[admars]

used vboxmanage to convert the virtualbox vdi to a vmware vdk

vmware player 6.0.7 (free version) then asked if I wanted to convert that to newer format, warned me it's not backwards compatable, started it up in vmware, and all seems to be working ok, for the time being, until there's another win10 update (10166 currently)

[Peter Koanda]

i have the solution but this forum doesn't allow me to post u r l

[Peter Koanda]

Use this VirtualBox latest preview build www~virtualbox~org~download~testcase~VirtualBox-5.0.1-101902-Win.exe bridged network should work 100%
<please replace ~ with the correct symbol cause this forum doesn't allow me to post u r l>

[christ2]

Use this VirtualBox latest preview build www~virtualbox~org~download~testcase~VirtualBox-5.0.1-101902-Win.exe bridged network should work 100%
<please replace ~ with the correct symbol cause this forum doesn't allow me to post u r l>

Thanks Peter your solution worked for me...

[datadesigner]

I know a lot of you had install issues...my problem was after an upgrade. I had this problem after upgrading to Windows 10 GA from Windows 7. Its working great now...I think my solution was more simple than a lot of other ways around this problem. This doesn't really FIX the problem, but it got everything working for me and it performs well so I thought I'd share it with you guys in return for all the help I've recv'd from this forum over the years. Instead of using VB's bridged network, I assigned my VM's nic to a "host-only" network in VB, then I bridged the "host-only" network in Windows with the physical adapter. The VB side of doing this is pretty straight forward (its a drop down on the network settings of the VM.) Win10 is less intuitive to me...here are the steps for that:

1. Open Network Connections (search for adapter in search box), then under "Network and Sharing Center" click "View network Connections."
2. Hold down the CTRL key and select the VB adapter and the host adapter.
3. Right click on one of the selected adapters and click "Bridge Connections" (you might need to give it an admin pw)

Step 3 might take up to 2 minutes to complete depending on your PC's hardware. It looks like its done immediately but its not...so don't give up after a few seconds. Eventually a new Win 10 "bridge adapter" will appear. Give it a little time after that and see if it works.

On my setup my home network was 192.168.5.X/255.255.255.0 and my private adapter's IP is 192.168.54.2. My VM's IP is 192.168.5.205 and my Win 10 host is 192.168.5.204. Soo...I'm surprised this works, but it did. I can connect from other machines to 192.168.5.205 just as if it was bridged in VB, and I can connect out from my VM to everything else.

I hope this helps other upgraders as Win 10 rolls out. With 128GB of supported RAM in Win10, it can be a great host OS, once it works.

[renato.pierri]

May be someone stills suffering with this issue.

I've solved that issue upgrading my VirtualBox to the latest version: 5.0.0 r 101573.

Hope it helps.

[Giusi]

yr very lucky indeed!

in my case, win 10 host, nor the 5.00 up to the latest test build issued works..

[BillB]

So I had to roll back to 9926 - that got the network adapter working again. That was a real mess. Even reinstalling the network adapter wasn't working.

....

I had no luck with this.
1. Upgraded to Windows 10 (production) this month, from Win 8.1 Pro with Vbox 4.23.xxx working fine
2. Tried to run Vbox in Win10 - would not run. (did not check forum)
3. Installed 4.30 - knocked out networking.
4. Then checked this forum to see al this drama.
5. Nothing anyone suggested would work.
6. Rolled back to previous win 8.1 - all was well
7. Ran vbox again - again knocked out networking.
9. Fumbled my way through getting rid of vbox and its bridged adaptors (by guides here)
10. Now have no Vbox version that i can use.
11. And also, now MS does not accept my previous 8.1 product key - so windows 8.1 running in 60 day trial mode
12. long talks to Microsoft support and they cannot simply revalidate my product key - Tech support says only way is to purchase ($250!) new 8.1 product key or clean install to Win 8 and upgrade again (simply not acceptable)
13. Many calls an hours with MS, now I am waiting on a call back from them next week (may never come?) where they will hopefully rectify the activation issue.
14 Still have no Vbox, so my RAC cluster lab is dead

Sigh - why did I upgrade?

PS: Now if I try to install any Vbox on 8.1, I get a pop up saying: The feature you are trying to use is on a network resource that is unavailable. It seems to be looking for VirtualBox-4.3.20-r96997-MuliArch_amd64.msi and can't find it (looking in c:\temp\VirtualBox)

Oh waht fun..

PS:
1. Using advice on this thread, I used revo uninstall to get rid of all registry traces of old VBOX installs.
2. Was able to install vb 4.3.30 with host only adaptors - works
3. Finetuned by VMs a bit and they are mostly working like before now - RAC clusters up and running on all interfaces.
4. So just to clear up that pesky windows activation issue now....

Thanks all for the many posts here that have helped!

[Giusi]

at this moment vb, in any of its vers. oldest or latest,
isn't able to be launched in network bridge for all the win 10 versions as host

[Giusi]

just for let you know that
latest 5.0.3.102290 did not solve the issue

[cdg]

The problem (of Vbox installation on Windows 10 crashing the system unless bridged networking is NOT selected) has apparently been solved in version 5.0.2. However, a new anomaly has arisen:

With bridged networking enabled, the following command works on the (Windows) guest machine, and the device is accessible whether it is a disk, folder or printer:

NET USE devicename \\computername\sharename

With NAT enabled, it results in ERROR 66!

Alternately, specifying

NET USE devicename \\ipaddress\sharename

does NOT result in error 66, but if the shared device is a printer, the guest can't access it even though it shows up in the net use list!

[Giusi]

the problem for many users has not really solved with 5.0.2..
and not with the very latest tests as 5.0.3.122290 too..

[Vissie2]

I have just Upgrade my Windows 7 to Windows 10.
Encountered same problem as describe above "Bridge network can't see Ethernet"
Then I downloaded latest VB 5.0.3 Build R102290.
Including extention pack for this version.

And now I can work with bridge.
So my Host is Windows 10 Home edition.
and my Guest is OSX 10.11 El Capitain.