A recent Windows 11 update (which also came to Windows 10) has been causing some serious problems for some users – and it seems Microsoft is trying to pass the buck.
As Bleeping Computer reports, some people who installed the optional August 2023 updates for Windows 11 or Windows 10 were getting the dreaded Blue Screen of Death, where their PC stops responding, with the error being labelled as an ‘UNSUPPORTED_PROCESSOR’ issue.
In a statement posted on its ‘Release Health’ website, that tracks known issues, Microsoft states that the “’UNSUPPORTED_PROCESSOR’ error was not caused by issues in KB5029351 and is limited to a specific subset of processors.”
Microsoft claims it is “collaborating with device manufacturers (OEMs)” by pausing the update being offered to Windows devices that may be affected.
If the KB5029351 is already installed and causing an issue, it will automatically uninstall, which should fix the issue.
Whose fault is it anyway?
Microsoft is usually pretty good at being transparent about Windows 11 problems, so it’s interesting that with this one, it’s saying that the error isn’t being caused “by issues in KB5029351” and that you should “contact your device’s processor manufacturer” if the problem persists.
That seems to be washing its hands of the problem a bit. After all, this issue only affects the KB5029351 update – and presumably these unsupported processors work fine with other Windows 10 and Windows 11 updates.
You’d also think it would be easier for Microsoft to release an update that was supported by these processors, rather than have the processor makers build their chips to be compatible with all future Windows updates.
It all seems a bit odd, but there must be some reasoning behind Microsoft’s blame game. The good news, at least, is that this only affects an optional update, which means it’s not going to be forced on you, and the fix seems relatively easy to apply.
Whether or not device manufacturers will be happy with Microsoft pointing the finger at them over this latest Windows 11 problem, however, is another story.