Home windows 10 customers are struggling by the hands of some contemporary bugs launched by the most recent replace for the OS from Microsoft.

That might be KB5026361, the cumulative replace for Home windows 10 for Could, which was launched a few weeks again, and seems to be inflicting a bunch of glitches and extra severe issues.

Within the severe class we will file some Reddit customers who’re complaining on two counts of the patch ‘bricking’ their PC, and likewise stories of Blue Display screen of Loss of life (BSoD) crashes post-update.

A few of these BSoDs supply up an error that reads ‘Process1 Initialization Failed’ and as Neowin, which noticed this, explains, this seemingly happens because of the Bootcat.cache file changing into corrupted (or its dimension having modified because the final time the PC booted).

Different Home windows 10 customers are encountering an issue that’ll sound acquainted, little doubt – the failure to put in the replace, usually accompanied with a meaningless error code (resembling ‘0x800f0922’ which seems to be one of many extra prevalent occurrences on this case).

On high of that, there are scattered complaints resembling somebody’s Home windows 10 mouse settings being reset after the replace (and a few earlier updates too, we’re informed).

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

Evaluation: One other replace and but extra issues

Provided that there are solely two stories of bricked PCs, we will’t leap to conclusions – there may presumably be different points at play in these cases. Nonetheless, it’s worrying to see such stories, even when this clearly isn’t a widespread downside. BSoD crashes are a nasty factor to be taking place right here, too.

It’s not shocking to see set up failures with the cumulative replace for Could, as this bugbear is one Microsoft simply can’t appear to shake, in Home windows 11 in addition to Home windows 10.

As for the ‘Process1 Initialization Failed’ downside, Neowin does level out that Microsoft has a treatment for that exact error – although the catch is that it’s for Home windows 7 formally (by way of an previous assist doc).

The strategy suggests booting with a Home windows set up USB drive, then deleting the problematic Bootcat.cache file, earlier than restarting the PC. We’re unsure that’s a good suggestion, although – and positively not one thing for these much less assured with PCs to strive – however extra tech-savvy varieties may all the time try it as a final resort if determined.

Hopefully, Microsoft will likely be wanting into these points, and fixes will likely be carried out as wanted. Though today, we get the sense that Microsoft is focusing much more on Home windows 11 than Home windows 10, what with the latter getting no extra options any further (save for, maybe, the odd very minor tweak).

Nonetheless, on the brighter facet, no extra options ought to imply fewer bugs being launched – in concept, anyway.