Windows 11’s cumulative replace for this month is inflicting severe issues in some reported circumstances.
That is KB5035853 for Windows 11 23H2 and 22H2 which began rolling out earlier this week carrying some helpful new options. That features with the ability to use the Snipping Tool to edit photos from your Android smartphone straight in your PC, plus including assist for much faster (80Gbps) wired connectivity with USB4 v2.0.
Nonetheless, some Home windows 11 customers have hit main snags when putting in the March replace, with Windows Latest highlighting these, and the location experiencing a Blue Display screen of Dying (BSoD) itself after working the replace course of.
The tech website’s BSoD arrived with an error saying ‘Thread Caught in Gadget Driver’ which isn’t very useful, and others have been hit by this drawback, corresponding to a reader working a bunch of Lenovo units (in a enterprise setting).
Moreover, there’s proof of this nasty crash on the Reddit thread introducing KB5035853. One consumer tells us: “This replace triggered a Home windows to crash on startup. Obtained blue display screen error. Needed to rollback. Only a warning. That occur to anybody else?”
Somebody chimes in to say they have been affected too (and bought put in a boot loop, with repeated reboots, earlier than ending up at that BSoD).
There are different experiences on this thread noting that the replace did set up, however then triggered ‘random’ BSoDs afterwards.
On high of this, there are additionally people who’re complaining about Home windows 11 working sluggishly, with their PC stuttering after the replace, and even freezing up periodically.
Evaluation: Fixing with one hand, breaking with the opposite?
These are actually disagreeable side-effects right here, and the treatment up to now appears to be merely rolling again the set up (eradicating KB5035853, or utilizing System Restore to rewind time again to earlier than the replace was triggered).
On Reddit, there’s a point out of a YouTube video that gives potential options, and we’ve had a glance – there are a few clips, actually – however we’d take the recommendation imparted with a hefty pinch of salt. Some people within the YouTube feedback have reported seeing success, and others have mentioned the fixes outlined have failed. However for now, slightly than attempting what looks like pictures at the hours of darkness as tried cures, should you’re affected, we’d in all probability simply go for reverting the replace and ready for Microsoft to analyze these glitches.
(It’s value noting that within the YouTube feedback there are additionally additional complaints of PCs significantly chugging with slowdown post-update).
In the meanwhile, Microsoft’s support document for the March cumulative replace signifies there are not any identified points.
The irony right here is that this March replace addresses an issue with the February replace for Home windows 11 whereby it failed to put in (and bought caught at 96% full with an error code and a useful message saying that ‘one thing didn’t go as deliberate’). So, the patch curing that drawback with the earlier patch failing to put in, additionally fails to put in in a special, and actually worse, manner.
Hopefully Microsoft is on the case with this one as we sort this. It’s tough to say how widespread the BSoD drawback is, however there are actually sufficient experiences of post-installation efficiency blues to recommend that one thing has gone awry with KB5035853.
Discussion about this post