@@MewtonBeats Both are fine. If you want to nitpick it that much, x64 should actually be x86-64, and x32/x86 should be IA-32 (in this case, as we are talking about the architectures of the processors the software is running on. There are other 32-bit processors that aren't IA-32, but they are usually obscure and rare). TL;DR: While x32 is technically inaccurate, saying x86 is also technically inaccurate. en.wikipedia.org/wiki/X86
@@ekeleze76 I remember hearing somewhere that x32 is a 64 bit mode for x86-64 that uses a 32 bit bus for memory. I'm not sure where I heard that, so take it with a pinch of salt.
i dont think this is related to the os being 32 bit but rather the old virtualbox version not emulating the proper instructions required for windows 11 or its pe environment to boot.
To my knowlage, you can't use x64 software on an x32 system.
x86*
@@MewtonBeats Both are fine. If you want to nitpick it that much, x64 should actually be x86-64, and x32/x86 should be IA-32 (in this case, as we are talking about the architectures of the processors the software is running on. There are other 32-bit processors that aren't IA-32, but they are usually obscure and rare).
TL;DR: While x32 is technically inaccurate, saying x86 is also technically inaccurate.
en.wikipedia.org/wiki/X86
@@ekeleze76 I remember hearing somewhere that x32 is a 64 bit mode for x86-64 that uses a 32 bit bus for memory. I'm not sure where I heard that, so take it with a pinch of salt.
Well i remember reading that you can EMULATE not virtualiz but emulate x64 on x32
@@uhhhh173Windows 10 x86 VM worked for me on Windows 2000.
i dont think this is related to the os being 32 bit but rather the old virtualbox version not emulating the proper instructions required for windows 11 or its pe environment to boot.
The gen alphas: Womp Womp
Hmm I Wonder Why
Must be compatibility
That's strange, try running Windows 11 on MS-DOS instead! :p
HMM idk why
from 12 minute you are sitting there and sleeping