Windows 11 Search returns no results after relocating C:\Users to D:\Users with directory junctions

Environment

Windows 11 Pro 22H2 workstation, user profile originally on C: (NTFS), moved to D: (different physical NVMe) using robocopy /MIR and created directory junctions (mklink /J C:\Users D:\Users). Indexing options show default Windows Search service (WSearch) running.

Symptoms

Start menu and Explorer search return no file results for user documents and desktop items; Cortana searches app results but not local files. File properties and files are present and accessible via Explorer manual navigation. Search in other locations (e.g., C:\Windows) still yields results. Rebuilding the index in Settings starts but shows 0 items indexed for user folders.

Observations

WSearch service runs under LocalService. Indexing Options -> Advanced -> Index Location shows the database path on C: (default) and indicates '0 items indexed' until the service is restarted. Event Viewer (Applications and Services Logs -> Microsoft -> Windows -> Search) shows repeated warnings indicating 'Path not indexed: D:\Users<username> - Access is denied' even though a local admin account can list files. The directory junction at C:\Users appears as a reparse point; permissions on D:\Users inherit from D: root and contain user ACLs. Disabling antivirus temporarily did not change behavior.

Already attempted

Restarted WSearch service, forced index rebuild, removed and re-added user folders in Indexing Options, reset folder permissions to inherit from parent, granted WSearch service account explicit read on D:\Users, created a new local user whose profile is created directly on C: (works correctly), checked for group policies redirecting folders (none).

Question

Why does Windows Search refuse to index user files after relocating Users to another volume using directory junctions, and what reversible steps will identify whether this is an ACL/privilege issue, a reparse-point limitation, or a Search service sandboxing constraint? How can indexing be restored without moving user data back to C:?

Post timeline

COMMUNITY RESPONSES

Verified community troubleshooting

0 replies

No answers yet..

Showing 0 of 0 community responses

AI DIAGNOSTICS

Incident analysis

Updated 1w ago• Trouble ID

Most likely causes

Windows Search service sandbox or service account cannot follow directory junctions pointing user profiles to another volume, resulting in access-denied behaviors. 80%

Missing or mismatched Owner/ACL/SID entries on D:\Users that prevent indexing from resolving SDDL expected for profile directories. 45%

Windows security features (Controlled Folder Access / Windows Defender Exploit Protection) blocking indexing of mounted volume or reparse points. 25%

Summary

Event log entries reporting 'Access is denied' for the D:\Users path despite file-level access indicate Windows Search's indexing process lacks the required rights to traverse the junction target or that it treats reparse/junctions as excluded. Directory junctions for system profile folders are not fully equivalent to native profiles, and WSearch may run in a reduced context that cannot follow junctions or may be blocked by the Windows Resource Protection or Controlled Folder Access. The fact a newly created profile on C: indexes normally and that adding explicit ACLs didn't help suggests the search service treats the reparse point as outside of its allowed scope or that the junctioning method broke some security identifiers expected by Search.

Suggested Fixes

Diagnostic step 1

Check and record current ACLs and owners for C:\Users (junction) and D:\Users (target) using icacls; avoid bulk ACL resets until backup of ACLs is taken.

Diagnostic step 2

Temporarily add the WSearch service account (NT SERVICE\WSearch) full read/list rights to D:\Users and a test file and restart WSearch to see if indexing resumes for that folder.

Diagnostic step 3

Create a symbolic link (mklink /D) or relocate only specific indexed folders (Documents, Desktop) using Known Folders redirection through registry/profile settings rather than directory junctioning system-wide; test indexing behavior.