File Explorer is the shell you interact with all day — the taskbar, the desktop, every folder window. When explorer.exe starts consuming 20 to 40 percent CPU continuously, everything feels wrong: folder windows hesitate, the taskbar lags, right-click menus take forever to appear, and your laptop runs warm while doing nothing. Because Explorer is so central, its high CPU usage is more disruptive than most background processes.

The tricky part is that explorer.exe is a host for many things beyond file browsing: thumbnail generation, shell extensions from third-party apps, cloud storage status overlays, search integration, and preview handlers. Any one of these plugins can go rogue and drag the whole process down with it. The diagnostic approach is therefore about isolation — figure out which subsystem is misbehaving, then fix or disable that specific thing. Blindly reinstalling Windows is overkill; targeted fixes work.

This guide walks through the isolation process in the order that solves most cases fastest, starting with the 30-second restart test and ending with the deeper repairs.

Why this happens

  • Corrupted thumbnail cache: Damaged thumbnail data forces Explorer to regenerate previews constantly, burning CPU every time you open a folder.
  • Misbehaving shell extensions: Third-party right-click menu entries (from archivers, cloud apps, antivirus) can hang or loop inside the Explorer process.
  • Cloud storage overlays: OneDrive, Dropbox, and Google Drive overlay icons require constant status checks that keep Explorer busy during syncing.
  • Corrupted Quick Access cache: The Quick Access / Home view caches frequent folders; corruption here causes repeated failed loads.
  • Damaged media files: A corrupted video or image that Explorer tries to thumbnail can trap the process in a retry loop.
  • Preview pane on broken files: The preview pane attempts to render whatever is selected — a damaged file means a stuck renderer.
  • Windows Search integration: Explorer’s search box ties into the indexer; a corrupted index makes Explorer-side search burn CPU.
  • Too many desktop icons or a huge folder: Explorer re-renders the desktop and large folders on every refresh; extreme cases add constant load.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Restart File Explorer

The 30-second test. If a transient glitch has Explorer stuck, this clears it.

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Find Windows Explorer under Processes.
  3. Right-click it and choose Restart.
  4. Your taskbar will briefly disappear and return. Check CPU usage after 2-3 minutes.

If usage drops and stays low, you’re done. If it climbs back up, something is persistently triggering it — continue.

Fix 2: Clear the thumbnail cache

Corrupted thumbnails are the most common persistent cause. Clearing the cache forces a clean rebuild.

  1. Open Disk Cleanup (search for it in the Start menu).
  2. Select your system drive and click OK.
  3. Check Thumbnails in the list (uncheck everything else unless you want a broader cleanup).
  4. Click OK, then Delete Files.
  5. Open a few folders to let thumbnails rebuild, then check CPU usage.

If the problem returns after rebuilding, a specific corrupted media file is likely re-poisoning the cache — see Fix 5.

Fix 3: Disable suspicious shell extensions

Third-party context menu entries are a notorious cause. The free tool ShellExView (from NirSoft) lets you disable them safely.

  1. Download ShellExView from NirSoft’s official site.
  2. Run it and sort by Type — look at Context Menu extensions.
  3. Select non-Microsoft extensions (pink background = non-Microsoft), right-click, and choose Disable Selected Items.
  4. Restart Explorer (Task Manager > Windows Explorer > Restart) and check CPU.
  5. Re-enable extensions in small groups to identify the culprit, then leave that one disabled or update the parent app.

Fix 4: Clear File Explorer history and reset Quick Access

A corrupted Quick Access cache causes repeated failed loads every time Explorer opens.

  1. Open File Explorer > three dots menu > Options.
  2. Under the General tab, click Clear next to “Clear File Explorer history.”
  3. Change Open File Explorer to from “Home” to This PC — this skips the problematic Quick Access view entirely.
  4. Uncheck Show recently used files and Show frequently used folders in Privacy.
  5. Click OK and restart Explorer.

Fix 5: Find and remove corrupted media files

If high CPU only happens in folders with videos or photos, a damaged file is the likely trigger.

  1. Note which folder triggers the spike.
  2. In that folder, switch to Details view (no thumbnails) and turn off the Preview pane (View menu).
  3. Play or open files one by one — the one that hangs, errors, or won’t generate a thumbnail is your suspect.
  4. Move the suspect file out of the folder (don’t delete immediately in case it’s actually fine).
  5. Check CPU usage with the file removed.

Fix 6: Tame cloud storage overlays

During heavy syncing, OneDrive/Dropbox status overlays keep Explorer constantly updating icons.

  1. Check whether the spike correlates with active syncing (cloud icon spinning in the taskbar).
  2. Pause syncing temporarily to confirm: click the cloud icon > gear > Pause syncing.
  3. For a permanent reduction, use Files On-Demand so fewer files need status tracking — see our guide on limiting OneDrive sync .
  4. In Dropbox/Google Drive, disable Finder/Explorer overlay icons in their preferences if the option exists.

Fix 7: Repair system files and check the search index

For the stubborn cases: corrupted system files or a broken search index feeding Explorer-side search.

  1. Open an elevated Command Prompt and run sfc /scannow, then restart.
  2. If issues persist, run DISM /Online /Cleanup-Image /RestoreHealth and restart.
  3. Rebuild the search index: Control Panel > Indexing Options > Advanced > Rebuild.
  4. As a diagnostic, try disabling Windows Search temporarily (services.msc > Windows Search > Stop) to confirm the index is involved.

If your CPU issues extend beyond Explorer, our technician’s high-CPU checklist covers the full landscape. Microsoft’s Windows support page has additional File Explorer troubleshooting for your build.

Closing

File Explorer high CPU is almost always a plugin or cache problem, not a Windows problem: corrupted thumbnails, a bad shell extension, cloud overlays, or a damaged media file. Isolate with the restart test, clear the caches, disable the extensions — and in most cases explorer.exe goes back to idling at near-zero where it belongs.

Frequently asked questions

Why does File Explorer use so much CPU?
The usual suspects are corrupted thumbnail caches forcing constant regeneration, misbehaving third-party shell extensions (right-click menu add-ons), cloud storage overlays like OneDrive or Dropbox constantly syncing status icons, a damaged Quick Access cache, or Explorer trying to preview a corrupted media file. Any of these can keep explorer.exe busy indefinitely.
Is it safe to restart File Explorer?
Yes, completely safe. Restarting explorer.exe only reloads the Windows shell — your taskbar and open Explorer windows briefly disappear and come back. Open applications, unsaved work, and background processes are unaffected. It’s the standard first troubleshooting step for any Explorer weirdness.
Can a single corrupted file cause high CPU?
Yes. If Explorer tries to generate a thumbnail or preview for a damaged video or image file, it can get stuck retrying. This commonly happens when you open a folder full of media. Deleting or moving the corrupted file — or disabling thumbnails — breaks the loop immediately.
Do I need to reinstall Windows to fix explorer.exe?
Almost never. File Explorer high CPU is fixable in the vast majority of cases with the steps below — clearing caches, disabling bad shell extensions, and fixing cloud overlays. Reinstallation is a last resort that very few people actually need for this problem.