External drive disconnects while copying — causes and next steps

What it means when a drive disconnects during copying

When an external drive disconnects during copying, the system usually loses a stable connection with the device. The cause may be the cable, power supply, USB enclosure, overheating, or read problems such as bad sectors or unstable firmware. The most important rule is simple: do not keep copying "until it works" if the system freezes or reports errors. With symptoms like these, the safest path is HDD data recovery instead of further live testing.

Most common causes in practice

  • USB cable / port — a loose connector, poor shielding or a damaged cable.
  • Power supply — especially with 3.5" drives and USB hubs without a power adapter.
  • Enclosure / adapter — USB-SATA bridge errors, UASP issues or overheating electronics.
  • Read problems — the drive struggles on bad sectors and the controller drops the connection.

Safe steps before the situation gets worse

  • Swap the cable and USB port, preferably without a hub. If the drive has its own power adapter, use it.
  • If the symptoms keep coming back, stop copying. Repeated reconnects often worsen the condition of the drive.
  • Do not run CHKDSK or any "repair" tools — they may write to the drive and alter the data structure.
  • When the data is important, the safest path is HDD data recovery (or SSD recovery if the enclosure contains a solid-state device: SSD/NVMe data recovery) based on imaging and analysis performed on a copy.

When this may involve NAS or RAID

If the disconnecting affects drives in a server, NAS or an array, do not run rebuilds or "repairs" blindly. Follow the procedures for RAID/NAS recovery and stop all write operations. If the drive has bad sectors or behaves unstably, HDD data recovery is usually based on sector-by-sector imaging.

Want to minimise the risk? Submit the device and describe the symptoms — we will choose the safest imaging method. Go to the case form.

How to tell a cable issue from a read instability

A pure cable or port problem usually shows up as an immediate disconnect without extra symptoms once you move the connector or switch the port. A failing drive behaves differently: the transfer slows down first, folders open with a delay, the system may freeze for a moment and then the device reconnects. If you also see I/O errors, CRC messages or a prompt to format the disk, treat the case as a data-safety problem rather than a simple USB annoyance.

If this is the only copy, prepare the handoff instead of more tests

When the disk contains the only copy of photos, company files or client material, stop chasing more reconnect tests after the first sensible checks. It is better to document the symptoms, the cable/power setup and the exact moment of disconnect than to keep stressing the device. Helpful related guides: WD Passport I/O device error — diagnosis and repair, Drive needs to be formatted — what this message means and Do not use CHKDSK if the drive is damaged.

How to recognise unreadable-sector behaviour instead of a simple USB issue

A basic cable or port problem usually causes a clean disconnect: the drive disappears instantly, then comes back when the connector is moved or the port is changed. A failing disk behaves differently. The copy speed drops first, the system starts hanging while opening folders, transfer time jumps up and down, and the drive may disconnect exactly when the operating system reaches damaged areas.

If you see this pattern, do not treat it like an accessory problem. It is often the moment when users keep retrying large copies and push the drive into a worse state. A safer comparison is to check whether the symptoms match guides such as RAW drive — do not format or do not use CHKDSK if the drive is damaged.

How to protect the only copy before the next disconnect

If the disk holds the only copy of work files, photos or accounting data, stop trying to copy the whole device in the file manager. Start by listing the most important folders, the exact cable / enclosure / power setup, and whether the disconnect happens at the same point every time. This is far more useful than ten more attempts that all stress the medium.

When the data is important, the safest goal is controlled imaging, not heroic copying attempts from within Windows or macOS. If the symptoms already look unstable, prepare the case for HDD data recovery or SSD/NVMe data recovery depending on the device type, and keep the current state unchanged until diagnosis.

If you want to assess the case safely

If the files matter and you do not want to keep risking more experiments, use the contact form and describe the device, symptoms and the most important data. You can also review typical ranges on the data recovery cost page and go straight to HDD data recovery if you want the service path that fits this case best.