-
-
Notifications
You must be signed in to change notification settings - Fork 555
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - virtuablox cannot make vms and booting ant non-windows vm that was created as windows causes an error #1327
Comments
|
hyper-V works but since i plan to run multiple oses, and hyper-V cannor run that, i cannot do a retroFW+debian+windows setup, this is an inconvenient for me, and a con of hyper-V and VMware might not be the software i'm most used to |
If you've enabled Hyper-V you need to enable the Virtual Machine Platform for other hypervisors to work. |
it is on and VMware works fine |
Have you tried googling your issue or looking for support from the Virtualbox community? |
googling found nothing and this seems to not have been encountered a lot, since else it would find a revalent thing |
So you didn't ask on the virtualbox forum (or whatever oracle has now). Do that and see if they can fix it. |
Before continuing...
Description
no vm's created for running Windows11(never booted os install) can go to be running Debian, this seems to happen since i have AtlasOS
Steps to reproduce
Expected behavior
i expected it to not cause an error and transition the never-installed windows to a full wipe
Actual behavior
it errors out on "supR3HardNtChildPurify", error code is "VERR_SUP_VP_NT_QI_VIRTUAL_MEMORY_ERROR (-5637)"
Atlas Version
Atlas v0.4.1 for Windows 11 24H2
Desktop information
Additional content
virtuablox reinstalling didn't work
The text was updated successfully, but these errors were encountered: