Diagnostic step 1
Temporarily enable detailed Indexer logging: in Event Viewer enable diagnostic logging for 'Microsoft-Windows-Search' and reproduce the search to capture precise failure codes; do not change policies yet.
Generated Oct 3, 2026, 12:35:03 AM
Temporarily enable detailed Indexer logging: in Event Viewer enable diagnostic logging for 'Microsoft-Windows-Search' and reproduce the search to capture precise failure codes; do not change policies yet.
Check and compare folder attributes (hidden, system, reparse point) and NTFS ACLs on original OneDrive path vs new D:\OneDrive_Projects. If reparse points or symlinks are present, remove only for testing and restore afterwards.
On a test user account, move a small sample folder to D: (not under OneDrive) and confirm it indexes; this isolates OneDrive-specific behavior from general indexing problems.
Coordinate with corporate IT to temporarily allow cloud-content indexing for your machine or to whitelist the new OneDrive path; share the Event Viewer indexer errors and timestamps to help them diagnose policy interactions.
If third‑party security software is present, add the new OneDrive folder to its trusted/scan-exclusion list for a short trial and test indexing. Revert exclusions if no effect. Escalate to corporate support if policy blocks are suspected—do not override enterprise policies yourself.