Page 1 of 1
Used to work, but new windows .... oups !
Posted: 29. Mar 2021, 10:47
by pierre73
Hi all,
I have a Clevo computer.
I used to run win 7 and Vbox was working fine.
I installed win 10 and Vbox won't work anymore.
I didn't change anything in the bios hence i guess windows must have a deadly setting somewhere.
I'd been looking on many discussions and tried many parameters but none would change anything.
So I come here and hope some good souls will help me with a step by step check of my problem.
Many thanks in advance.
Pierre
Re: Used to work, but new windows .... oups !
Posted: 29. Mar 2021, 13:08
by mpack
"Vbox won't work" is hard to diagnose. What exactly does not work? The UI? Particular VMs? What is the symptom of failure?
A common cause of failure with Win10 hosts is that Hyper-v is sometimes enabled. Read:
HMR3Init: Attempting fall back to NEM (Hyper-V is active).
Re: Used to work, but new windows .... oups !
Posted: 29. Mar 2021, 17:30
by pierre73
Hello,
Yes I know it wouldn't be clear, but as I don't know which way to start...
Though it appears clear that I forgot the promp error message...
Attached is the set up page, I can't validate the page and can't find the issue...
Re: Used to work, but new windows .... oups !
Posted: 29. Mar 2021, 17:34
by scottgus1
OK, that message is for an older setup (and I think it needs to be re-worded).
Either your host PC's 'Virtualization Technology' (VT-X/AMD-V/SVM) is off in the physical BIOS, or Hyper-V is enabled and taking the VT. The above link covers Hyper-V issues, and
I have a 64bit host, but can't install 64bit guests covers turning on VT and Hyper-V issues.
Re: Used to work, but new windows .... oups !
Posted: 29. Mar 2021, 17:39
by mpack
VirtualBox 6.1.x now requires VT-x or AMD-v to run all VMs. In the past it was possible to run XP without VT-x/AMD-v but that possibility is obsolete (there are no PCs left that truly need it) and has been deleted.
Scott has directed you to the correct FAQ.