Visit Website →
← Back to blog

Explorer.exe High CPU: Find the Real Cause and Fix It

October 25, 2026
Explorer.exe High CPU: Find the Real Cause and Fix It

When explorer.exe sits at 20 to 30% CPU with no folder open, Windows Explorer is rarely the real problem. It runs your taskbar, Start menu, desktop and File Explorer windows, and it loads add-ons from other software. Most of the time one of those add-ons, a network drive that no longer answers, or a stuck thumbnail job is what keeps it busy. The fix is to find which one, then change only that.

This guide goes from the 30-second fixes to the methodical ones. Each step says what it tests, so you are not guessing. Where a change touches settings, it says how to reverse it.

Tempered
Find the Cause Before You Change
Tempered identifies real constraints on Windows PCs and explains specific, user-approved changes, with an undo path for each adjustment.
Explore Tempered

TL;DR

  • Restart explorer.exe from Task Manager first. If the CPU drops and stays down, you had a stuck session. If it comes back within minutes, something is feeding it work.
  • The usual culprits are third-party shell extensions (cloud sync icons, archive tools, antivirus), thumbnail generation for large media files, and unreachable mapped network drives.
  • Test one variable at a time: a clean restart, a folder you suspect, startup apps off, then a trace if it still happens.
  • Change one thing, re-measure, and keep a way back. Skip registry cleaners: they do not address any of these causes.

Table of Contents

What explorer.exe is doing when the CPU climbs

Explorer is more than the window you browse files in. It is the shell: taskbar, Start, desktop icons, notification area, context menus, previews and thumbnails. It also hosts code written by other companies. Microsoft engineers describe Explorer as essentially a container for COM components, which is why a conflict with a poorly optimized third-party handler, such as a cloud sync status icon or a custom file-type handler, can show up as Explorer's CPU use rather than the add-on's.

Shell components linked to Explorer CPU load

That is the key idea for this whole article. Task Manager blames the process that hosts the work, not the code that causes it. So a clean fix means identifying the add-on, the folder or the drive, not just killing explorer.exe again and again.

A few patterns help you guess before you test:

What you seeLikely cause
High CPU right after sign-in, settles after a few minutesStartup apps and sync clients scanning on launch
High CPU only when opening one folderThumbnails or previews for large media, or a huge file count
High CPU when idle, with no windows openA shell extension, a dead network mapping or a stuck search/indexing task
High CPU for a few seconds on right-clickA context menu extension from another program
High CPU when renaming or moving filesAn extension or antivirus hooking file operations

Step 1: Confirm it is explorer.exe and get a baseline

Before changing anything, measure.

  1. Press Ctrl+Shift+Esc to open Task Manager.
  2. On the Processes tab, find Windows Explorer and sort by CPU.
  3. Note the percentage with no File Explorer windows open, and again after a minute of doing nothing.
  4. Open the Performance tab and note overall CPU use, so you know how much of the load is Explorer's share.

Write down the numbers. On a laptop with a modern 8 to 12 thread processor, 3% from Explorer on idle is normal and 25% is not. If the whole CPU is pinned at 100% and Explorer is only a small slice, you are chasing the wrong process. Our guide to finding the CPU hog in Windows 11 covers how to read that view.

People report the same symptom in many forms: a laptop with Explorer consuming 24 to 30% from the moment of startup, or 30 to 40% on a Windows 11 laptop at idle that comes right back after ending the task. Both point to something that restarts the load, which the next steps isolate.

Step 2: Restart Windows Explorer

This is the fastest test and often a real fix after sleep, a driver update or a long uptime.

  1. In Task Manager, right-click Windows Explorer on the Processes tab.
  2. Choose Restart. Your taskbar and desktop flicker for a moment and come back.
  3. Watch the CPU column for two to three minutes.

If the number stays low, the session was stuck. If you often see this after days of uptime, a normal restart (not Fast Startup shutdown) clears more state than an Explorer restart does. Our piece on Fast Startup in Windows 11 explains why a shutdown does not always give you a clean boot.

If the CPU climbs again within minutes, restarting only hid the symptom. Continue.

Step 3: Rule out shell extensions

Shell extensions are the most common cause that a plain restart cannot fix. They are small add-ons that put icons on files, add right-click entries, or build previews. Cloud storage clients, archive tools, PDF viewers, antivirus suites and some graphics drivers all install them.

Signs of an extension problem:

  • Overlay icons (green checks, sync arrows) on files, and CPU spikes when you open folders in a synced location.
  • A long pause before the right-click menu appears.
  • Explorer CPU that rises only after you installed or updated a specific program.

How to test without hacking anything:

  1. Think back to what you installed or updated in the week the problem began.
  2. Pause or quit that program's background client (for example the tray icon of a sync tool) and watch Explorer's CPU.
  3. If the CPU drops, update the program, or look in its settings for an option to turn off overlay icons or shell integration.
  4. If you need to go deeper, a free utility that lists third-party context menu and shell handlers lets you switch them off one at a time. Disable half, test, then narrow down. Re-enable anything that was not the cause.

If the program is OneDrive, see our walkthrough of OneDrive high CPU fixes that take 5 to 10 minutes. It is worth doing before you reinstall anything.

Microsoft-side advice is consistent here: disabling the offending extension is the most effective approach for persistent cases, and clearing temporary files alone rarely helps, as the Explorer-as-COM-container discussion above notes.

Step 4: Check thumbnails and the COM Surrogate

If the CPU only jumps in a particular folder, thumbnails are a prime suspect. Windows deliberately hosts thumbnail extraction and other risky work in a separate helper called the COM Surrogate (dllhost.exe), so a bad third-party thumbnail handler takes down the helper rather than your desktop. A spike there often points to a corrupted or hard-to-read media file, such as a large AVI or RAW photo.

Try this:

  1. Open File Explorer, select View, then Show, and look at what the folder contains. Switch the view from large icons to Details.
  2. If the CPU settles, thumbnails were the load. Open Folder Options (from the three-dot menu in Windows 11), go to the View tab, and tick Always show icons, never thumbnails.
  3. If you want thumbnails back, untick it, then move the suspect files out of the folder in batches until the spike stops. The last batch holds the problem file.

The setting is a plain checkbox, so reversing it takes five seconds. It also does not delete anything.

While you are in Task Manager, glance at the dllhost.exe entry (COM Surrogate). If it is the process burning CPU while Explorer is quiet, the same advice applies, and the troubleshooting is about a file, not about Explorer.

Step 5: Look for dead network drives

This one catches many desktop PCs. A mapped drive set to Reconnect at sign-in can make Explorer keep trying to verify a share that is offline. One Super User thread describes Explorer pegged even with no windows open, and the pattern of unavailable shares and stale mount point labels in the registry is a known trigger.

  1. Open This PC and look under Network locations for drives showing a red X or that you no longer use.
  2. Right-click each and choose Disconnect.
  3. Restart Explorer and watch the CPU.

If a drive matters, note its path first (for example
as\photos) so you can map it again. Only if disconnecting does not help is it worth looking at the registry labels, and that is a point to back up first or let a tool log it. Do not edit the registry from a forum post without a restore point.

Step 6: Trim what runs at startup

If the CPU spike is highest in the first few minutes after sign-in, the load is probably many apps starting together, with Explorer in the middle. Task Manager's Startup apps page rates each program. According to Microsoft's startup guidance, a High impact app uses over 1 second of CPU time or 3 MB of disk at startup, and a Medium impact app falls between 300 ms and 1 second of CPU or 292 KB to 3 MB of disk.

To review them:

  1. Open Settings, then Apps, then Startup. Or use the Startup apps tab in Task Manager.
  2. Sort by impact and look at the High items first.
  3. Switch off anything you do not need within the first minute: updaters, chat clients, game launchers, vendor helper apps.
  4. Restart and measure again.

Switching off a startup entry does not uninstall it, and you can flip it back on the same page. We wrote a longer walkthrough on startup impact fixes you can undo, and if you would rather keep an app but not have it fight for resources at sign-in, delaying startup apps on Windows 11 takes about a minute.

Step 7: Check for other processes that look like Explorer's fault

Sometimes Explorer is busy because another process makes it wait. Two neighbors are worth a look in Task Manager:

If the desktop itself feels slow rather than Explorer's windows, DWM.exe GPU spikes are a separate check.

Step 8: Trace it when nothing above fits

If the spike survives all of the above, stop guessing and capture evidence. Microsoft's high CPU troubleshooting guidance recommends a Performance Monitor log at a 1 to 5 second interval, along with the Sysinternals ProcDump tool to capture memory dumps during the spike. That page is written for Windows Server, but the method of logging during the event and then reading thread stacks applies on a desktop too.

A lighter version for a home PC:

  1. Download Sysinternals Process Explorer and run it as an administrator.
  2. Right-click explorer.exe, choose Properties, then the Threads tab.
  3. Sort by CPU and select the busiest thread. The stack shows which module it is running. A DLL that does not belong to Microsoft is your suspect.
  4. For a file or registry key that is being hit over and over, Process Monitor shows it. Microsoft's Defrag Tools episode on debugging demonstrates using Process Monitor to learn why a program is getting an access error, which is the same technique.

Once a DLL name shows up, search for which program installed it, then update, reconfigure or remove that program. One user who hit 100% CPU on renaming a file used Process Monitor to see what the machine was doing during the rename, which is the right instinct.

Our perspective: measure first, change second

We build Tempered for people in exactly this spot: a PC that feels slow, a process name in Task Manager and a dozen forum posts that each say something different. What we see is that high Explorer CPU is a good example of a symptom that gets a bad cure. The common advice is to run a cleaner, wipe temp files, and clean the registry. None of that reaches a misbehaving shell extension, a dead share or a thumbnail job.

So our approach is to name the constraint with live numbers (CPU, RAM, GPU, disk, uptime), explain in plain language what we think is going on, and propose a specific change you approve. We do not clean the registry or invent problems to look busy. Every change is logged and has a one-click undo, because a fix you cannot reverse is a new risk. If a step in this article does not help, you should be able to put the setting back exactly as it was, and that holds whether you do it by hand or with our tool.

The habit to take away is simple: change one thing, re-measure, and keep notes. That habit finds the cause faster than any single trick.

— Ian

Let Tempered do the measuring

If you would rather not work through Task Manager yourself, Tempered is an AI-assisted diagnostic and optimization tool for Windows 10 and 11. It reads live hardware metrics, points to what is holding the PC back, manages background processes and startup entries, and applies safe tweaks only after you approve them, each with an explanation and an Undo. It does not need an AI API key. You can start on the free plan, and paid plans are listed on the pricing page: Torque from $5.99 per month and Torque Max from $12.99 per month.

Quick prevention checklist

  • Restart the PC fully every few days rather than relying on sleep.
  • After installing a sync client, archive tool or antivirus, watch Explorer's CPU for a day.
  • Remove mapped drives you no longer use.
  • Keep camera RAW and large video folders out of thumbnail view, or keep thumbnails off for them.
  • Review Startup apps every month or two.

FAQ

Is it safe to end explorer.exe in Task Manager?

Yes. Use Restart on Windows Explorer in Task Manager, and the taskbar and desktop reload in a second or two. Save your work in File Explorer windows first, since they close. It does not delete files or change settings.

Why is Windows Explorer using CPU when I have nothing open?

The shell still runs your taskbar, desktop and notification area, and it hosts third-party extensions. Idle load usually comes from one of those add-ons, an unreachable network drive or a startup app still scanning. Work through the shell extension and network drive steps above to find which.

Will a registry cleaner or temp file cleanup fix it?

Usually not. Persistent Explorer CPU is typically caused by an extension or a specific file or drive, and clearing temporary files does not remove those. Identify the cause first, then change that one setting.

Does high explorer.exe CPU mean I have malware?

Not usually, but it can. Check that the file sits in C:\Windows and run a full scan with Windows Security. If Explorer is high only in one folder or after one install, an add-on or file is the far likelier cause.

Sources