My experience is that Win11 will run a large number of programs that Win10 can run. Win11 for me is mostly visual changes, things moved around and needs finding and getting used to it. But that's been the case since my first computer in '92 with MS-DOS 5 and Windows 3.1 then new job in computer store ad building 2 year after that [retired]. One change with Win11 is there is no installation for a 32-bit version although 32-bit programs can be run.
It is called reverse engineering. It is one of the oldest practice, and the practice that allows ( for example ) EA "Electronic Arts" to make those "Madden" games for the SEGA Genesis/Megadrive. Why? At this point in history SEGA ( Japan ) was giving the middle-finger to many western companies. So these companies literally had to "reverse engineer" and create there own dev-kits.
reverse engineering is the reason why eastern series literally was able to go up against western machines and allowed for creation of various processors and chip-sets.
With programming you literally could "deconstruct" any program from the inside out, and if not then use the "Source code" to compile something together.
.....................
By that "programmer could do this easy", I ran into a really nice website after reading the fine-print on this DOS release of Mplayer, and Windows 98 conversion of CPU-ID ( When I was running Windows 98 ). The website was amazing. Point being is that all drivers could be downgraded/upgraded to whichever system.
Only problem with Windows 10 ( possibly 11-12 ) is that these DIY drivers will be block and you have to unblock them a script.
The same with newer GPU drivers on earlier versions of windows 10.
A huge hit was Microsoft literally attacking anybody that was uploading there software. They do not want people to edit or alter there drivers. By uploading I do not mean entire windows installation. I mean things like language pack files, or altered files so you would have next to no problem installing anything.
.............................
You might as well go ahead and try. I mean the Drivers should work no different. If it was me that is how I would roll.
1. Install Windows 10
2. Disable integrity checks and enable driver test signing
3. When installing drivers look in the Windows.old folder System32. Where all the drivers INF fZiles should be unless mistaken.
4. See if the drivers would install
5. Look up the part, model, make and go online and search for drivers and install manually.
6. If updating drivers remember that some newer drivers prevents downgrading or uninstalling through normal means.
Then of course there is alternative drivers. Like for instance Windows PE are using a set of drivers made to boot on a
specific hardware. Same with using drivers meant for previous or later Windows installments. Meaning you can use those
drivers ( official or not ) but they might not perform as they should. Your windows 10 should work flawlessly with windows 11 drivers unless we are talking about other features like A.I. ( computer learning ), or automated processes or even the problem that prevents moving a windows XP install before disabling first. If the drivers are not working ( newer ) then try to Disable integrity checks and enable driver test signing, because sometimes newer drivers will appear to be installed but will not function due to this limitation. Same with DIY drivers.
With each Windows 10 update they have removed various support. Like I am certain my 1903 could run specific programs from Vista and XP but my 2004 ( 20H1 ) seems to have lost this ability.
The solution is to use emulators.
DOSBOX = DOS
Windows 9x emulator ( Hyper-V, VMware X86 emu ) = DOS + Windows stuff.
X64 just means the OS is X64 if they were to drop support for X32 ( which they can not because X64 is built in X32 ( i386 ) )
so it makes no sense to remove support. However if it was a processor for some reason was unable to do X32 and only do X64 programs that uses X32 at some point in it's execution and or code would cease to function. Otherwise would be pure emulation and thus slower then what it seems.
OSX PPC was X64 but the operating system was X32. However with correct programming a program could access these abilities or even take advantage of multiple processors. OSX dropping support for PPC applications was the biggest downfall because many newer applications do not do the same work
Quote