Forum Discussion
Karl-WE
Sep 07, 2023MVP
B25941 - booting ISO fails with STOP UNSUPPORTED_PROCESSOR - SOLVED
Dear Windows Insider Team, I am trying a new attempt to build up a lab and testing Windows Server vNext. However booting the latest ISO fails (baremetal Installation) when loading the setup ...
- Nov 12, 2023The issue has been solved in b25987 (or earlier). This could be due to code changes. It could be also the case that now, after the official release of Intel's 14th gen CPUs, the microcode, formerly implemented by ISV as "Intel next gen" is now accepted by the kernel.
Either way, thank you very much!
Joachim_Otahal
Sep 08, 2023Iron Contributor
BIOS/UEFI update. Some MSI mainboards currently have a similar issue with Windows 11.
- Karl-WESep 08, 2023MVPIt's the latest provided by Asrock. Can you refer to the UEFI Update and MSI Boards with the same version of Windows Server vNext and 13 gen Intel?
Thanks for references.
Just to avoid misunderstandings, W11 works flawless even Insider Dev. Only Windows Server vNext is impacted.
In-place Upgrade from the fresh ws 2022 to vNext Datacenter will termimate in SafeOS Phase 2 aswell.
For unclear reasons setupdiag doesn't give any output after rollback.- Joachim_OtahalSep 09, 2023Iron ContributorWell, it was a shot in the dark. I guess you tried the "BIOS safe defaults" not "optimized defaults" and the like already.
But when you mention "upgrade": If the recovery partition is too small and there is not enough space left (i.e. 1 GB of disk space unused by any partition) upgrades fail. Had that a few times, for example when upgrading from 2012 (R2) to 2019. So three possible solutions: Use a partition manager to increase the size of that partition. Shrink the main partition by at least 1 GB and hope the upgrade will use the free space. Do a fresh install with vNext on an empty disk.- Karl-WESep 09, 2023MVP
"if the recovery partition is too small and there is not enough space left"
or too many primary partitions on this physical disk used for the installation / WinRE due Windows Multiboot), even (obviously) though using GPT on this physical disk.