A computer problem starting right after a Windows or macOS update, a new peripheral or a software install should be checked against that specific change before a factory reset. 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
ReversibleNote the exact update version or newly installed software, and confirm the prior working state. 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. Uninstall the new software or roll back the update in a controlled test, where the OS supports it. 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. Apply the vendor's fix for the update, or reconfigure the setting the new software changed.
Verify and stop safely
ReversibleConfirm stable operation with the update or new software present for one full session. Stop for drive errors, clicking, disconnects or the only copy of important data.
Evidence ledger
Sources behind this answer
Exact questions