Why Is Explorer Using So Much CPU? | Stop CPU Spikes

When File Explorer starts chewing through CPU, the whole PC can feel off: clicks land late, fans ramp up, and switching windows turns sluggish. The annoying part is that “Explorer” isn’t just a folder window. It also helps run the desktop, taskbar, parts of Start, previews, and a bunch of plug-ins that other apps hook into. So the spike you see may be Explorer doing work for something else.

This article is built to help you find the real trigger, not just hide it. You’ll start with fast, low-risk checks that give clear clues. Then you’ll isolate the cause with a repeatable routine. By the end, you’ll know whether you’re dealing with thumbnails, Quick Access history, Search indexing, a cloud sync hook, a drive problem, or a misbehaving shell add-on.

Start With A 2-Minute Reality Check

Open Task Manager and sort by CPU. If “Windows Explorer” is near the top, right-click it and choose Restart. If the spike drops and stays down, it was likely a temporary hang from a folder view, preview generation, or an Explorer hiccup after sleep or a device reconnect.

If the spike drops for a moment and comes back the instant you open a specific folder, that’s great news. You already have a repeatable trigger. Keep that folder name in mind, because being able to reproduce the spike on purpose makes every next step faster.

Spot The Pattern: Constant Load Vs. Short Bursts

A steady 15–30% CPU that doesn’t settle often points to repeated background work: Search indexing pressure, a shell extension loop, or a cloud client integration constantly checking status. A burst that hits 60–100% for a few seconds when you enter a folder often points to thumbnails, metadata reads, or previews.

Glance At Disk And Network

Switch to Task Manager’s Performance tab and watch Disk and Ethernet/Wi-Fi during the spike. If CPU is high and Disk stays busy, Explorer may be reading lots of files to build thumbnails or fetch file properties. If Network activity jumps, a mapped drive, NAS, or a cloud folder may be involved.

Why Explorer Uses So Much CPU During Folder Browsing

Explorer CPU spikes tend to come from a small set of repeat offenders. The fastest path is matching what you see to a likely cause, then testing one change that should shift the behavior.

Thumbnails And Preview Features

Folders full of photos, videos, large PDFs, RAW images, or project files can push Explorer hard. It generates thumbnails, reads metadata, and may load a preview handler to show a preview pane. If one file is corrupted, Explorer can get stuck retrying work in a loop.

• Test: In the problem folder, switch the view to Details and turn off the Preview pane.
• Signal: If CPU drops right away, the trigger is tied to thumbnails, previews, or property reads in that folder.

Also check the Details pane (the pane that shows file info). In some setups, it can also kick off metadata reads. Turning it off for a test is a clean way to confirm whether file properties are the pressure point.

Quick Access And Recent Items Getting Stuck

Quick Access is handy until a pinned path becomes unreachable. A disconnected external drive, a stale network location, or a moved folder can cause repeated retries that show up as Explorer CPU load.

• Test: Open Explorer and type C:\ into the address bar. If that’s smooth, then clicking Home/Quick Access triggers the spike, pinned or recent items are a strong suspect.
• Fix direction: Clear File Explorer history and unpin locations that point to offline paths, then add pins back one at a time.

Windows Search Indexing Pressure

Explorer leans on Windows Search in ways people don’t always notice: sorting, property lookups, and some “instant” results in certain views. When the index is rebuilding, stuck, or dealing with a large batch of file changes, you can see CPU churn paired with heavy disk activity.

If Search seems involved, use Microsoft’s steps for Search troubleshooting and the built-in troubleshooter: Fix problems in Windows Search.

Third-Party Shell Add-Ons

Right-click menus, archive tools, cloud clients, developer tools, media taggers, and some security products add shell components. Explorer loads them in-process. If one behaves badly, Explorer takes the hit.

A strong clue is a spike that happens when you right-click files, hover over the context menu, or load icon overlays (sync checkmarks, lock icons, status badges). Updating that app can fix it. If updates don’t change anything, removing the app for a test often tells you the truth in one reboot.

Cloud Sync Folders And Placeholder Files

Cloud folders can be heavy because Explorer has to resolve status icons, file availability, and sometimes fetch metadata. If the spike happens only inside a synced folder, test a local folder with a similar number of files. If local is smooth and the synced folder spikes, the cloud integration is involved.

Try pausing sync for five minutes and re-testing the same folder. If CPU stays low during the pause, you’ve narrowed the source to that sync layer rather than Explorer itself.

Network Drives, NAS Shares, And Slow Storage

Explorer does constant directory enumeration. If a share responds slowly, CPU can climb as Explorer retries and updates the UI. Similar symptoms can show up on a failing HDD, a flaky USB drive, or a storage device with file system errors.

• Disconnect mapped drives you don’t need and re-test.
• Open Explorer straight to a known local folder instead of Home.
• If the spike happens only on one drive letter, focus on that device.

System File Corruption Or A Bad Interaction After An Update

If the spike started right after a Windows update, a crash, or an unexpected power cut, system files can be part of the story. When Explorer misbehaves across every folder, not just one location, checking Windows image and system file integrity is a reasonable step.

Microsoft documents the supported DISM + SFC repair steps here: Use the System File Checker tool.

Use This Isolation Routine To Get A Clear Answer

If you want a solid diagnosis instead of guesswork, isolate the trigger by changing one variable at a time. The goal is simple: find the one action that flips CPU from calm to chaos.

Step 1: Make The Spike Repeatable

Close all Explorer windows. Restart Explorer from Task Manager. Then open the exact folder or perform the exact action that normally triggers the spike. If the spike happens only on right-click, reproduce it that way. If it happens only in one directory, go straight there. A repeatable trigger is your shortcut to certainty.

Step 2: Reduce Explorer’s Work In That Folder

In the problem folder, switch to Details view, turn off the Preview pane, and turn off the Details pane. Then sort by Name. Sorting by metadata like Date taken or Length can trigger deeper reads across many files, especially on network shares or large media directories.

If these changes calm CPU immediately, the cause is not “Explorer is broken.” It’s Explorer doing too much work for thumbnails, previews, or property reads in that folder.

Step 3: Test With A Clean User Profile

Create a new local Windows user account and sign into it. Don’t install anything. Open the same folders and reproduce the same actions. If Explorer stays calm on the new account, the cause is likely inside your profile: pinned Quick Access items, history state, custom folder views, or user-level shell add-ons.

Step 4: Test Without Non-Microsoft Startup Apps

Disable non-Microsoft startup apps, reboot, and re-test the trigger. If the spike disappears, add those apps back in small batches until the spike returns. The batch that brings it back contains the culprit. This approach is slower than random toggling, yet it gives a clean answer.

Fixes That Solve The Most Explorer CPU Spikes

Work through these in order. Each step is chosen because it either fixes the issue outright or gives a strong clue about where the issue lives.

Restart Explorer The Right Way

Restarting Explorer from Task Manager is cleaner than rebooting the entire PC and often resolves a hang after sleep, a device reconnect, or a shell glitch. If the spike is a one-time event, this ends it.

Clear Thumbnail Cache When Media Folders Trigger The Spike

If CPU spikes only in photo/video folders, thumbnail cache issues are common. Clear thumbnail caches, then test the same folder again. You’re watching for a behavior change: does the folder open smoothly, or does CPU still pin the moment you enter?

If clearing caches helps only briefly, suspect one file. Move half the files out, test, then narrow again. This “split the folder” method finds the one corrupt file that keeps triggering repeated work.

Reset Quick Access History When Home View Is The Trigger

If Explorer spikes before you even reach a folder, and Home/Quick Access is involved, clear File Explorer history and remove pins that point to offline locations. Then reopen Explorer and watch CPU. If it stays low, add pins back slowly so you can catch the one that breaks it.

Disable Preview Features When A Handler Is Misbehaving

Preview handlers can load for PDFs, Office files, and many media types. If turning off the Preview pane stops the spike, keep it off for a day and note whether the system stays stable. You can also remove custom columns in Details view for that folder type, since certain columns trigger extra metadata reads.

Trim File Explorer Integrations That Hook Into Right-Click

If CPU spikes when you right-click files, context menu extensions are the front-runner. Update the app that added the menu entry. If that doesn’t change anything, remove that app for a test. If Explorer becomes smooth, you’ve got your answer.

Check For Search Index Pressure

If you see steady CPU paired with heavy disk activity and searches feel slow, Search indexing may be rebuilding. Let it finish if you recently copied a large batch of files. If it seems stuck for hours, use the Search troubleshooting link above and review your indexing settings.

Deeper Fixes When The Spike Keeps Returning

If the spike keeps coming back, you need steps that separate “folder content problem” from “system-wide issue.” These moves take longer, yet they give strong signal.

Fix Folder Template Misclassification

Windows applies templates like Pictures or Music to folders based on what it thinks is inside. A large mixed folder can get classified as Pictures and trigger thumbnail-heavy behavior even when you don’t want it. Set that folder’s template to General items and re-test. If CPU drops, the template choice was driving extra work.

Test With “Launch Folder Windows In A Separate Process”

There’s an option in Folder Options that launches folder windows in a separate process. Turning it on can help you spot when a folder window is the trigger, while the shell stays stable. It won’t fix a bad add-on on its own, yet it can reduce the blast radius and make testing clearer.

Check The Drive And File System

If Explorer spikes only when browsing one drive, focus there. Storage errors can force retries and slow reads, which makes Explorer look like it’s “using CPU,” even when it’s really stuck waiting on I/O. Run a disk check and watch if the same drive keeps causing spikes during folder enumeration.

Look For Unwanted Programs That Hook Into Explorer

If Explorer spikes in random places and right-click menus feel slow, there may be an unwanted program injecting shell components or overlays. Run a full scan with your security tool, remove anything you don’t recognize, then re-test the same action that used to spike CPU.

Repair System Files When Explorer Feels Broken Everywhere

If Explorer spikes on almost every folder and you also see odd UI behavior, run DISM + SFC using Microsoft’s documented steps linked earlier. When the repair finishes, reboot and test the same folder that used to trigger the spike. If CPU behavior changes after the repair, system integrity was part of the cause.

What “Normal” Looks Like And When It’s A Real Problem

Some Explorer CPU is normal. Opening a huge folder, generating thumbnails for the first time, or indexing a large batch of new files can spike CPU for a short stretch. What’s not normal is a spike that never settles, or a spike that happens on every folder no matter what you open.

• If Explorer pins 50–100% CPU for minutes, treat it as a fault to isolate.
• If the spike happens only in one folder type, focus on thumbnails, previews, and file integrity inside that folder.
• If the spike happens only on right-click, focus on context menu extensions.

Last-Resort Options That Keep Personal Files Intact

If nothing has helped, you still have data-safe resets before you even think about wiping Windows.

Move To A Fresh User Profile

If a brand-new user account stays smooth, migrating to a fresh profile can remove years of accumulated history state, pins, and shell hooks. Copy your personal files over, then reinstall apps slowly so you can catch the one that makes Explorer spike again.

Use System Restore Or An In-Place Repair Install

System Restore can roll system settings back to a prior point while leaving your personal files alone. An in-place repair install can reinstall Windows components while keeping files and many settings. These are heavier steps, so save them for cases where Explorer misbehaves across the whole system and you’ve already tested add-ons, folders, and Search.

A Quick Checklist For The Next Time It Happens

If you see the spike again later, run this quick checklist and you’ll get to a solid answer fast:

1. Restart Explorer, then reproduce the spike.
2. Test the same action in a local folder and a synced or network folder.
3. Turn off Preview and Details panes, switch to Details view, sort by Name.
4. Clear Quick Access history if Home view triggers the spike.
5. Disable non-Microsoft startup apps to isolate shell add-ons.

Once you know which action triggers the load, the fix stops feeling random. Explorer is often just the place where the problem shows up. The real cause is usually a folder feature, a handler, or an add-on doing too much work inside the Explorer process.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback