Friday, August 25th 2023

MSI Statement on "Unsupported Processor" Error Message of Windows 11 Update KB5029351 Preview

Press Release by
btarunr
 Discuss (10 Comments)
MSI has received several reports of users encountering a Blue Screen of Death that has an error message that reads "UNSUPPORTED_PROCESSOR" with MSI's 600/700 series motherboards after installing the Windows 11 update, KB5029351 Preview. Both MSI and Microsoft are aware of the "UNSUPPORTED_PROCESSOR" error and have begun investigating the root cause. While the investigation is underway, we recommend that all users temporarily refrain from installing the KB5029351 Preview update in Windows. We will keep you updated on the progress of our investigation.
Temporary Workaround
If you have already encountered this issue, KB5029351 might automatically be uninstalled to allow Windows to restore to normal. However, if KB5029351 is not automatically uninstalled, we recommend reverting your BIOS to the previous version and uninstalling KB5029351 from Windows.

If you are unsure of how to restore to older BIOS, this video link will help you on how to flash BIOS on MSI motherboards. More information on KB5029351 can be found here.

Related News

Add your own comment

10 Comments on MSI Statement on "Unsupported Processor" Error Message of Windows 11 Update KB5029351 Preview

#1
SimpleTECH
Interesting I had this problem with an ASUS motherboard (ProArt Z690-CREATOR WIFI) and an Intel i7-13700K. But after restarting a few times, having Windows uninstall/revert the update, I redownloaded it again and after restarting it was fine. In fact, the latest 22631.2262 that came out yesterday has been okay.
Posted on Reply
#2
LabRat 891
Peculiar. This is the same kinda error you get trying to install 64-bit Windows 8.1 or newer on a DDR1 K8.

I find it funny that modern PC owners are getting the same error the Retro community just has to 'deal with'.
Posted on Reply
#3
RJARRRPCGP
At this rate, people are likely surprised that they still have yet to be aware of Microsoft enforcing the pre-Coffee Lake and pre-Pinnacle Ridge processor ban with that stop code.

If Microsoft bans those processors at the kernel level, then it's game over for the Rufus workarounds! Then it means no more 11 for Haswell.
LabRat 891Peculiar. This is the same kinda error you get trying to install 64-bit Windows 8.1 or newer on a DDR1 K8.

I find it funny that modern PC owners are getting the same error the Retro community just has to 'deal with'.
More like what I would expect, if I try to use Windows 11 on a 65nm Core 2, LOL.

Now about the Windows version of a kernel panic=Was there a whoops made by MSI, where the processor information was missing, or did the new BIOS make the CPU unstable, even when I never got that stop code for even an insanely unstable CPU core OC.
Posted on Reply
#4
Dr. Dro
RJARRRPCGPAt this rate, people are likely surprised that they still have yet to be aware of Microsoft enforcing the pre-Coffee lake and pre-Pinnacle Ridge processor ban with that stop code.

If Microsoft bans those processors at the kernel level, then it's game over for the Rufus workarounds! Then it means no more 11 for Haswell.


More like what I would expect, if I try to use Windows 11 on a 65nm Core 2, LOL.

Now about the Windows version of a kernel panic=Was there a whoops made by MSI, where the processor information was missing, or did the new BIOS make the CPU unstable, even when I never got that stop code for even an insanely unstable CPU core OC.
65 nm Core 2 (Conroe) has a more advanced instruction set than the Phenom II. It's not really important, both should run Windows 11 as it stands today.

This just seems like a weird bug. I wasn't affected, even on a system where it could happen (latest 14th-gen compatible BIOS, 13th gen i9 CPU + Z690 motherboard)
Posted on Reply
#5
Mussels
Freshwater Moderator
So their solution is to do nothing?
What's going to happen if someone has those new CPU's and wants to use them with that BIOS?
Posted on Reply
#6
Dr. Dro
MusselsSo their solution is to do nothing?
What's going to happen if someone has those new CPU's and wants to use them with that BIOS?
I think MS has already fixed or pulled the update :confused:
Posted on Reply
#7
Mussels
Freshwater Moderator
Dr. DroI think MS has already fixed or pulled the update :confused:
It's a weird combination.
It only affected MSI boards with a BIOS for upcoming CPUs (why was it public in the first place?) using windows 11 that received that update.


It automatically uninstalled after a few reboots of the error, so no one was ever stuck with a dead PC because of this.
Posted on Reply
#8
Dr. Dro
MusselsIt's a weird combination.
It only affected MSI boards with a BIOS for upcoming CPUs (why was it public in the first place?) using windows 11 that received that update.


It automatically uninstalled after a few reboots of the error, so no one was ever stuck with a dead PC because of this.
I wonder if it's only for the Z790s, BIOS 1.C0 (released July 21) on the Z690 Ace here seemed ok
Posted on Reply
#9
Mussels
Freshwater Moderator
Dr. DroI wonder if it's only for the Z790s, BIOS 1.C0 (released July 21) on the Z690 Ace here seemed ok
Whatever BIOS it was, added support for 14th gen but also somehow renamed the 13th gen CPUs - it's entirely likely it was just a typo from MSI and everyones blown it into a massive issue for windows.
Posted on Reply
#10
Dr. Dro
The Z690 Ace just received a 1.D0 BIOS update that aims to fix this specific issue, 1.C0 was pulled from the MSI website.
Posted on Reply
Nov 22nd, 2024 10:30 EST change timezone

Latest GPU Drivers

New Forum Posts

Popular Reviews

Controversial News Posts