Forum Discussion
B25941 - booting ISO fails with STOP UNSUPPORTED_PROCESSOR - SOLVED
- 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!
"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.
the upgrade issue from WS 2022 to Windows_InsiderPreview_Server_vNext_en-us_25941 seems unrelated to the UNKNOWN_PROCESSOR issue.
There are vssadmin and diskshadow with different capabilities.
Finally got setupdiag results indicating an issue that a snapshot could not be removed. vssadmin also stated that the snapshot could not be deleted. However bing GPT helped me and I learnt about another command "diskshadow" which appears similar to vssadmin but was successful to delete this particular snapshot. Trying the IPU once again.
to avoid misunderstanding WS 2022 is on an isolated NVMe so cannot be prone to cause issues with too many primary partitions.
OT: unlike my Windows Client NVMe. However I reduced the number of partitions with Minitool Partition Wizard.
Partitioning tool, why we still need 3rd party in 2023?
Despite the new partition tool is amazing in settings app, I am quite sad that resizing, deletion and moving partitions is still not natively supported by Microsoft, and I really wonder why this is the case.
Please integrate setupdiag into any current mainstream supported OS
Secondly I would like to plea that Windows Setup should also place the latest setupdiag.exe in c:\windows\system32 by default. It is quite unusual it is still a seperate download, while included in ISO sources dir, but not in the OS. It could be maintained with an auto-updater or CUs.
- Hi there,
I can confirm there is a relation between the current UEFI updates to support yet unreleased Intel CPUs, and this issue.
I have had luck to change the Mainboard to MSI and applied the latest Update that is intended to fix a BSOD state with Windows 11 and the new "next gen" CPU compatibility.
If you are affected in your hardware based home lab, contact your mainboard vendor Support and point them here.