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.
