virtualbox[.]org/
forums.virtualbox[.]org/viewtopic.php?t=114169
Forum posts indicate it's a problem with the Windows installer. I replaced the new Oracle folder with a copy of the previous version and it works.
WARNING - VirtualBox 7.2.4 Fails In Windows
(2 posts) (1 voice)-
mikiem2
ModeratorThe following is based Only on my own, personal experiences -- I have no clue of what's behind these problems, and while I suspect it's an incompatibility with Windows after the latest updates, that's pure speculation. I simply hope that this *might* be useful to someone. The problems do not seem to be software related, since I've experienced the same basic issues using another copy of Win11 with different software installed on this same PC. It could of course be hardware related -- I don't have VBox installed on any other PCs/laptops so I have no experience there.
1) After updating VBox 7.1.14 to 7.2.4, trying to run any vm failed with an error referencing VMMR0.r0. Leaving all the newer drivers etc. in place, I simply replaced the Program Files\ Oracle\ VirtualBox folder with a folder containing the older version 7.1.14. That worked for a couple of weeks I think.
2) VBox 7.1.14 suddenly started throwing an error, again referencing VMMR0.r0, whenever I tried to run any vm. Repairing VBox using its installer had no effect, upgrading to 7.2.4 had no effect, reinstalling 7.1.14 had no effect. Uninstalling VBox, then installing 7.2.4 worked. On the 2nd copy of Windows, while the 7.1.14 -> 7.2.4 upgrade also failed, uninstalling VBox, then installing 7.2.4 worked. Using this primary copy of Windows, VBox 7.2.4 continued to work for about a week.
3) Then one day I again got an error referencing VMMR0.r0 whenever I tried to run a vm. Shooting in the dark, some of the hits I got Googling the problem talked about problems with Windows virtual memory features &/or Hyper-V, so I tried enabling Windows Virtual Machine Platform in Control Panel -> Programs and Features. That failed, so I turned that off and tried Windows Hypervisor Platform, and that worked, although VBox performance took a noticeable hit. If turning that on was actually a cure, then turning it off should break VBox again, only that's Not what happened -- VBox has been working now for the past 1.5 weeks with Windows Hypervisor Platform turned off (?).
Posted 2 weeks ago #
Reply
You must log in to post.