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

[notmoti]

Anybody try 99222?

[Jacob Klein]

I believe that I've confirmed that Windows 10 Build 10041 has networking issues, even if VirtualBox was never installed onto a clean installation of it.
For me, the network just stops working altogether sometimes.
Good thing I was dual-booting. Looks like I'll have to "sit this round out", and use my Windows 8.1 partition for a few weeks until I can try a new build :/

[cybershawngates]

On Windows 10 Build 10041, any install or upgrade of any version of VirtualBox hoses my network stack. I had to use System Restore, to restore to the restore point that was automatically created when I attempted the upgrade/install, and now my network works again.

It looks like installing/upgrading will not be possible within 10041. If you need to install/upgrade, one option might be to go back to 9926, do the install/upgrade, then go to 10041.

Edit: I'm not out of the woods yet. After the System Restore, now none of my "Windows apps" start, and "sfc /scannow" can't even run. Grrrr. I knew going in that selecting "Fast ring" would be buggy, but I was prepared for it, and I accept the consequences. However, it's quite sad that this build was released to the poor "Slow ring" folks.

Edit 2: Confirmed the 2 problems (network stack gets broken on a VirtualBox install, and System Restore destroys authorization for modern Windows apps), on a brand new fresh install of 10041. So now I'm going to try to install 9926, then VirtualBox, then upgrade to 10041 via Windows Update. Will report back my results shortly.

Regards,
Jacob

i did the same - system restore to 9926 install point. Then I had to search a powershell command that fixes metro apps not opening and start menu not popping up. Finally I had to delete my main user account and create a new user account (copied stuff from old account prior to delete) and then it's working. I believe it was this

https://www.techmesto.com/fix-start-men ... l-preview/

It still required deletion of primary user account to get things working and a couple reboots and log in to admin account to first get things working prior to creation new account. I have a lot of windows apps installed and did not want to reinstall of them (as to why I didn't just clean install 9926 again).

[cybershawngates]

All USB support was gone upon the system trying to load VirtualBox Miniport.

Haha yeah this happened to me yesterday. All my USB devices went down when installing the latest 4.3.27. You have more patience than I do. I just re-installed the whole OS.

I'm afraid to test other builds now and without VirtualBox I won't be using the new Windows 10 build.

exactly - I will be staying on 9926 for a while till someone figures this out.

reporting - where do we report this bug? EDIT: I posted on this one:

https://www.virtualbox.org/ticket/13937#comment:3

[Jacob Klein]

Again, I will mention, that I'm betting this is a Windows 10 bug, instead of a VirtualBox bug. The network stack in Build 10041 is prone to failure, and others are reporting USB stack failures too. What really sucks is that I can't just go to 9926, since 10041 has been released to the Slow Ring, and Windows Update will download it. So.... as I said, I'm going to use Windows 8.1 until the next Windows 10 build comes out for me to try.

[Jacob Klein]

Windows 10 Build 10049 was released today to the Fast ring users. I briefly tried to install Oracle VirtualBox v4.3.27 Test Build 99222.

On Windows 10 Build 10041, the installation appeared successful but the network was destroyed.
On Windows 10 Build 10049, the installation rolls back at the end and says it had a fatal error, and the network remains in-tact.
I guess I consider this an improvement?

I'd be curious what others are experiencing with 10049, and what they think.
Again, I want to stress that it's very likely we are seeing Windows bugs here, and not Oracle bugs, I think.

[cybershawngates]

Theres a new windows host build 10049 - anyone try virtualbox on it?

On Win10-9926 I'm getting a intermittent BSOD using Virtualbox 4.3.27
Crash analysis says : Probably caused by : VBoxNetFlt.sys ( VBoxNetFlt+46bd )

EDIT: @Jacob - I See ur post above me feedback from 10049 - Best I stay away from it now!

[Jacob Klein]

I explained my 10049 experience, in the post before yours.

[cybershawngates]

I explained my 10049 experience, in the post before yours.

I see it now - this just keeps getting worse and worse lol. And it's got a Summertime release date win10?

[Sireone]

I'd be curious what others are experiencing with 10049, and what they think.
Again, I want to stress that it's very likely we are seeing Windows bugs here, and not Oracle bugs, I think.

Seeing the same rollback error on 10049. What sux for me, is that I was trying to use Hyper-V in the interim, but that seems to be broken in 10049.

[Jacob Klein]

Thanks for confirmation, Sireone.

I think we're in the middle of a "rough patch of Windows 10 builds", where network/usb stacks are quite broken. I've started using Windows 8.1 again (which I had set up a long time ago, since I was dual-booting into Windows 10).

[sese]

I installed the Windows 10 Build 10049, until now I didn't find any way to run virtual box on my computer. I tried even 5.0 beta, none was working.
I'd like to know if someone find a way to run virtuabox on this windows build.

[Martin]

Wait till Microsoft fixes the bugs in Windows 10.

[cybershawngates]

so 9926 is the last known working build of windows 10 as host? I changed myself to the slow channel for updates.

[Jacob Klein]

Hate to tell you, but 10041 has been offered even to the Slow Ring, as of several days ago. That is why I started using my Windows 8.1 partition again.