Windows 11’s cumulative update for this month is causing serious problems in some reported cases.
This is KB5035853 for Windows 11 23H2 and 22H2 which started rolling out earlier this week carrying some useful new features. That includes being able to use the Snipping Tool to edit photos from your Android smartphone directly on your PC, plus adding support for much faster (80Gbps) wired connectivity with USB4 v2.0.
Furthermore, there’s evidence of this nasty crash on the Reddit thread introducing KB5035853. One user tells us: “This update caused a Windows to crash on startup. Got blue screen error. Had to rollback. Just a warning. That happen to anyone else?”
There are other reports on this thread noting that the update did install, but then caused ‘random’ BSoDs afterwards.
Analysis: Fixing with one hand, breaking with the other?
These are really unpleasant side-effects here, and the cure so far seems to be simply rolling back the installation (removing KB5035853, or using System Restore to rewind time back to before the update was triggered).
On Reddit, there is a mention of a YouTube video that offers potential solutions, and we’ve had a look – there are a couple of clips, in fact – but we’d take the advice imparted with a hefty pinch of salt. Some folks in the YouTube comments have reported seeing success, and others have said the fixes outlined have failed. But for now, rather than trying what seems like shots in the dark as attempted cures, if you’re affected, we’d probably just go for reverting the update and waiting for Microsoft to investigate these glitches.
(It’s worth noting that in the YouTube comments there are also further complaints of PCs seriously chugging with slowdown post-update).
At the moment, Microsoft’s support document for the March cumulative update indicates there are no known issues.
The irony here is that this March update addresses a problem with the February update for Windows 11 whereby it failed to install (and got stuck at 96% complete with an error code and a helpful message saying that ‘something did not go as planned’). So, the patch curing that problem with the previous patch failing to install, also fails to install in a different, and in fact worse, way.
Hopefully Microsoft is on the case with this one as we type this. It’s difficult to say how widespread the BSoD problem is, but there are certainly enough reports of post-installation performance blues to suggest that something has gone awry with KB5035853.