Windows XP Installation Stops at the beginning [SOLVED PROVISIONALLY]

[laukinming]

After formatting a new guest hard drive, the Windows XP installation loads, but then it does nothing.

It just sits there at "Preparing Installation" instead of displaying a green bar.

I have attached a log file.

Games Support-2023-12-04-07-24-22.zip

(33.14 KiB) Downloaded 76 times

[laukinming]

OK, found the problem: I enabled a bunch of virtualisation features instead of enabling the BIOS settings (i.e. the BIOS has somehow reset since my last wipe) and made this mess.

Luckily, I undid it and it's back to normal.

Apologies for the bother.

[scottgus1]

No problem! Thanks for letting us know you found a solution.

[laukinming]

The problem has resurfaced.

I'm using a later version, 7.0.14.

This time, it is from a system wipe and I have not messed with any of the Windows Features, including those that have to do with virtualisation.

Another log has been attached.

[laukinming]

I've currently tried to wipe my hard drive again and putting Windows 11 Build 22631.3007 without adding the Cumulative Preview.

I still haven't added any more features other than DirectlPlay and SMB1.0/CIFS file sharing support.

I have another computer, a Linux Mint machine, and it boots the XP installer just fine. I know it's this computer's problem, but I can't pinpoint the source. Downgrading was attempted, and the problem persists.

So far, I never enabled any of the virtualisation features because I know that they're not to enable, or am I wrong.

Please help!

[laukinming]

No need.

I enabled the Virtual Machine Platform on Windows 11.

Remember to do that!

Case closed for now.

[laukinming]

OK, problem is back.

I don't know how, but the problem just came back and I didn't make changes to other settings.

This time, I tried enabling both Virtual Machine Platform and Windows Hypervisor Platform.

Now I am going to try Windows Hypervisor Platform on its own.

If you have any advice, I would welcome it.

[laukinming]

OK, enabled Virtual Machine Platform by its lonesome yet again, and works.

Sometimes I can't understand my computer.

[scottgus1]

In some fashion or other, your Windows 11 host is enabling Hyper-V, which has been known to interfere with Virtualbox. HMR3Init: Attempting fall back to NEM (Hyper-V is active) has some ways that the forum gurus have found to disable Hyper-V, at the expense of some of Windows' security features. Risk/benefit analysis is needed by you to determine if full-open Virtualbox or Hyper-V security is more important.

That your enabling some Hyper-V features gets Virtualbox going is interesting. It could be there's some combination of other Hyper-V items running, some of which are enabled in the computer's BIOS now.

FWIW Windows keeps coming up with more Hyper-V-related services that the Virtualbox devs are constantly having to work through. It is possible that the tutorial above will get out of date, until someone reports a new Hyper-V service and how to turn it off.

[laukinming]

No, I didn't enable Hyper-V, I enabled Virtual Machine Platform.

Hyper-V is off.

[scottgus1]

No, I didn't enable Hyper-V, I enabled Virtual Machine Platform.

Virtual Machine Platform uses Hyper-V. If you enabled the one, it enables the other. If the green turtle is present. Hyper-V is enabled.

Do you see the green turtle?

[laukinming]

No, I haven't the faintest idea what you're talking about.

Green turtle? I just know that when I enabled Virtual Machine Platform, the problem was solved.

Well, for better or worse, it works, until next time.

[scottgus1]

I haven't the faintest idea what you're talking about.

See the tutorial linked above, paragraph starting with "You might notice in the guest window's Status Bar"...

[laukinming]

OK, I did remember that I enabled "Memory Integrity" on Defender, which might have caused all this, so I turned it off.

I also turned off "Virtual Machine Platform," "Hyper-V," and "Hypervisor Platform," and the system still runs, and this time, without the turtle icon.

Thank you.

But I will leave this to be ongoing and shall still put it on "Solved Provisionally," but at least it's fine.