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 - after WIM file loading progress with BSOD STOP UNSUPPORTED_PROCESSOR
Repeating the same with the latest Windows Server 2022 ISO throws no errors.
The computer is not a server hardware however, yet never seen such an issue before, being part of the vNext Insider for quite some years.
HW is certainly compliant with Windows 11 and its security requirements, which I hope you will also embrace for Windows Server vNext, besides advancing to W11 UI in this release.
CPU Information
13th gen i7-13700k
Processor ID: B0671
Microcode Revision: 119
fTPM INTC firmware 600.18
SHA256, SHA384, SHA SM3_256
Phyical presence spec Version: 1.3
TPM Version: 2.0
Anything I could do on my end?
- The 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!
- The 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! - Unfortunately Asrock Support doesn't react to the issue even when I managed to proove the root cause on two Asrock Mainboards and MSI as a reference. Anything that could be done from the Microsoft's end about the Intel 14th gen Microcode in UEFI? Since they are released now, will the lastest Windows Server vNext build support the UEFI versions? Thank you very much for your feedback!
So it is clear now about the cause.
The IPU from WS 2022 to vNext fails with the same error as baremetal installation, initially reported.
BSOD UNSUPPORTED_PROCESSORReading the article from Günter (ex MVP) and xeno I believe MSFT should dig into this instead of tinkering from Insiders.
SetupDiag: processing rule: FindRollbackFailure.
.....
Error: SetupDiag reports rollback failure found.
Last Phase = Finalize
Last Operation = Remove System Restore checkpoints
Error = 0xC1900101-0x20017
LogEntry:Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.
SetupDiag found 1 matching issue.
SetupDiag results were logged to: C:\Windows\system32\SetupDiagResults.xml
Logs ZipFile created at: C:\Windows\system32\Logs.zipSetup error: 0xC1900101 - 0x20017
Installation failed inthe SAFE_OS phase with an error during BOOT operation
The error in setupdiag is misleading. The BSOD occours right after the first reboot attempt of the IPU sequence, so when loading the kernel
Wished we would have feedback hub app in Windows Server, that would make all our lives easier for sake of logging. There are no dmp files available.
Logs: Server vNextDear Server Insider Team,
It's a bit disappointing there has been no feedback on this matter.
I believe to have found the root cause for this issue.
The issue has been confirmed by Microsoft, according to several blogposts, but only for Windows 11 Insider Client OS.
The underlying issue seems to emerge on Intel 600 and 700 series chipsets, which lately received (or made available) a new UEFI update to support unreleased Intel 14th gen CPUs (named next gen CPUs, in release notes) on these platforms.
Installed the latest UEFI not looking for this support, rather as best practice.
MSI has worked on a fix with Microsoft and re-released their next gen CPU update support. Other vendors seem pending here.
I strongly believe this is the cause of my trouble reading the articles around it and the changelog from MSI.
If anyone else reading this has a sophisticated setup and has installed the UEFI Update, and is now affected contact your Mainboard vendor support/ OEM and pointing to the next gen CPU support as a possible reason.
https://thewindowsclub.blog/de/msi-fixes-the-unsupported-processor-blue-screen-of-death-error/
- here is a mention of this issue related to Windows 11 insider and Server insider builds
https://borncity.com/win/2022/08/28/vmware-workstation-unsupported_processor-fehler-bei-windows-11-insider-und-server-2022/ - Joachim_OtahalIron ContributorBIOS/UEFI update. Some MSI mainboards currently have a similar issue with Windows 11.
- It'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_OtahalIron 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.