Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
See the following for disabling Hyper-V properly on Windows:
viewtopic.php?f=25&t=99390
If you need Hyper-V enabled so you can use Docker and/or WSL then grab the VirtualBox-6.1.35-150972-Win (later version may or may not work) on the following page:
https://www.virtualbox.org/wiki/Testbuilds
NOTE: Make sure you keep a copy of any test versions you download as only the latest is available for download.
viewtopic.php?f=25&t=99390
If you need Hyper-V enabled so you can use Docker and/or WSL then grab the VirtualBox-6.1.35-150972-Win (later version may or may not work) on the following page:
https://www.virtualbox.org/wiki/Testbuilds
NOTE: Make sure you keep a copy of any test versions you download as only the latest is available for download.
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
It dosen't helpAndyCot wrote:See the following for disabling Hyper-V properly on Windows:
viewtopic.php?f=25&t=99390
If you need Hyper-V enabled so you can use Docker and/or WSL then grab the VirtualBox-6.1.35-150972-Win (later version may or may not work) on the following page:
https://www.virtualbox.org/wiki/Testbuilds
NOTE: Make sure you keep a copy of any test versions you download as only the latest is available for download.
Only some systemsettings seam to lose
See Picture from Error in Virtualbox und my setting in DOS WIndow als Administrator
- Attachments
-
- Linux_Error_klein.jpg (72.6 KiB) Viewed 2030 times
-
- DOS_Disable_hyperV_klein.jpg (65.65 KiB) Viewed 2030 times
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
The new Windowsupdate from today dosen't help
2022-05 Kumulatives Update für Windows 11 für x64-basierte Systeme (KB5014019)
Please solve the Problem .......
2022-05 Kumulatives Update für Windows 11 für x64-basierte Systeme (KB5014019)
Please solve the Problem .......
-
- Volunteer
- Posts: 5102
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
I doubt that the Windows updates have much to do with your problem. I have been running the KB5013943 update for two weeks and installed KB5014019 today. Neither had any effect on my VirtualBox vms.
I would be more impressed if you posted a log showing that the Windows hypervisor is not loaded.
I would be more impressed if you posted a log showing that the Windows hypervisor is not loaded.
Bill
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
Hello BillG,
thanks for your replay. In the Appendix my logfile
thanks for your replay. In the Appendix my logfile
- Attachments
-
- VM_LOG.zip
- (29.5 KiB) Downloaded 10 times
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
Here my Updatehistory. I have uninstalled and installed 1 or 2 patches to see if the problem can be solved.
i use a surface pro 8, can it be related to that. I think that it is related to the Windows update, because 5 minutes before the Update everything ran without problems and directly after the patch i got the errors. Between these steps is nothing happened
i use a surface pro 8, can it be related to that. I think that it is related to the Windows update, because 5 minutes before the Update everything ran without problems and directly after the patch i got the errors. Between these steps is nothing happened
- Attachments
-
- Updateverlauf.png (99.2 KiB) Viewed 1909 times
Last edited by Thyfos on 27. May 2022, 18:33, edited 1 time in total.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
If Bill can run with the updates installed, then it's probably not the updates.
Hyper-V is on, and you're running 6.1.34:
Alternatively, turn off Hyper-V, see See HMR3Init: Attempting fall back to NEM (Hyper-V is active).
One other alternative, you VM has only one processor. Try two.
Hyper-V is on, and you're running 6.1.34:
Test builds 6.1.35 are reported to have some fixes for the recent Hyper-V mess. See Andy's link above. If you use a Test build, save the installer until you change versions in the future.00:00:03.043116 VirtualBox VM 6.1.34 r150636 win.amd64 (Mar 23 2022 00:36:21) release log
00:00:03.596752 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
Alternatively, turn off Hyper-V, see See HMR3Init: Attempting fall back to NEM (Hyper-V is active).
One other alternative, you VM has only one processor. Try two.
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
Thank you Guys, you are the best! With 2 cpu the Problem seems to be solved!!!!!! Thank you!
the steps to turn off hyper-v i had done, see screenshots above . It doesn't matter now, it works and I am very happy.
the steps to turn off hyper-v i had done, see screenshots above . It doesn't matter now, it works and I am very happy.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
Verra interestin'! Thanks for the feedback. Could you please post another log of the VM, just for comparison?Thyfos wrote:With 2 cpu the Problem seems to be solved
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
I attached the log after stop a good runinng VM.
- Attachments
-
- SF_Oracle19-2022-05-27-18-45-52.zip
- (32.71 KiB) Downloaded 15 times
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
I tested a second VM wiht 2 CPU's. Also no problems here
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Reporting that KB5013943 Update for Windows 11 broke my VirtualBox
Thanks for the log!
Glad the two processors worked!
Hyper-V is still enabled, (it can be tricky to get rid of if other thigs like the Windows *Guards are enabled).00:00:03.750645 VirtualBox VM 6.1.34 r150636 win.amd64 (Mar 23 2022 00:36:21) release log
00:00:04.210660 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
Glad the two processors worked!