On July 28, tech outlet BGR spotlighted a Reddit post that stopped many Windows users mid-scroll: Windows Explorer was sitting on 21 GB of RAM. For context, that’s more memory than a basic laptop ships with, and it was all attributed to the process that draws your desktop, taskbar, Start menu, and file browser. This wasn’t a one-off glitch—Explorer memory leaks have shadowed Windows 11 since its 2021 launch—but the 21 GB figure put a brutal number on a daily nuisance that leaves PCs stuttering and unresponsive.

The Reddit user’s system reported only 52 percent memory utilization at the time, so they clearly ran a high-RAM machine. But on a 4 GB or 8 GB device, even a 2 GB Explorer footprint can grind everything to a halt. The timing is telling: reports of Explorer going rogue have ticked up in community forums and social media over the last year, often tied to cumulative Windows updates that patch one thing and quietly nudge another out of balance.

What’s actually happening inside Explorer

Explorer.exe is not merely the window you use to browse Documents or Downloads. It is the Windows shell—a host process that also manages the desktop, taskbar, notification area, and all those right-click context menus. And because Microsoft’s extensibility model invites third-party software to bolt on features inside that same process, any errant add-on can hijack Explorer’s memory. A classic memory leak occurs when a program allocates RAM, finishes its job, but never releases the memory back to the operating system. Over hours or days, the committed memory climbs inexorably.

What the 21 GB incident underscores is not that Windows itself has a single catastrophic leak, but that the ecosystem of extensions, preview handlers, and cloud sync providers now layered onto Explorer creates an attack surface for runaway memory consumption. BGR’s report noted that some users have seen Explorer creep past 2 GB, but the 21 GB outlier shows how a leak can balloon if left unchecked on a system with abundant RAM—masking the problem until the PC becomes unusable.

Microsoft’s own developer documentation is blunt about the risks: “Shell extension handlers are in-process Component Object Model (COM) DLLs that are loaded into the Explorer process. Therefore, a crash or hang in a shell extension handler can crash or hang Explorer.” That same architecture also allows a poorly written thumbnail generator, cloud overlay status icon, or archive utility to siphon memory without ever being identified in Task Manager’s “Processes” tab—all the user sees is a bloated Explorer.

What it means for you

If you’re a home user on a budget laptop with 4 GB or 8 GB of RAM, an Explorer process hogging 1.5–3 GB can make the entire system feel broken. Clicks lag, the Start menu freezes, right-click menus take seconds to appear, and File Explorer windows refuse to open. The experience is indistinguishable from a machine infected with malware, even though the culprit is often a legitimate—if buggy—application.

Power users and IT admins face a subtler headache: the very tool they use to manage files becomes the bottleneck. An admin trying to copy deployment packages or sort through server shares might find Windows Explorer unresponsive, when the actual issue is a preview handler trying to render a video file or a sync client hammering status checks. The symptom is universal slow-down, but the root cause is hidden inside Explorer’s crowded process space.

Developers who craft shell extensions should pay close attention. Microsoft advises that context-menu commands “should keep menu-construction work fast and avoid expensive processing on the user interface thread.” When that guidance is ignored—or when an extension hits an edge-case file—the result is exactly the memory inflation users are complaining about. And since Explorer loads all handlers into one process, a single faulty extension can taint the experience of every other add-on.

How we got here

Explorer’s dual role as file manager and shell dates back to Windows 95, but the addition of cloud storage, rich previews, and extensive context menus has amplified the risk. Windows 11’s new File Explorer brought tabs, a redesigned Home view that surfaces recent Office.com files, and tighter integration with OneDrive. Each of those integrations generates additional work that Explorer must perform—metadata queries, thumbnail generation, sync status overlays, and cloud file hydration checks. Multiplied across dozens of installed applications, the potential for a runaway allocation is enormous.

Microsoft delivers monthly cumulative updates that sometimes quietly patch Explorer stability issues, but the company rarely calls out a specific “memory leak fix.” The Reddit post that BGR covered is not an isolated anomaly; similar complaints have surfaced in Windows 11’s Feedback Hub, on Microsoft’s community forums, and on Reddit over the past 18 months. The 21 GB figure, however, grabbed mainstream attention because it was so extreme and because it came from an average user, not an IT lab.

Cloud storage clients are frequent culprits. OneDrive, Google Drive, Dropbox, and others inject overlay icons and context-menu entries that must constantly re-validate file states. If a sync engine encounters a locked file, a network hiccup, or a sheer volume of changes, Explorer can get stuck repeatedly querying that information without releasing memory. The same pattern appears with media preview handlers: codecs that parse high-resolution images, videos, or PDFs sometimes leak memory after drawing thumbnails.

Importantly, not every high memory reading signals a leak. Opening a folder stuffed with 10,000 raw photos will legitimately spike Explorer’s RAM while it builds thumbnails. The question is whether that memory returns to a baseline after the folder is closed. A true leak builds and never recedes; a temporary spike is just Explorer doing its job.

What to do now

Immediate relief: restart Explorer

When your desktop freezes or the Start menu refuses to open, the quickest remedy is also the one Microsoft itself documents: restart Windows Explorer through Task Manager. Press Ctrl+Shift+Esc, find “Windows Explorer” in the list, right-click it, and choose Restart. The screen may flicker, open File Explorer windows will close, but within seconds the shell reloads, releasing all memory held by the old process. This doesn’t fix the underlying problem, but it buys you a working session.

Install pending Windows updates and reboot

Next, check for system updates. Go to Settings > Windows Update > Check for updates. Install everything offered—including optional quality updates that sometimes carry Explorer fixes—then restart. Microsoft’s File Explorer support page explicitly recommends this step before any deeper troubleshooting. A clean boot often scrubs away transient glitches that accumulate during long uptimes.

Identify the trigger with methodical testing

Blindly uninstalling programs won’t help. Instead, restart Explorer, note its memory in Task Manager (use the “Memory” column), then perform one action at a time:
- Open a folder with many images or videos
- Browse a network share
- Navigate a OneDrive or other cloud-synced folder
- Right-click a file and observe context menus
- Use the Preview pane (View > Preview pane)
After each step, close the window and recheck memory. If Explorer’s footprint climbs and refuses to drop back, you’ve found a suspect folder, file type, or integration.

Toggle the Preview pane off as an experiment. Switch the folder to a plain list or details view instead of large thumbnails. If memory stabilizes, a preview handler or thumbnail generator is likely leaking. The goal is to narrow the field, not to permanently disable all thumbnails.

Purge problem extensions with a clean boot

Because third-party shell extensions run inside Explorer, a clean boot is the gold standard for diagnosis. Microsoft’s procedure uses msconfig to disable all non-Microsoft services and Task Manager’s Startup tab to prevent apps from launching at sign-in. Reboot, then test Explorer in this isolated state. If the memory growth disappears, you know the cause lives among your regular startup programs.

Microsoft’s guidance recommends re-enabling items in small groups and rebooting each time until the misbehaving service or app is identified. Keep a list of what you disable—VPN clients, security suites, cloud sync tools, printer utilities, audio managers, and file metadata indexers are common suspects.

Use Process Explorer to catch the real culprit

Task Manager tells you Explorer is bloated; Process Explorer (free from Microsoft’s Sysinternals) tells you which DLL inside Explorer is bloating it. Launch Process Explorer, select explorer.exe, and switch to the DLL view. Look for non-Microsoft DLLs that consume unusual amounts of memory or correspond to recently installed software. If a specific context-menu handler, preview extension, or sync overlay appears, that’s your likely source.

Process Explorer can also display handles and memory-mapped files, which helps when a single file or network location is repeatedly being opened and not closed.

Repair Windows system files—but only when warranted

If Explorer misbehaves even in a clean boot, two command-line tools can check for OS corruption. From an elevated Command Prompt or Terminal, run:

DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

Microsoft recommends DISM first, because it can fetch healthy files from Windows Update to fix the component store. SFC then scans protected system files and replaces damaged copies using that repaired store. This duo is effective for system-level corruption—Explorer crashes, blank desktop icons, or shell instability—but it won’t cure a leaky third-party extension.

What not to do

Avoid so-called “RAM cleaner” or “memory optimizer” utilities. They forcefully trim working sets, which can make performance worse by discarding cached data that Windows would otherwise reuse. Restarting Explorer, updating Windows, and isolating extensions are far more reliable. Also, resist the urge to reinstall Windows unless all other steps fail; a clean boot and Process Explorer will usually pinpoint the trouble without such a drastic measure.

Outlook

Microsoft continues to refine File Explorer with each feature update, but the fundamental architecture—loading third-party code into a single process—won’t vanish overnight. The company has experimented with sandboxed or out-of-process extensions, but backward compatibility makes a sweeping change difficult. In the near term, Windows users should treat Explorer memory leaks as a manageable, diagnosable problem rather than a cosmic mystery.

The 21 GB Reddit post will eventually fade from memory, but the conditions that created it remain. Keeping Windows updated, auditing installed software that touches the file system, and learning to use the clean boot and Process Explorer are the best insurance against a shell that suddenly turns your PC into a paperweight. A disciplined diagnostic approach—monitor, isolate, remove—beats a frantic restart every time.