When a computer function works in another app, user account or port, keep the repair inside the failing context. For Windows File Explorer, first open a local known folder, disable preview for one test and disconnect unavailable network paths.
What this covers
- Windows File Explorer with this exact failure state
- Diagnosis across local disk versus network/cloud path, preview handler and storage health
What it does not cover
Try in this order
0 of 4 completedCapture the exact failure state
ReversibleName the failing app, user account, port or peripheral and one that still works. Expected behavior: enumerate folders and storage without hanging on one path or extension.
Isolate the component boundary
ReversibleOpen a local known folder, disable preview for one test and disconnect unavailable network paths. Swap only the app, account, cable, port or user profile while keeping the computer unchanged. Boundary to separate: local disk versus network/cloud path, preview handler and storage health.
Correct only the proven cause
ReversibleRepair the failed extension/path or storage device rather than resetting Windows. Repair the isolated app, user profile, driver binding or physical path.
Verify and stop safely
ReversibleRetest both contexts after sign-in and one cold restart. Stop for drive errors, clicking, disconnects or the only copy of important data.
Evidence ledger
Sources behind this answer
Exact questions