A memory leak in Windows 11’s File Explorer is holding users’ RAM hostage

Share on facebook
Facebook
Share on twitter
Twitter
Share on linkedin
LinkedIn
Share on reddit
Reddit
Share on telegram
Telegram
Share on email
Email

Memory leaks aren’t a new thing for Windows users. Programs pop up from time to time using more RAM than they’re meant to, but for those thinking of switching over to Windows 11 tomorrow there’s something to bear in mind, in that you could be faced with memory leak issues caused by the OS’s own File Explorer.

If you aren’t aware of memory leaks as a concept, they’re essentially what happens when a certain process that’s been running on your PC refuses to release the cache memory space it’s been assigned. Sometimes the RAM doesn’t free up even long after the program’s window has been closed, and that horded memory can cause all sorts of problems by slowing down your machine, and in extreme instances causing it to become unresponsive.

The Windows 11 File Explorer memory leak bug, which surfaced a couple of months ago thanks to the keen eyes of one Windows 11 Insider preview user, is outlined in a post by user gyrohan269 on the Windows 11 subreddit. They note that with each instance of Windows File Explorer opened, the RAM usage stacks and doesn’t disperse upon exiting. The post was met with thousands of upvotes from those with a similar issue, and plenty of comments from users who were able to replicate the issue.

We’re currently running version 22000.194 (which we believe is the release version) on our test bench, and I was able to reliably replicate the bug several times. And, no, the RAM usage still hadn’t freed up even after about half an hour of waiting.

If you want to check if this is a problem for your own Windows 11 version, open Task Manager now and sort your processes by highest memory usage, then spam Win+E. You’ll notice Explorer rise up the list pretty fast, and once you’ve closed them all keep an eye out to see if the memory frees up.

There doesn’t seem to be an official acknowledgement of the issue anywhere, let alone news of a coming fix. Thankfully it has been logged in the Feedback Hub so, if you can replicate it, do pile in so Microsoft are aware it’s a wide-ranging issue.

Of course you can always restart the Windows File Explorer process manually to free up the cache from within the Task Manager, or prepare for trouble with one of the best RAM kits. But those who aren’t aware of the problem could end up with a pretty clogged cache on upgrading to Windows 11.

Users sporting minimal RAM sizes, and those who don’t often restart their PCs, could be faced with major issues if the problems surrounding File Explorer’s RAM usage aren’t rectified.

Article source: PCGamer

You might also enjoy