Something went wrong while installing Win 10 on VirtualBox version 6.1

[Davenonwork]

I tried installing Win10Prox641809 and Win10Prox642004 got below error:
I am installing from ISO file. Skip did not work. Retry did not work. Any help please!

VMB error 1

VMB error 1.jpg (96.43 KiB) Viewed 4288 times

Virtual Box version is latest one I am using:

VMB version.jpg (81.52 KiB) Viewed 4288 times

[scottgus1]

It is possible Hyper-V is enabled.

Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log. Search the log for these words:

Attempting fall back to NEM

If these words are in your guest's vbox.log, Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)

If these words are not present, zip the vbox.log, and post the zip file, using the forum's Upload Attachment tab.

[Davenonwork]

I will try fix advised and provide feedback. Thanks!

[Davenonwork]

I could not find "Attempting fall back to NEM" in VBox.log
I zipped VBox.zip and attached as you asked.
Thanks!

[mpack]

Where did this Windows 10 ISO come from? It doesn't seem to have a typical name.

Back in the day users with Dell hosts would sometimes make ISO images of their Dell setup DVDs and try to install them in a VM. This would fail because the image won't activate on anything but Dell, and the VM is not a Dell. I honestly don't know if this is still a thing in Win10. I'm sure Dell still gets Windows at a discount, so the underlying cause still exists - but modern Win10 style is to let you install, tell you it isn't licensed, and offer you an online upgrade.

[Davenonwork]

Where did this Windows 10 ISO come from? It doesn't seem to have a typical name.

Back in the day users with Dell hosts would sometimes make ISO images of their Dell setup DVDs and try to install them in a VM. This would fail because the image won't activate on anything but Dell, and the VM is not a Dell. I honestly don't know if this is still a thing in Win10. I'm sure Dell still gets Windows at a discount, so the underlying cause still exists - but modern Win10 style is to let you install, tell you it isn't licensed, and offer you an online upgrade.

ISO file is not shown in any screenshot I posted.
If you are confusing it with VM name. You can name it whatever you want as per your environment.
I downloaded the Windows 10 2004 ISO file from [url deleted] student portal.

[mpack]

The ISO file is referenced in the log, which I know how to read, nor am I confused.

00:00:06.803644 File system of 'D:\SETUPS-Take backup and remove\WilmU\Windows 10 Prov2004 - DVD\en_windows_10_consumer_editions_version_2004_x64_dvd_36d61c40.iso' (DVD) is ntfs

I removed the download link from your previous post: it referenced an Azure (cloud) storage location, which is not a standard distribution source for Windows ISOs. The fact that Microsoft owns Azure doesn't change that. Please make sure that don't post questionable download links on this site. In this case I'm not too unhappy because proper downloads are easily available from Microsoft (and I wonder why you didn't simply use them). Win10 won't activate without a license, and I have no reason to believe that the version you indicated had been cracked.

[scottgus1]

No Hyper-V, which is good:

00:00:06.900195 HM: HMR3Init: VT-x

Your CPU is really tiny:

00:00:08.623318 Full Name: "Pentium(R) Dual-Core CPU E5700 @ 3.00GHz"
00:00:08.623002 CPUM: Logical host processors: 2 present, 2 max, 2 online, online mask: 0000000000000003
00:00:08.623004 CPUM: Physical host cores: 2

Intel agrees that you have two non-hyperthreaded cores. Windows 10 itself likes two cores. You have only one in the guest:

00:00:06.899619 NumCPUs <integer> = 0x0000000000000001 (1)

I think I remmeber a post or two where giving two cores to the guest fixed OOBE errors like you're getting.

However your PC is really low-capability for giving a high-strength guest like Windows 10 both cores while you're running Windows 10 on the host too. Give the guest 2 cores and try again. But be prepared for the PC to struggle.