Page 1 of 1

win 7-64 is not installed

Posted: 11. Feb 2021, 09:12
by tmpnikl
host win 10, iso x 86 in VB installs fine, but install iso x 64 does not reach the prompt window, although there is no such freeze on another computer. In safe mode, it reaches drive.sys and stops. What could be the problem?

Re: win 7-64 is not installed

Posted: 11. Feb 2021, 10:52
by mpack
Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

Re: win 7-64 is not installed

Posted: 11. Feb 2021, 11:22
by tmpnikl
Thanks for the answer, the log is in the attached file.

Re: win 7-64 is not installed

Posted: 11. Feb 2021, 12:54
by mpack
00:00:12.267465 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:12.328690 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
You have Hyper-v enabled. Please read the last post of FAQ: I have a 64bit host, but can't install 64bit guests. I suggest that you go directly to the "bcdedit" instruction.

I suggest that you also give 2 cores to the VM, set graphics RAM to 128MB, and install the host Extension Pack.

Re: win 7-64 is not installed

Posted: 12. Feb 2021, 07:01
by tmpnikl
Thanks for the answer, thanks for the link, but Hyper-v has been disabled. But I realized that I need to check all the windows 10 components again. After turning off the Windows Sandbox, the installation was successful.

PS: sorry for the english spelling.

Re: win 7-64 is not installed

Posted: 12. Feb 2021, 07:44
by BillG
Yes, sandbox is another one which causes trouble - it runs in a virtual environment, like WSL2 etc etc.

Re: win 7-64 is not installed

Posted: 12. Feb 2021, 10:57
by mpack
tmpnikl wrote:Thanks for the answer, thanks for the link, but Hyper-v has been disabled.
If that was true then the quoted line from the log would not have been present.

You need to understand the difference between the Hyper-v "manager" which creates VMs and the underlying Hyper-v "engine", which the log refers to as NEM. Originally the two things were one (more or less), but these days a lot of Windows 10 security features implicitly enable the underlying engine. This is also what the FAQ told you.