Windows 11 bug that made some users wrongly suspect they’d been hacked has finally been fixed – but it took Microsoft over a year
Weird and worrying File Explorer bug is cured with December update
Microsoft has fixed a bug in Windows 11 that has been hanging around forever, pretty much – or for over a year anyway.
In fact, as Windows Latest observes, it took Microsoft fifteen months to fix the problem with File Explorer whereby it would simply pop into the foreground with no warning.
In other words, you might be busy working away at some task or other and File Explorer suddenly appears on top of all your other windows, for absolutely no reason.
An odd problem indeed, but we’re told that the cure is packaged up in the latest update for Windows 11. That’s the recently released cumulative update for December, also known as patch KB5033375.
Microsoft notes: “This update addresses an issue that affects File Explorer windows. When you do not expect them, they appear in the foreground.”
The bug seems to happen randomly on affected PCs, and worse still, Windows Latest says that it can occur on a roughly hourly basis in some scenarios, which is way too regularly for our liking.
Analysis: False hacking suspicions
The thing about this bug is that it isn’t just a distraction or annoyance, but more than this, it may make some Windows 11 users wrongly suspect that they’ve been hacked. After all, your PC doing things of its own accord, when you’re not touching the keyboard or the mouse perhaps, is a sign of potential compromise – and certainly a freaky thing to experience if nothing else.
Get the best Black Friday deals direct to your inbox, plus news, reviews, and more.
Sign up to be the first to know about unmissable Black Friday deals on top tech, plus get all your favorite TechRadar content.
In this respect, the File Explorer bug may have caused some undue worry on the part of those experiencing it, who may have been running virus scans and all sorts of other carry-on, imagining that there could be a potential breach of security on their system somewhere.
It’s good that this is fixed, but it should never take more than a year for a problem to be banished from Windows 11. There have certainly been some relieved users we’ve seen on the likes of Reddit rejoicing that this gremlin in the works has finally been dealt with, while scratching their heads at just how long it took Microsoft to untangle this one.
You might also like...
Darren is a freelancer writing news and features for TechRadar (and occasionally T3) across a broad range of computing topics including CPUs, GPUs, various other hardware, VPNs, antivirus and more. He has written about tech for the best part of three decades, and writes books in his spare time (his debut novel - 'I Know What You Did Last Supper' - was published by Hachette UK in 2013).