Login or Register
FULL AI ANALYSIS

Windows 11 indexer uses 100% CPU after switching OneDrive account and folder paths

Generated Oct 3, 2026, 12:35:03 AM

Analysis summary

High CPU with repeated indexing activity around OneDrive paths plus OneDrive sync paused alleviating the issue point to a feedback loop between the OneDrive file change notifications/placeholders and Windows Search. Files On‑Demand can cause rapid metadata changes as placeholders are rehydrated or probed by indexers. Corrupt search database, problematic file-type filter, or uncontrolled update events from the OneDrive client can keep the indexer busy indefinitely.

Possible causes

OneDrive Files On‑Demand placeholders generating repeated change notifications that keep the indexer continually re-scanning

85%

A bug or race in the OneDrive client emitting spurious file system events while doing background health checks

80%

Search database corruption combined with frequent metadata churn in OneDrive folder

40%

Corrupt or incompatible IFilter/IFX for a specific file type leading the indexer to repeatedly fail and retry

15%

Suggested fixes

1

Diagnostic step 1

Temporarily pause OneDrive sync and confirm CPU returns to normal to validate correlation — reversible via the OneDrive UI

2

Diagnostic step 2

Exclude OneDrive paths from Windows Search (Indexing Options) and observe CPU for several hours; if stable, re-enable and allow a full rebuild during low‑use hours

3

Diagnostic step 3

Collect ETW traces for SearchIndexer and OneDrive with Windows Performance Recorder (short 2–5 minute captures) to spot repeated file change events and stack traces for hot threads before escalating

4

Diagnostic step 4

Check for third‑party IFilters: uninstall or disable custom file-type filters and test; rebuild the index only after testing exclusions

5

Diagnostic step 5

If index rebuilds fail repeatedly, stop Windows Search, back up and remove the Search database folder, and restart (this is reversible by restoring the folder backup) — escalate to Microsoft support if ETW traces show one process constantly injecting file events

Contact • Help • API Docs • Careers • Terms • Privacy • Cookies • Ads