it let me open gateway once but still i launched it with 3rd try. and all i see is this text (Loading linux 6.1.0-37-amd64… Loading initial ramdisk …) and black screen after. sometime its “-” symbol pinging few times. how to fix it? is there a disc problem? i had this type of stuff previously on older versions but now i got completely new windows and hardware as well. no matter which boot mode im choosing result is the same.
how to fix this? maybe i should upload logs?
i got 9800x3d if its matter idk
host is windows or gnu/linux? vbox version? if its gnu/linux, which distro? have your tried the kvm version if you are on gnu/linux?
Good day kind sir. im on win11, vbox 7.2.4 r170995 qt 6.8.0 on windows
go to sysmaint/persistent boot, then upgrade the system, i have linux version 6.1.41.
Report back if the issue persisted.
1 Like
Might be the result of Hyper-V slowing VirtualBox down. You might want to try leaving the VM booting for a very long time (maybe as long as 15 minutes) to see if it does eventually boot.
There is an (experimental) script developed by the Whonix project that you can use to try to disable Hyper-V on Windows 11; this will speed up Whonix execution in VirtualBox. It does come with some risks, especially if you’re using Windows Hello, Device Encryption, or BitLocker, so if you want to try it, proceed with caution and carefully read the built-in documentation it displays when initially run. The script is at Whonix-Installer/DisableHyperV.bat at master · Whonix/Whonix-Installer · GitHub.
2 Likes
after the instructions gaven my clever man nurmagoz everything is working fine.
1 Like
yea first thing i checked is Hyper-V and it was turned off. thanks for reply btw
1 Like
how does bitlocker conflicts with Whonix? im usually using it and gonna turn it on
also what is your opinion on Vbox encryption? is it enough and safe to protect if my hardware will be taken by someone to break through?
Check this:
Note: Whonix is based on Kicksecure
Can you confirm green turtle issue has been resolved?
Does it?
Off-topic. 1 issue = 1 forum topic please.
1 Like
It doesn’t conflict, but disabling Hyper-V may cause Windows automatic BitLocker decryption to break. If that happens, you’d need to provide a recovery key at least once to get the system to boot, so it’s very important that you have access to that key before trying to disable Hyper-V. (The scripts are designed to prevent Windows from misbehaving in this way, but better safe than sorry.)
2 Likes