[Solved] Failed installation Windows 10 64 on Host Windows 10 64

[DomTom91]

Hi,

Sorry for my poor english

I want install an VM Windows10 64 bits on a guest Host Windows10 64 (20H2 v19042.868).
I use VirtualBox v6.1.18 r 142142 (Qt5.6.2).
I've differntes VMs who work correctly : Debian64 (graphical interface), Jeedom (Debian64 less garphical interface), Xubuntu64, Windows7 64.

My hyper-V and others optionnals fonctions who can create problems seems to be disable on my Win10 64 host.

The problem for my new VM is that I can't boot.
If I want do an upgrade on my VM Win7 64, I've 30% who do under Win7 with a graphical windows, and at the first reboot, I've a Guru mediation critical error.
If I want install on a new VM Win10 64, I've a Guru mediation critical error and I can't run installation.

My ISO disc is download from Microsoft's website and I use it for install my "Hard" machine.

I don't found solution with my friends Google, SearX.bar, or on this forum.

Does it possible to have help please ?

I joint my logs and picture.

Notes : I've test with templates Win10 64, Win2019 64, Win2016 64, Win8.1 64 ans with check or uncheck , in french, "Activer EFI" (run EFI in english ?)
When I check the box, I can look the sentence "press a key for boot from CD or DVD" and I've the crash after that I press a key. If it's uncheck, I don't see the sentence.

Best regards.
Thomas

[mpack]

Windows 10-64bit?

You have selected "Windows Server 2019" as the template, which is not correct.

If the guest is actually Windows 10 then choose the Windows 10 (64bit) template.

If the guest is Windows Server 2019 then choose the Windows Server 2016 template (a potential problem has been reported with the 2019 template).

In other news, 32MB is not enough graphics RAM. Please increase to 128MB. Disable transparency effects (in the Windows guest OS) and then enable 3D acceleration.

Also, I notice that you located the VM on host drive E:. I hope that this drive is suitable for running Windows - e.g. a removeable drive can be a bad idea, a USB removeable drive would be worse!

[DomTom91]

Thx for your answer.

Yes I run on hard machine Windows 10 64 bits and I want install the same on the VM.
Yes I've done a test with the template Windows 2019 64bits.
The hard machine is my personnal filses server , softwares server, print server.
I've a 6To RAID5.
It is backup on a second Win10 64bits server with 6To RAID 5 to.
the E partiton is one of my differents partion on the RAID.
My others VMs are on E drive to. I've not problems with the others.

I've do a new test with the template Windows 10 64 bits and up the VRAM to 128 Mo same you tell me.
Same error.
I send the new log file.

[fth0]

Why did you enable System > Processor > Nested VT-X/AMD-V? Does your problem persist if you disable it?

[DomTom91]

Yes always the same problem when I disable it.

In the absolute, one time that I will my VM guest Win10, I want test to installl inside other VMs.

[fth0]

Please provide another VBox.log file, from a VM run with System > Processor > Nested VT-X/AMD-V disabled.

PS: You can write your posts in your own language, and we will try and use Google Translate (or similar) to translate it.

[DomTom91]

Thx for your help.

Ci-joint un nouveau fichier log avec processeur, fonction avancées VT-x/AMD-V imbriqué désactivé

[mpack]

Triple fault guru again. This could simply mean that the "F:\Windows.iso" file is corrupted. An MD5 or SHA checksum comparison on that exact file would be useful.

[fth0]

00:00:08.080951 CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it!

00:00:08.081274 Ext Features
00:00:08.081274   Mnemonic - Description                                  = guest (host)
00:00:08.081285   NX - No-Execute/Execute-Disable                         = 0 (0)

00:00:20.386356 IEM: wrmsr(0xc0000080,0x0`00000d00) -> #GP(0)
00:00:20.386353 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'

I can try and explain the Guru Meditation:

According to the CPUID of the host CPU, as seen by VirtualBox, the Data Execution Prevention (DEP/NX/XD) CPU feature is not available. This is usually the consequence of DEP/NX/XD being disabled in the BIOS. Windows 10 usually requires it and tries to turn it on (bit 11 of the IA32_EFER MSR), thereby triggering the Guru Meditation. Please search for the BIOS setting and turn it on.

What I cannot explain is the security state of the host OS, which is also Windows 10 ...

[DomTom91]

hi @fth0,

Very big thanks.
You're right.
Nx was not check in the BIOS of my motherboard, I enable it and Now I'm installing my VM Windows 10.

I'm not sure that I've understant all that you tell me.
That I don't understant it's if Windows 10 need that this fonction is enable for run, why I can install it on my "hard" pc with this fonction disable. May be the Microsoft's magic...

Bests regards.

Thomas