Windows 11 update crashes and burns on some PCs due to ‘unsupported CPU’ error

Windows 11 has a new spanner in the works with the latest update for the operating system, a worrying one that crashes the PC with an ‘unsupported processor’ error.

The Verge reports that they – and other folks on Reddit – have experienced this error, and that it happened after installing the KB5029351 update for Windows 11 22H2. Note that this is a preview update, so it’s optional and doesn’t have to be installed (it won’t be downloaded unless you manually check for updates and choose to do so).

In affected cases, after installing the update, a Blue Screen of Death appears with the mentioned error message about the CPU not being supported by Windows 11, and the PC then reboots.

The good news is that the system apparently recovers and rolls back the patch, according to reports (and The Verge says this is what happened to them).

Microsoft has acknowledged the problem, and advises: “KB5029351 might automatically uninstall to allow Windows to start up as expected.”

The common factor among those who have encountered this bug is that they have an MSI motherboard (with an Intel CPU) that has been updated to the most recent BIOS release.

Microsoft informs us: “We are presently investigating to determine if this is an issue caused by Microsoft. We will provide an update when more information is available.”

Analysis: Prevention measures in place – but there’s still scope for concern

While we’re all likely aware that Windows 11 brought in some much stricter requirements for supported CPUs compared to Windows 10, being told that their processor was unsupported probably caused a few folks to almost fall out of their chairs.

As reported, the error should allow the PC to reboot and uninstall the update to go back to normal, but Microsoft’s use of the term ‘might’ automatically uninstall in its advisory does leave some room for concern. What if it doesn’t? That could be a nasty problem indeed.

The good news is that Microsoft has now instigated measures to prevent the Windows 11 update in question from being delivered to PCs that will be affected (those with Intel chipset-toting MSI motherboards on that most recent BIOS). So, at this point, you don’t have to worry – if you do fall into this group of PC owners, the patch will be pulled, and you won’t be offered it under Windows Update.

The remaining concern, then, is that this optional preview patch becomes the full (mandatory) update for Windows 11 22H2 in September. So Microsoft will have to make very sure this bug is fully squashed by that time – or that MSI addresses it with a new BIOS update that happens in a swift manner, if it isn’t a glitch in the Windows matrix.

You might also like

TechRadar – All the latest technology news

Read More

Microsoft hasn’t forgotten about Windows 10, as a vital fix for game crashes finally arrives

Windows 10 gamers have got a reason to celebrate with the latest preview update for the OS, which comes with an important fix for a nasty gaming-related crash, and other cures besides.

The problem with PC games is related to Timeout Detection and Recovery (TDR) errors popping up, either causing a crash, or even locking up the system in some more extreme cases.

As you may have seen, the fix for this was applied to Windows 11 in the Moment 3 update – it was first spotted in the preview of that patch which emerged late in June.

The good news for Windows 10 users is that the fix is in KB5028244 (build 19045.3271 for Windows 10 22H2), which again is a preview patch (an optional download). This means the full (polished) fix will be available in August’s cumulative update for Windows 10, and that’s only a couple of weeks away now.

In the release notes for the patch, Microsoft observes: “This update addresses an issue that might affect your computer when you are playing a game. Timeout Detection and Recovery (TDR) errors might occur.”

On top of this, there are fixes for a bug that prevents some VPN apps from making a successful connection, and a glitch that means when a PC comes back from sleep, certain display or audio devices go missing in action.

Furthermore, there’s the resolution of a problem with Windows 10 where a full-screen search can’t be closed (and prevents any further action from being taken with the Start menu), and a raft of other tweaks and fixes.

Analysis: A welcome fix, albeit slightly late

There are some important cures here, then, as those mentioned bugs are quite a pain for those affected.

PC gamers on Windows 10 – the vast majority still – were particularly miffed when Windows 11 got a solution for the TDR crashes in June, with Microsoft leaving them in the lurch. And with no mention of Windows 10 back at the time, some gamers were even talking about this being a reason to upgrade to Windows 11 – that’s how annoyed some folks are by this one.

As one Reddit user put it: “Windows 10 TDR errors have been the bane on [sic] my life.”

At any rate, the fix is now here, and hopefully it’ll prove effective on Windows 10. Of course, right now it’s still testing as an optional update, so you’ll have to manually grab the patch via Windows Update, and there may still be problems with it. That said, those affected by TDR crashes might be so keen to get rid of them that any risk of side effects elsewhere may seem a small price to pay.

Whatever the case, as mentioned, the full fix should be coming in the cumulative update for Windows 10 next month (assuming no problems are encountered in this final testing phase).

Clearly, Windows 11 has priority as Microsoft develops and tinkers with its desktop operating systems, but it feels an odd situation where two-thirds of gamers are still on Windows 10, and are getting the short end of the stick with fixes like this.

TechRadar – All the latest technology news

Read More

Windows 10 update is causing lots of problems – including nasty crashes

Windows 10 users are suffering at the hands of some fresh bugs introduced by the latest update for the OS from Microsoft.

That would be KB5026361, the cumulative update for Windows 10 for May, which was released a couple of weeks back, and appears to be causing a bunch of glitches and more serious problems.

In the serious category we can file some Reddit users who are complaining on two counts of the patch ‘bricking’ their PC, and also reports of Blue Screen of Death (BSoD) crashes post-update.

Some of those BSoDs offer up an error that reads ‘Process1 Initialization Failed’ and as Neowin, which spotted this, explains, this seemingly occurs due to the Bootcat.cache file becoming corrupted (or its size having changed since the last time the PC booted).

Other Windows 10 users are encountering a problem that’ll sound familiar, no doubt – the failure to install the update, often accompanied with a meaningless error code (such as ‘0x800f0922’ which appears to be one of the more prevalent occurrences in this case).

On top of that, there are scattered complaints such as someone’s Windows 10 mouse settings being reset after the update (and some previous updates too, we’re told).

Others have lodged complaints about bugs with KB5026361 in Microsoft’s Feedback Hub, and another report from a Redditor states that their laptop’s Wi-Fi doesn’t work, and that the ‘windows bar is locked’ (presumably the taskbar is unresponsive) after the update.

Analysis: Another update and yet more problems

Given that there are only two reports of bricked PCs, we can’t jump to conclusions – there could possibly be other issues at play in those instances. Still, it’s worrying to see such reports, even if this clearly isn’t a widespread problem. BSoD crashes are a nasty thing to be happening here, too.

It’s not surprising to see installation failures with the cumulative update for May, as this bugbear is one Microsoft just can’t seem to shake, in Windows 11 as well as Windows 10.

As for the ‘Process1 Initialization Failed’ problem, Neowin does point out that Microsoft has a cure for that particular error – though the catch is that it’s for Windows 7 officially (via an old support document).

The method suggests booting with a Windows installation USB drive, then deleting the problematic Bootcat.cache file, before restarting the PC. We’re not sure that’s a good idea, though – and certainly not something for those less confident with PCs to try – but more tech-savvy types could always attempt it as a last resort if desperate.

Hopefully, Microsoft will be looking into these issues, and fixes will be implemented as needed. Although these days, we get the sense that Microsoft is focusing far more on Windows 11 than Windows 10, what with the latter getting no more features from now on (save for, perhaps, the odd very minor tweak).

Still, on the brighter side, no more features should mean fewer bugs being introduced – in theory, anyway.

TechRadar – All the latest technology news

Read More