Windows · files

Windows File Explorer stopped working after an update, outage or hardware change

A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. This record isolates Windows File Explorer through local disk versus network/cloud path, preview handler and storage health.

Direct answer

A failure immediately after a known change should be checked for new defaults, stale pairing, power sequencing or compatibility before factory recovery. 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
  • Customer-accessible observation, settings and external components

What it does not cover

  • ×A displayed manufacturer error code with a different documented meaning
  • ×Live electrical, sealed-system, internal battery-cell or gas repair
  • ×A claim that every model exposes identical controls
Try in this order0 of 4 completed
  1. Capture the exact failure state

    Reversible

    Record the change, version, outage time or newly connected hardware and the last known working state. Expected behavior: enumerate folders and storage without hanging on one path or extension.

  2. Isolate the component boundary

    Reversible

    Open a local known folder, disable preview for one test and disconnect unavailable network paths. Remove or roll back only the reversible change, or test the previous direct path. Boundary to separate: local disk versus network/cloud path, preview handler and storage health.

  3. Correct only the proven cause

    Reversible

    Repair the failed extension/path or storage device rather than resetting Windows. Reapply compatible settings, update both endpoints or replace the incompatible new path.

  4. Verify and stop safely

    Reversible

    Restart twice and confirm the feature remains stable with the intended change present. Stop for drive errors, clicking, disconnects or the only copy of important data.

Evidence ledger

Sources behind this answer

Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.

Exact questions

Common follow-ups

What should I check first when Windows File Explorer has this problem?+

Open a local known folder, disable preview for one test and disconnect unavailable network paths.

Why not factory-reset immediately?+

The useful boundary is local disk versus network/cloud path, preview handler and storage health. A reset can erase state without proving which side failed.

When should I stop troubleshooting?+

stop for drive errors, clicking, disconnects or the only copy of important data.

Change recordAug. 17, 2026 — Published as a distinct component-state record for Windows File Explorer; it is not a manufacturer-name permutation.
Report a correction
Wrong device or version?

Match the path before repeating the steps.

Match another device