Windows 11 update is reportedly causing some PCs to crash or run very sluggishly

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.

However, some Windows 11 users have hit major snags when installing the March update, with Windows Latest highlighting these, and the site experiencing a Blue Screen of Death (BSoD) itself after running the update process.

The tech site’s BSoD arrived with an error saying ‘Thread Stuck in Device Driver’ which isn’t very helpful, and others have been hit by this problem, such as a reader running a bunch of Lenovo devices (in a business setting).

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?”

Someone chimes in to say they were affected too (and got put in a boot loop, with repeated reboots, before ending up at that BSoD).

There are other reports on this thread noting that the update did install, but then caused ‘random’ BSoDs afterwards.

On top of this, there are also folks who are complaining about Windows 11 running sluggishly, with their PC stuttering after the update, or even freezing up periodically.


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.

You might also like…

TechRadar – All the latest technology news

Read More

Windows 11 hack keeps your PC alive (sort of) after a Blue Screen of Death crash

A Blue Screen of Death (BSOD) in Windows 11 is when the PC locks up entirely, with no possible recourse – except to reboot there and then – unless you’ve hacked the operating system, that is.

Tom’s Hardware reports that NTDEV, the maker of Tiny11 (a lightweight version of Windows 11) flagged up on X (formerly Twitter) that NSG650 has a project on GitHub which is a driver that modifies the normal BSOD behavior, firing up a Linux emulator when a crash occurs.

In other words, instead of just having the option to reboot, you get a RISC-V Linux emulator popping up post-crash. How is this done? It leverages the bugcheck callback feature in Windows – which is part of the BSOD process, and allows for code to run after a crash – and in this case, the code inserted brings up the emulator.

Now, all the Linux emulator consists of is a basic command line (like the old days of DOS, just a text interface), and you can’t really do anything with it – it’s just showing what can be done (see the video clip below), rather than actually implementing anything useful.


Analysis: An opportunity for Microsoft?

With this methodology discovered, this raises the question that with some work, could something more advanced be concocted along these lines? Something that does allow you to do useful things after a BSOD, like plug in a USB drive and back up files, for example, if you’re worried they might be corrupted. Or maybe to run some kind of lightweight recovery utility.

Having seen this in action, though, it’s entirely possible Microsoft will patch this out, as it could be seen as a security risk in Windows 11 (and Windows 10 for that matter).

However, we can but hope that it might inspire Microsoft to look at doing something more useful, as mentioned, with the BSOD, and allowing at least some post-crash options, if indeed it’s possible to work anything meaningful in that way – which we don’t know, we should add.

For the moment, this little trick remains an interesting novelty, with a tantalizing possibility that it could become more than that in the future. Whatever the case, even if nothing happens along those lines, we think Microsoft could definitely improve BSODs in other ways – though if you happen to encounter one, at least we have a Blue Screen of Death survival guide.

You might also like…

TechRadar – All the latest technology news

Read More