There’s a special annoyance in opening Task Manager and seeing Windows Explorer — the process that draws your desktop — sitting at 20%, 40%, or higher CPU while you do nothing. On Acer laptops this is a frequent complaint, and the explanation is architectural: explorer.exe doesn’t just show folders. It hosts the desktop, the taskbar, every context menu, every overlay icon, and every thumbnail — which means every third-party add-in, including Acer’s own, runs inside it and its CPU usage lands on Explorer’s bill.

So high Explorer CPU is really a “who’s hiding inside Explorer” mystery. The suspects: dead context-menu extensions from uninstalled software, cloud sync overlays in a sync loop, thumbnail generation stuck on a corrupt cache, and Acer’s preinstalled shell integrations. Here’s how to unmask them in order.

Start with the instant test: in Task Manager, right-click Windows Explorer > Restart. If CPU drops to near-zero and stays there, note how long until it climbs back — that timing tells you whether the trigger is constant or gradual. For the slow-Explorer (rather than CPU) variant, see our File Explorer slow on 24H2 guide ; for the general high-CPU hub, the best Explorer CPU fixes cover adjacent cases.

Why this happens

  • Dead context-menu extensions: Uninstalled programs leaving handlers that time out inside Explorer’s process.
  • Cloud sync overlay loops: OneDrive/Dropbox overlays re-evaluating icon states continuously during stuck syncs.
  • Corrupt thumbnail cache: Forcing full regeneration on every folder visit instead of using cached results.
  • Acer shell integrations: Acer utility context menus and overlays adding per-interaction overhead.
  • Preview pane on media folders: Generating live previews for every selected video/document.
  • Search indexer querying through Explorer: Heavy indexing manifesting as Explorer CPU during folder browsing.
  • Corrupt system files: Damaged shell components looping on operations that should be instant.

How to fix it

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

Fix 1: Restart Explorer and observe the pattern

Get your baseline before changing anything.

  1. In Task Manager > Processes, right-click Windows Explorer > Restart — the desktop will briefly vanish and return; this is normal.
  2. Watch Explorer’s CPU for 10 minutes of normal use. Drops to ~0% and stays there? The trigger may have been transient — monitor for a day.
  3. Climbs back gradually over hours? Something loaded at startup is leaking or accumulating — suspect shell extensions (Fix 2).
  4. Spikes immediately when you open a specific folder? That’s thumbnails/previews (Fix 4) or a network location timing out.
  5. Spikes only on right-click? That’s definitively a context-menu extension — go straight to Fix 2.

Fix 2: Disable third-party shell extensions

The highest-yield fix for Explorer CPU issues.

  1. Download ShellExView from NirSoft (free, portable) and run it as administrator.
  2. Go to Options > Hide All Microsoft Extensions — now you see only third-party code running inside Explorer.
  3. Sort by Type and focus on Context Menu handlers. Select all non-Microsoft ones, right-click > Disable Selected Items.
  4. Restart Explorer from Task Manager and test for 30 minutes — right-click files, browse folders, use the desktop normally.
  5. If CPU is cured, re-enable extensions in small batches to find the offender; leave it disabled or update/reinstall its parent program. Pay special attention to Acer utility entries and old codec packs.

Fix 3: Calm the cloud sync overlays

Sync clients inject icon overlays into every file display.

  1. Click the OneDrive cloud icon > Settings and check sync status — a stuck or perpetually “syncing” state keeps overlays churning. Pause syncing for a few hours as a test.
  2. If you use Dropbox, Google Drive, or similar, pause them too — test one at a time to identify the culprit.
  3. In OneDrive settings, review Files On-Demand: folders set to online-only force status checks on every browse; set frequently-browsed folders to Always keep on this device.
  4. As a deeper test, unlink OneDrive temporarily (Settings > Account > Unlink this PC) — if Explorer CPU normalizes, the sync client’s shell integration was the cause; reinstall the latest client version.
  5. Keep only the sync clients you actively use — each one adds overlay handlers to every Explorer window.

Fix 4: Fix thumbnails and the preview pane

Media folders are Explorer’s heaviest workout.

  1. Open Disk Cleanup, select the system drive, check Thumbnails, and click OK — this clears the corrupt cache forcing regeneration loops.
  2. In File Explorer, press Alt+P to disable the preview pane, and hide the Details pane from the View menu.
  3. Test the previously problematic folder — if CPU stays flat now, thumbnails were the loop.
  4. For a permanent setting on huge media archives: right-click the folder > Properties > Customize > Optimize this folder for: General items — this reduces thumbnail generation.
  5. If you installed a third-party codec pack (K-Lite etc.), its thumbnail handler is a prime suspect — update it or uninstall it and test.

Fix 5: Audit Acer’s preinstalled integrations

Acer’s extras run inside Explorer’s process.

  1. Settings > Apps > Installed apps: review Acer entries — Acer Care Center, Acer Quick Access, Acer Product Registration — and uninstall what you never use.
  2. Check ShellExView (from Fix 2) specifically for Acer-published extensions you may have missed.
  3. Open Acer Care Center > settings and disable background monitoring/checkup features you don’t need — its helpers can poll the shell.
  4. Check Task Manager > Startup apps for Acer helpers and disable the non-essential ones.
  5. Re-test Explorer CPU for a day; factory-integration CPU issues usually vanish once the unused utilities are gone.

Fix 6: Check for indexer and search interference

Search activity surfaces as Explorer CPU.

  1. Open Indexing Options and check whether “Indexing in progress” — a stuck or endless re-index manifests during folder browsing.
  2. Rebuild the index if it seems stuck, or narrow scope via Modify — exclude folders you never search.
  3. In Folder Options > Search tab, uncheck Include system directories and Include compressed files — these make every Explorer search dramatically more expensive.
  4. Test browsing with the Search service temporarily stopped (services.msc > Windows Search > Stop) — if Explorer calms down, the indexer was the hidden load.
  5. If confirmed, either rebuild the index properly or reduce its scope permanently rather than leaving the service stopped.

Fix 7: Repair system files and verify

When the shell itself is damaged.

  1. Run sfc /scannow from an elevated Command Prompt, then DISM /Online /Cleanup-Image /RestoreHealth — corrupt shell components cause exactly these looping behaviors.
  2. Install all pending Windows updates — Explorer CPU bugs get fixed in cumulative updates; specific KBs are on the Microsoft Update Catalog .
  3. Test in a fresh local user account — if Explorer behaves there, your profile’s shell configuration (extensions, settings) is the cause; migrating is cleaner than endless hunting.
  4. As a final check, run a Microsoft Defender Offline scan — persistent unexplained Explorer CPU deserves a malware rule-out.
  5. Microsoft’s Windows support hub documents the official file-explorer troubleshooting steps as a reference.

Closing

Explorer.exe high CPU on Acer laptops is almost never Explorer’s fault — it’s the add-ins living inside it: dead context-menu extensions, churning cloud overlays, a corrupt thumbnail cache, or Acer’s own shell integrations. Restart to confirm, strip third-party extensions with ShellExView, calm the sync clients, and clear the thumbnail cache. Explorer goes back to idling at 0%, which is the only CPU usage a file manager should ever have.

Frequently asked questions

Why is File Explorer using so much CPU on my Acer laptop?
Explorer.exe hosts the desktop, taskbar, and every folder window, so its CPU usage reflects everything plugged into it: third-party context-menu extensions, cloud sync overlays (OneDrive, Dropbox), thumbnail generation for media folders, and the search indexer querying through it. On Acer laptops, preinstalled utilities add their own shell extensions and overlay icons, multiplying the load. Sustained high CPU almost always means one of these add-ins is stuck in a loop, not that Explorer itself is broken.
Is it safe to restart Windows Explorer from Task Manager?
Yes, completely safe. Restarting Windows Explorer (right-click it in Task Manager’s Processes tab > Restart) just reloads the shell — your apps keep running, unsaved work in other programs is untouched, and the desktop/taskbar reappear within seconds. It’s the standard first-response diagnostic: if CPU drops after the restart but climbs back over hours, something Explorer loads at startup is the leaker; if it stays high immediately, the trigger is active right now.
Can Acer's preinstalled software cause Explorer CPU spikes?
Yes. Acer ships utilities that integrate with Explorer: context-menu entries, overlay icons for cloud/backup features, and background helpers in Acer Care Center and Quick Access. Each one executes code inside Explorer’s process, so a buggy or outdated Acer extension shows up as explorer.exe CPU. Disabling third-party shell extensions with ShellExView (keeping Microsoft’s) is the fastest way to test this theory without uninstalling anything.
Why does Explorer CPU spike when I open folders with videos or photos?
That’s thumbnail and preview generation: Explorer extracts thumbnails and metadata for every media file in the folder, which is CPU-intensive for videos especially. Normally it caches the results and the spike is brief; if it never settles, the thumbnail cache is corrupt (forcing regeneration every visit) or a codec pack’s thumbnail handler is crashing in a loop. Clearing the thumbnail cache and disabling the preview pane are the quick fixes.