File Explorer should idle at 0% CPU. So when explorer.exe is sitting at 15–30% in Task Manager — fans humming, battery draining, the whole shell feeling laggy — something is wrong inside the process that draws your desktop, taskbar, and every folder window. Right-clicks hesitate, window animations stutter, and the laptop runs warm doing apparently nothing.

On HP laptops, two culprits dominate. The first is HP’s own preinstalled software: HP Support Assistant, HP Wolf Security components, and trial utilities that register shell extensions inside explorer.exe. The second is the classic Windows set: a broken thumbnail handler that re-renders previews in a loop, a corrupted icon cache, or a cloud-sync overlay (OneDrive, Dropbox) that re-checks every file’s status continuously.

Because explorer.exe also renders the taskbar and desktop, you cannot just kill it and walk away — but you can restart it, strip its extensions, and fix its caches. The steps below isolate the cause without destabilizing the shell. For the slowness variant of this problem, see slow File Explorer on Lenovo .

Why this happens

  • Broken thumbnail or preview handlers: a damaged codec or preview handler re-renders previews in an infinite loop.
  • Corrupted icon cache: Windows rebuilds icons constantly when the cache database is damaged.
  • Cloud storage overlay icons: OneDrive/Dropbox status checks on thousands of files keep the process busy.
  • HP shell extensions: HP utilities register context-menu and overlay handlers that misbehave inside explorer.exe.
  • Corrupted Quick Access data: damaged jump-list or recent-items data makes Explorer re-parse on every action.
  • Desktop slideshow or animated background: rapid background changes force the shell to recompose continuously.
  • Malware masquerading as explorer: fake explorer.exe processes running from non-system folders burn CPU while spying.

How to fix it

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

Fix 1: Verify it is the real explorer.exe

Before troubleshooting, rule out malware impersonating the shell. Also check the process command line in Task Manager for suspicious flags.

  1. In Task Manager’s Details tab, right-click explorer.exe and choose Open file location.
  2. Confirm it opens C:\Windows — the genuine shell lives only there.
  3. If it opens anywhere else, run a Microsoft Defender Offline scan immediately.

Fix 2: Restart Explorer cleanly

A stuck shell loop often clears with a restart, which is safe and takes seconds. A restart that holds for hours before the spike returns points to a slow-building trigger like a cache.

  1. Open Task Manager, find Windows Explorer under Processes, right-click, and choose Restart.
  2. Watch the CPU column for two minutes; if it settles to 0–1%, a transient loop was the cause.
  3. If it climbs again, continue — the loop has a persistent trigger.

Fix 3: Clear thumbnail and icon caches

Corrupted caches are the top legitimate cause of explorer.exe CPU spikes. Expect one slow folder visit while caches rebuild, then fast ones after.

  1. Open Disk Cleanup, select the system drive, tick Thumbnails, and click OK.
  2. Then delete the icon cache: in File Explorer go to %localappdata%\Microsoft\Windows\Explorer and delete iconcache*.db.
  3. Restart Explorer from Task Manager and let caches rebuild once.

Fix 4: Disable cloud overlay icons temporarily

If CPU spikes in synced folders, the overlay handlers are the amplifier. Selective sync is the permanent answer; pausing is just the diagnostic.

  1. Pause OneDrive syncing (click its taskbar icon > Pause syncing) for two hours as a test.
  2. In OneDrive settings, consider Files On-Demand so fewer files need status checks.
  3. If CPU normalizes, keep sync selective rather than syncing the entire drive.

Fix 5: Strip third-party shell extensions

A single bad context-menu handler can pin explorer.exe. Disable them systematically. Security software and cloud storage clients are the most common offenders here.

  1. Download ShellExView from NirSoft and run it as administrator.
  2. Disable non-Microsoft extensions in small batches, restarting Explorer after each.
  3. When CPU stays at zero, re-enable one by one to identify the offender, then uninstall it.

Fix 6: Remove HP utilities that hook the shell

HP-specific handlers are a prime suspect on HP hardware. HP’s own cleanup guidance is at HP support . HP Wolf Security in particular hooks deeply into the shell on business models.

  1. Open Settings > Apps > Installed apps and review HP-branded entries.
  2. Uninstall HP JumpStart, trial security software, and utilities you never use.
  3. Keep only what you actively use, restart, and re-check explorer.exe CPU at idle.

Fix 7: Scan for system corruption

If the shell itself is damaged, SFC and DISM repair it. These repairs are safe to run even if you are unsure corruption is the cause.

  1. Run sfc /scannow in an admin Command Prompt.
  2. Follow with DISM /Online /Cleanup-Image /RestoreHealth.
  3. Reboot and confirm explorer.exe idles at 0% CPU. More on these tools at Microsoft’s Windows help .

Fix 8: Turn off the Preview and Details panes

The Preview pane and Details pane force Explorer to load preview handlers for every file you select, and a buggy handler burns CPU on each selection change. Turning both panes off removes an entire class of handler bugs from the equation, and most users never miss them once they try the uncluttered view.

  1. In File Explorer, open the View menu on the ribbon.
  2. Untick Preview pane and Details pane so neither is active.
  3. Select various files and watch explorer.exe CPU in Task Manager.
  4. If CPU stays flat, a preview handler was the culprit — leave the panes off.

Closing

Explorer.exe should be the quietest process on your system. When it is not, the cause is almost always inside its plugin ecosystem — a broken thumbnail handler, a corrupted cache, an overzealous cloud overlay, or an HP utility gone rogue. Verify the process is genuine, clear the caches, strip the extensions, and the shell goes back to idling at zero. If right-clicks are slow as well as CPU-heavy, see fixing the slow right-click menu .

Frequently asked questions

Is it normal for explorer.exe to use CPU sometimes?
Yes, briefly. Opening a folder with thousands of files, generating thumbnails for the first time, or right-clicking while a context menu builds can spike explorer.exe for a few seconds. What is not normal is sustained CPU — 10% or more for minutes at a time with no folder windows open. Brief spikes are work; sustained usage is a loop.
Why does restarting Explorer fix it temporarily?
Restarting kills the wedged loop but not its trigger. If a corrupted thumbnail cache or a bad shell extension caused the loop, the fresh explorer.exe process hits the same trigger and starts looping again within minutes. Temporary relief confirms the problem lives inside the shell process; the permanent fix is removing the trigger with Fixes 3 through 6.
Can OneDrive really cause high Explorer CPU?
Yes, and it is one of the most common causes. Every file in a synced folder gets an overlay icon (synced, syncing, error), and Explorer queries the sync engine for each one. In folders with tens of thousands of files, that is constant background work. Pausing sync or enabling Files On-Demand dramatically reduces the per-file checks Explorer has to perform.
Should I worry if there are two explorer.exe processes?
Usually not. Windows sometimes runs a second explorer.exe for separate folder windows or the UAC-elevated desktop. Both should idle near 0% CPU. Worry only if one sustains high CPU, or if either process’s file location is not C:\Windows — that indicates malware impersonating the shell and needs an immediate offline scan.