When a computer function works in another app, user account or port, keep the repair inside the failing context. For Windows external drive, first use a known cable and direct port, inspect Disk Management and copy a noncritical test file.
What this covers
- Windows external drive with this exact failure state
- Diagnosis across drive versus cable, enclosure, USB power, filesystem and host port
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 reliably and read/write without disconnects or filesystem errors.
Isolate the component boundary
ReversibleUse a known cable and direct port, inspect Disk Management and copy a noncritical test file. Swap only the app, account, cable, port or user profile while keeping the computer unchanged. Boundary to separate: drive versus cable, enclosure, USB power, filesystem and host port.
Correct only the proven cause
ReversibleReplace the failed path or repair only after an image/backup of important data. 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 writing after clicks, repeated disconnects, I/O errors or unique data risk.
Evidence ledger
Sources behind this answer
Exact questions