Win XP VM Under Win 11 Not Working

[Tax Shack]

What do you mean not working?! It's been a while since I ran this Win XP VM, but today I get two different errors and it depends on the amount of RAM set on the VM. With 750MB, I get a blue screen (same with 1024MB). With 2048 MB, no blue screen, but it took over an hour for XP to come up and once it did, clicking on stuff does nothing (or maybe it's extremely slow going). I guess something new on the host since the last time I ran this has caused problems. Attached are a blue-screen and no-blue-screen logs.

BTW, I've been running a Win 10 VM just fine under this same host environment. Any help is appreciated!

[lylejk]

Can you recover from a saved recovery point. Usually save a golden set point for my VMs. Run XP VM daily under Win11 without issue. Might be a driver issue but if nothing changed, then possibly your VM got corrupted. Over time, I had to re-install my XP VM a few times over the years (once when running Win7 and another time when in Win10). Sad when there is no solution other than to do this. Hopefully you will fine a solution without having to hose your VM.

[multiOS]

@Tax Shack

Both sets of logs show you have the same issue that you previously experienced:

00:00:05.158320 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:05.433381 NEM: info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:05.433531 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

00:00:05.444610 CPUM: No hardware-virtualization capability detected

The lack of access to VT-x means that VirtualBox is having to fall back to making use of the Microsoft hypervisor interface.

If you have 'upgraded the Host Windows 11 System to 24H2 that probably reactivated some Virtual-Based Security features.

For Microsoft's current take/advice on this issue see:

- https://learn.microsoft.com/en-gb/troub ... th-hyper-v