Your laptop's crawling. Task Manager shows explorer.exe eating 2GB of RAM. Nothing obvious's using it. Before you hand it over to a repair shop, here's what's actually happening and how to fix it yourself.
TL;DR
Windows Explorer high memory leaks are usually caused by shell extensions (antivirus, OneDrive, GPU utilities). Boot Safe Mode to confirm, then use ShellExView to disable suspect extensions one at a time. If that doesn't work, clear caches, update Windows, and optimise virtual memory settings.
Key Takeaways
- Explorer memory leaks are almost never Explorer's fault - it's usually add-in software
- Safe Mode testing takes 15 minutes and tells you immediately if third-party extensions are guilty
- Most fixes don't require specialist tools beyond Windows' built-in utilities
- If basic fixes fail, a PC optimiser tool can automate the heavy lifting of extension management and cache clearing
- True memory leaks show continuous growth; normal caching plateaus and releases when idle
At a Glance
- Difficulty: Intermediate
- Time Required: 45-90 minutes
- Success Rate: 70-80% with shell extension fixes
What Causes Windows Explorer High Memory Usage?
Explorer running at 2GB isn't a bug you've stumbled on - it's a pattern, and it has four main causes. The first and most common is third-party software that hooks into Explorer itself. Your antivirus scans files as you browse. OneDrive shows sync status. NVIDIA's GPU utilities add context menus. All of these run inside explorer.exe, and many of them either leak memory or hold onto caches that should've been released. One bad integration and you're bleeding RAM.
The second culprit is Windows Search indexing gone wrong. During file searches across multiple drives or mapped network folders, Explorer sometimes duplicates index paths and churns through RAM redundantly. Microsoft fixed this in Windows 11 Insider Preview Build 26220.7523, but older builds are affected. If you've never updated past mid-2024, you might be running the broken version.
Third is thumbnail caching. Every time you open a folder with images or documents, Explorer generates previews and stores them. These temporary files should be cleaned up, but sometimes they accumulate and the memory working set grows without releasing it. On systems with heavy file operations - large copy jobs, lots of folder browsing - this adds up fast.
Fourth is virtual memory misconfiguration. Systems with only 8GB of RAM often have a pagefile that's too small or disabled entirely. When physical RAM fills up, Windows struggles to offload memory to disk, and Explorer appears to leak when it's actually just thrashing. This is less common than the others but brutal when it happens.
Windows Explorer High Memory: Quick Fix
Boot Safe Mode and Identify the Cause Easy
- Press Win+R
Typemsconfigand press Enter. - Go to the Boot tab
Check the 'Safe Boot' box. Leave it set to 'Minimal'. Click OK. - Restart your system
Windows will boot into Safe Mode. This disables third-party shell extensions but keeps Windows' core functions running. - Open Task Manager
Press Ctrl+Shift+Esc. Find explorer.exe in the process list. Note its memory usage right away. - Open a few folders and search
Spend 15 minutes browsing files and running a search across your drive. Watch explorer.exe memory. If it stays stable below 500MB, third-party extensions are definitely the problem. - Boot normally
Open msconfig again, uncheck Safe Boot, click OK, and restart. Memory will likely jump again once you're back to normal mode with all extensions loaded.
Solution 2: Disable Problematic Shell Extensions
This is the fix that works most of the time. You'll use a free tool called ShellExView to list every extension loaded into Explorer, then disable them one by one until memory stabilises. It sounds tedious, but it's methodical and reliable.
Use ShellExView to Find and Disable Memory-Leaking Extensions Intermediate
- Download ShellExView
Go to NirSoft's official ShellExView page. Download the 64-bit version (or 32-bit if you're on a 32-bit system). Extract the.zip file. - Run as administrator
Right-click ShellExView.exe and select 'Run as administrator'. A window opens showing all your shell extensions with company names, descriptions, and status. - Create a backup
Click Options > Export to save your current configuration as a.reg file. Store this somewhere safe. If something breaks, you'll import it back. - Sort by Company
Click the 'Company' column header. This groups Microsoft extensions at the top and third-party ones below. Focus on antivirus vendors (Norton, McAfee, Kaspersky, Windows Defender context handlers), cloud storage (OneDrive, Dropbox, Google Drive), GPU makers (NVIDIA, AMD), and media codecs. - Disable one extension at a time
Select a suspect extension (e.g., one from your antivirus). Right-click and choose 'Disable Selected Items'. ShellExView will ask for confirmation. Click OK. - Restart Explorer
Open Task Manager (Ctrl+Shift+Esc). Find explorer.exe. Right-click it and select 'Restart explorer.exe'. You'll see the desktop flicker as Explorer restarts. - Monitor memory for 15 minutes
Open a few large folders. Run a file search. Watch explorer.exe in Task Manager. If memory stays below 600MB and doesn't climb, you've found the culprit. If it still shoots up to 1.5GB+, re-enable that extension and try the next one. - Once you've found the culprit
Leave it disabled. You've effectively fixed the leak. If you need the functionality that extension provided (e.g., OneDrive sync), contact the vendor or check their website for an updated version that doesn't leak.
Solution 3: Clear Caches and Update Windows
If disabling extensions doesn't fully solve it, or if you're uncomfortable messing with extensions, the next step is to clean out accumulated caches and apply the latest Windows updates. Microsoft has patched several Explorer memory issues in recent builds, and clearing temporary files reduces the load Explorer carries.
Clean Caches and Apply System Updates Easy
- Run Disk Cleanup
Press Win+R, typecleanmgr, and press Enter. Select your C: drive (or system drive). Tick 'Thumbnails', 'Temporary Internet Files', and 'Temporary files'. Click 'Clean up system files' to remove Windows update cache as well. Let it finish. - Delete icon cache manually
Open File Explorer. Press Ctrl+H to show hidden files. Navigate toC:\Users\[YourUsername]\AppData\Local. Look forIconCache.db. Delete it (you may see a warning that it's in use - that's fine, Windows will recreate it on restart). Restart your computer. - Update Windows
Open Settings. Go to 'System' > 'Windows Update' > 'Check for updates'. Install all available updates, especially cumulative updates. Builds 26220.7523 and later include fixes for duplicate indexing in searches. Restart when prompted. This may take 20-30 minutes. - Run system file checks
Open Command Prompt as administrator. RunDISM /Online /Cleanup-Image /RestoreHealth. This downloads and installs system file repairs (takes 10-20 minutes). Then runsfc /scannowto check and repair corrupted system files (takes 5-15 minutes). Both may require a restart. - Monitor after restart
Restart your system. Open Task Manager. Run typical file operations (browse folders, search, copy files) for at least 2 hours. Watch explorer.exe memory. If it plateaus around 400-600MB and doesn't climb further, the fix worked.
Solution 4: Advanced Diagnostics and Virtual Memory Optimisation
If you're still seeing 2GB+ memory usage after trying the above, it's time for deeper investigation. Process Explorer, a tool from Microsoft's Sysinternals suite, shows you exactly which DLLs and components are holding memory. You'll also adjust your pagefile to give Windows room to offload memory under pressure.
Diagnose with Process Explorer and Tune Virtual Memory Advanced
- Download and run Process Explorer
Go to Microsoft Sysinternals Process Explorer. Download the.zip. Extract and run as administrator. - Configure columns for memory tracking
Click View > Select Columns. Tick 'Private Bytes', 'Working Set', 'Handles', and 'Threads'. These columns show which processes actually own memory versus just accessing it. Private Bytes is what matters - that's real, non-shareable memory tied to explorer.exe. - Locate and monitor explorer.exe
Find explorer.exe in the process list. Note its Private Bytes value. Open some large folders (with lots of images) and run a search across multiple drives. Watch Private Bytes. If it climbs from 200MB to 2GB and keeps climbing even when you're idle, it's a true leak. - Check loaded DLLs
Right-click explorer.exe and select 'View DLLs'. Look for DLLs from vendors you don't recognise (not Microsoft, not Windows). These often indicate shell extensions that might be problematic. Antivirus DLLs, cloud storage libraries, and GPU utilities show up here. - Optimise virtual memory settings
If physical RAM is constrained (8-12GB), your pagefile may be too small. Open Settings > System > About > Advanced system settings (or right-click This PC > Properties > Advanced system settings). Click 'Performance' > Settings > 'Advanced' tab. Under 'Virtual Memory', click 'Change'. Uncheck 'Automatically manage'. Set custom sizes: Initial = 1.5x your RAM (e.g., 12GB for 8GB RAM), Maximum = 3x RAM (e.g., 24GB). Click 'Set', then OK. Restart. - Verify adequate disk space
Make sure you have at least 20GB free on your system drive. The pagefile needs room to grow. If you're below 10GB free, that's your real problem - you're out of virtual memory. - Test and report if still broken
Restart. Run Task Manager. Monitor explorer.exe for 2-3 hours during normal work. If memory still climbs to 2GB+ and you see continuous growth, create a memory dump: right-click explorer.exe in Process Explorer, select 'Create Dump' > 'Create Full Dump'. Open Windows Feedback Hub (Win+F), submit a report under 'Files, folders and storage', attach the dump, and describe the issue. Microsoft can analyse it for engineering teams.
Preventing Windows Explorer High Memory Leaks
Once you've fixed the leak, keep it from coming back. The main prevention strategy is controlling what software integrates with Explorer in the first place.
Audit extensions monthly. Open ShellExView quarterly and check for any new third-party extensions you don't recognise. If an update installed something sketchy, disable it straightaway. Keep a habit of it - takes 5 minutes and saves headaches.
Clean caches proactively. Run Disk Cleanup once a week. Tick Thumbnails and Temporary files. This keeps Explorer's working set from bloating as it accumulates preview data. If you do heavy file work (managing thousands of photos, large copy jobs), do this more often.
Stay current with Windows updates. Updates often include memory fixes. Install them as they're released, especially cumulative updates on Patch Tuesday. Builds 26220.7523 and later have the indexing fixes.
Monitor baseline memory. Use Process Explorer to establish what normal explorer.exe memory looks like on your system. On most machines, 300-500MB during light use is normal. If you see it consistently above 700MB, investigate immediately rather than waiting for it to hit 2GB.
Limit simultaneous searches. If you search across five mapped network drives at once, you're stressing Explorer unnecessarily. Search one location at a time. This is especially important on older systems with 8GB RAM.
Consider upgrading RAM if you're on 8GB. 8GB is Microsoft's technical minimum for Windows 11, but it's marginal. If you regularly work with large directories or network shares, 16GB removes most memory pressure and makes Explorer leaks far less painful. It's a £40-50 investment that buys peace of mind.
Windows Explorer High Memory: Summary
Windows Explorer high memory usage is annoying but usually fixable. Start with Safe Mode testing - 15 minutes tells you if it's third-party extensions. If it is, use ShellExView to disable them one by one. That solves it 70-80% of the time. If not, clear caches, update Windows, and check your virtual memory settings. Only if all three have failed should you dive into Process Explorer dumps and reporting to Microsoft. The key is testing systematically, one change at a time, so you know exactly what fixed it. And once you've fixed it, stay on top of updates and extension audits so it doesn't happen again.