The server part is because the install.wim/esd info is changed to server (by the fix you used), server doesn't have the requirement checks so this way it can install on unsupported hardware.
By not using a fix but that would not get your win 11 on unsupported hardware. Why is this a problem?
So even though I'm using 21H2 I wouldn't be able to upgrade to 22H2 using your tool to override hardware impositions? Sorry, I know it sounded dumb but I wanna understand and I know you can help me to.
When the tools are used it will show Server at upgrading and you can upgrade to 22H2. You didn't want it to show Server, that's what i replied to.
Hello, Is anyone getting error 0xc1900101 or error 0x8024a22d while trying to upgrade to this build? I've been since last night trying to update and after rebooting my PC the startup sequence gets stucked and I need to force the shutdown and restore to the previous build. Thanks
Then try to disable it by @BAU his defender toggle bat. Other reasons can be driver incompatibility or even bios needs an update.
0xc1900101 same. This error may occur same as driver_power_state_failure. File: NTOSKRNL.exe (original, not modified) -windows update
Where can I find that toggle bat? Drivers are updated always via WU so I have what Microsoft says to be "up to date" drivers.
I installed 22H2 a week or so ago using uup. Is there anything different from the official release preview that I would be missing?
No, both are still 22621.1 and when you have created the ISO from the may entry on UUP dump you probably have the NDP35-48 CU installed too.