Virtualbox 7.0.16 crashes Windows 11 host

[Cor3]

I'm having this issue with Windows 11 Insider build 22635.3495 23H2. When tried to start Debian Virtual Machine. Having greenscreen issue with VBoxNetLwf.sys as rest of people here.

[Woody_98]

Throwing my name in the hat, Windows 10 Ent latest build, I start up a headless Fedora 39 VM and as soon as DNF check update starts my workstation blue screens. I've gone back to the previous test build I'd upgraded from and all is good.

[microapplication]

Windows 11 pro powershell, VirtualBox 7.0.16, Guest Fedora39
ssh login, excute: mkdir foonathan_memory_vendor/build
System blue screen and crashes

[Bettatek]

I have also encountered this on a Windows 10 host after upgrading to Virtualbox 7.0.16. The problem doesn't occur when starting a Linux guest O/S but does occur when starting a Windows 11 guest O/S.

[kabu]

There is a new warning on main virtualbox.org page and download page about this issue, so development is aware of problem and looking into it.

[Renansmed]

I have same issue.
I´m running Windows 11, 23h2 and VB 7.0.16
I went back to VirtualBox 7.0.14 and it worked without a problem

[Denwar]

Same BSOD crash. (Just adding my +1).

Linux Mint VM: boot and login fine, but Windows will BSOD short after runnng Firefox or trying too SSH.

VirtualBox 7.0.16
Windows 11 23H2 build 22631.3447

Code: Select all

PAGE_FAULT_IN_NONPAGED_AREA

is the only thing I'm quick enough to see before it reboots.

Will try downgrading to 7.0.14.

[NAILS]

same here. BSOD as soon as I try to do something. going back to 7.0.14.

[lIUSPCN]

host crash immediately while SSH login by PUTTY:
VirtualBox 7.0.16
host: Windows 11 23H2 build 22631.3447
guest: debian 12.5.0


VirtualBox 7.0.14 worked FINE.

[multiOS]

Has anyone adding to the 'me too' list read the heavily highlighted warning on the VirtualBox downloads page - https://www.virtualbox.org/wiki/Downloads - advising users not to upgrade to 7.0.16 yet? i.e. DO NOT INSTALL until a fix is announced for a known problem identified in the original release.

[Stickybit]

Just revert back to 7.0.14, and temporarily switch to NAT networking - then your VM's will run again. After a successful VM startup, you can switch back to the method of networking, that you want to use.

Regards, Stickybit