A computer feature or peripheral that has completely stopped should be separated into driver, permission and physical-connection layers before assuming component failure. 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
ReversibleCheck Device Manager or System Information for whether the hardware is even detected, and whether an error code is shown. 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. Test the peripheral on a different port or user account, and test a different peripheral on the same port. 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. Reinstall or roll back the driver, or grant the missing app permission.
Verify and stop safely
ReversibleConfirm the feature works after a full restart in at least two different applications. Stop for drive errors, clicking, disconnects or the only copy of important data.
Evidence ledger
Sources behind this answer
Exact questions