32-bit/x86 Windows 10 install possible?

[zhudnall]

I have tried to install every Windows 10 32-bit/x86 version I could find, and with UTM at the most I get is either freeze on disc boot or the initial "waiting" circle of death hang, never gets to install screen.

I've tried multiple configurations, x86_64, x86, amd64... I've tried Intel emulation, qemu64 and qemu32, default. I've tried 2009 and 1996 machines.

I have done UEFI/EFI and non-UEFI boot options.

I'm running out of options and I was wondering if anyone has had any success with this, because I'm not seeing much in the Issues log.

UTM Version: 4.4.5
macOS Version: 14.4.1 (23E224)
Mac Chip (Intel, M1, ...): M3 Pro

**If you have that persistent question of "bUT wHy?!"... its 32-bit legacy software / drivers, because why the hell else would I need to subject myself to this torture.

[osy]

Please provide your config.plist

[osy]

Try changing the CPU to Broadwell-v4 or SandyBridge-v2 or something not too old but not too new

[zhudnall]

I had the same thought process for the emulation layer. I already attempted Broadwell because it was in fact the last Intel chip I've personally purchased. I also had no luck with the SandyBridge, Haswell, or IvyBridge. Neither with Default or Qemu Athlon/32/64.

I always get stuck in the same spot after boot

[osy]

Maybe turn off force multicore?

[zhudnall]

I tried removing force multicore, and also tried setting number of cores to default. I also tested across all the previous stated processors with no avail.

[zhudnall]

Also for the sake of completeness, I am attempting to emulate the Windows 10 x32 22h2 version from Microsoft.

[C4J]

I also have this problem. I am running on a MacBook Apple Silicon M3.

I have got Windows 11 and Windows XP working with UTM emulation - but Windows 10 (32bit) just won't install. I have download the media via CrystalFetch and from Microsoft direct but when I boot the new VM is just goes into the EFI boot shell and does not even try to boot from the DVD. I have tried the above suggestions without success. I did not have any issues with Win 11 and Windows XP. Very odd.

[zhudnall]

I noticed that this was moved from Issues to Discussions... I'm not sure that was the correct move.