Explorer at thirty percent on an idle desktop is usually one shell extension, not a broken Windows. Finding it takes three steps and a restart each.
Restart **explorer.exe** to confirm the symptom, narrow it to a folder, then disable **shell extensions** in halves with **ShellExView**. A cloud sync client is the other frequent cause.
A restart of the process resets its state. If the CPU drops immediately and climbs again, the cause is loaded with the shell rather than being a system service.
taskkill /f /im explorer.exe & start explorer.exeRight-click a large folder and open properties, or browse a network share. A spike on one specific location points at a thumbnail handler or a sync overlay.
ShellExView shows every handler registered for Explorer in a single list with its publisher. Sorting by company separates Microsoft entries from third-party ones.
Disable half the non-Microsoft entries, restart Explorer and watch the CPU. Then halve the remaining half. Six or seven restarts find most offenders.
OneDrive, Dropbox and vendor launchers register overlays that run on every folder view. Quitting the client for ten minutes is a faster test than disabling ten extensions.
A constantly rebuilding search index keeps the disk busy and pushes CPU into the shell process. The index status page shows the progress and the item count.
control.exe srchadmin.dllA slow share or an offline sync layer. Test the same folder from another machine.
The index or a thumbnail cache rebuild. Let it finish before diagnosing.
The process is not the cause. Check for a third-party shell replacement.
The extension came back with its application. Uninstall the app instead of disabling its handler.
For finding the entry, yes. Windows has no built-in list of shell extensions.
Only its Explorer integration, such as the context menu entry or icon overlay.
Re-enable the extensions in ShellExView and restart **explorer.exe**. Every entry keeps its previous state after a restart.
Free · no account needed · tracks your progress