How to Recover a PC That Lost Power During a File Copy
I’ll explain how to protect the original files, determine what the interrupted copy actually left behind, check filesystem health without making matters worse, and choose between retrying, recovery software, or restoring from a backup.
A power cut during a file copy can leave you with several different problems: a complete source file and an incomplete destination file, filesystem errors, missing directory updates, or—if you used a move operation—uncertainty about where the only usable copy now resides. The safest response isn't to start clicking through every recovery tool. First, preserve what you have, then establish what changed.
Stop and protect the drives
If the computer has just restarted, avoid immediately repeating the copy, deleting partial files, or running a “repair” utility. Every write to the affected drive can overwrite data that recovery software might otherwise find. This matters most when the destination contains the only copy of a file, or when the source was a removable drive that is behaving unusually.
If the interrupted transfer involved an external hard drive, USB flash drive, or memory card, disconnect it cleanly after the system has finished mounting it. If the drive is making repeated clicking sounds, disappearing, reporting the wrong capacity, or becoming extremely slow, shut the computer down and stop experimenting. Those symptoms can indicate hardware failure rather than an ordinary interrupted copy.
For a normal internal drive that appears stable, you can continue with a cautious inspection. If possible, make a full backup or a sector-by-sector image of the affected drive before attempting repairs. An image is especially useful when the drive is failing because it lets you work on a copy instead of repeatedly stressing the original.
Check your recovery starting point: Before opening files or repairing the drive, confirm which location held the original, which held the destination, and whether either location contains another backup. If the destination may be the only surviving copy, treat it as a recovery case rather than an ordinary failed transfer.
Determine whether the transfer was a copy or a move
A copy operation normally leaves the original data in place and creates a second copy at the destination. If the power failed halfway through, the destination may contain a partial file while the original remains usable. In that situation, the original is usually your safest starting point: verify it, preserve it, and copy it again to a different destination if you have enough storage.
A move is more complicated. Within the same drive, a move may primarily update directory information rather than rewrite all the file data. Between different drives, it generally involves copying data and then removing the source. A power interruption can therefore leave the file at the source, at the destination, in both places, or in neither location as a normal visible file. Don't assume that a missing shortcut or folder entry means the underlying data is gone.
Also consider whether you used a program that stages, compresses, synchronizes, or verifies files. Backup and sync applications may keep temporary files, logs, version histories, or conflict copies in places that ordinary file browsing doesn't reveal. Reopen the same application and inspect its job history before changing its folders manually.
Inspect without trusting the partial file
Let the operating system finish any automatic startup checks, then inspect the source and destination with read-only actions first. Compare filenames, sizes, timestamps, and—where practical—checksums. A partial file can have a plausible name and a large size while still being unusable.
For documents, open a copy rather than the only version. A word-processing document may open with a warning and silently discard damaged sections; a compressed archive may list some contents while failing later; a video may play through its beginning while missing its index or final segment. An application’s ability to open a file is useful evidence, but it isn't proof that the file is complete.
If you know the expected size or have a checksum from the original system, use that information. For a repeatable comparison, calculate a hash of the source and destination after copying them to separate locations. Matching hashes provide strong evidence that two files have identical contents; different hashes show that they differ, but they don't by themselves tell you which one is correct.
Don't use file size alone as your test. Some formats reserve space in advance, some contain padding, and some remain readable despite losing important data near the end. A checksum, application-level validation, or comparison with a known-good backup gives you more useful confidence.
Check the filesystem before repairing it
An interrupted write can leave filesystem metadata inconsistent, even when the files themselves are mostly intact. Modern filesystems use journaling or similar techniques to reduce this risk, but those mechanisms generally protect filesystem structure—not the contents of a file that an application was still writing. A completed directory listing therefore doesn't guarantee a completed transfer.
First check whether the operating system has marked the drive as needing attention. Windows may offer a drive scan or repair prompt; macOS Disk Utility includes First Aid; Linux distributions commonly provide filesystem-specific checking tools. The exact commands and options vary by filesystem and operating-system version, so use the documentation for your system rather than copying a command intended for a different drive.
Before a repair operation, back up important readable data and close applications using the drive. Filesystem checks can remove orphaned entries, reconnect fragments, or place recovered pieces in special folders. That may fix the structure, but it can also change how damaged data is presented. Never treat a repair utility as a substitute for a backup or file-recovery plan.
For a system drive, follow the operating system’s instructions about offline or recovery-environment checks. For an external drive, make sure you identify the correct volume before choosing a repair option. A command aimed at the wrong disk can turn a recoverable mistake into a much larger one.
Retry only when the original is safe
If the source file still exists and can be read normally, the lowest-risk solution is usually to copy it again to a new destination. Don't overwrite the partial destination until you have confirmed that the source is healthy and that you no longer need the partial file for comparison or recovery.
Use a different destination when practical, particularly if the original destination is showing errors or is nearly full. A copy that repeatedly stops at the same point may indicate a bad sector, a failing cable or enclosure, a permissions problem, a full filesystem, or a file that another program is still changing. Repeatedly retrying without finding the cause can add stress and obscure the original symptoms.
For large transfers, a tool that can resume and verify files is more appropriate than dragging everything again. Read its behavior carefully: some tools resume by appending, some replace the partial file, and some compare timestamps instead of contents. Verification should compare the completed destination with the source, not merely report that the transfer reached 100 percent.
If the file is part of a live database, virtual machine, mail store, project folder, or application library, don't copy it while the application is using it. Create an application-supported backup or snapshot first. A power interruption may have affected internal transactions that a simple file copy can't make consistent.
When recovery software is appropriate
Recovery software becomes more reasonable when the original file is missing, the filesystem no longer lists the expected directory, or a move operation removed the source before the destination was complete. Stop writing to that drive as soon as you recognize this situation. Install recovery software on another drive, and save recovered files to another physical drive—not back onto the one being examined.
There are two broad recovery approaches. Filesystem-aware tools try to reconstruct names, folders, and metadata from surviving directory structures. File-carving tools search for recognizable file contents and may recover data when the directory information is damaged, but they often lose filenames and folder organization. Carving also performs poorly with fragmented files and may produce incomplete results.
Start with a full scan or image when the drive is unstable, and preview recovered files before deciding they are usable. Recovery tools can display a file that has the right extension but contains only fragments. Check representative files from each important folder, and compare their contents with known versions where possible.
If the data is irreplaceable, the drive is failing, or the transfer involved sensitive business or legal material, professional recovery may be safer than repeated home scans. Continuing to power a failing drive can reduce the chance of success. A professional service can't guarantee recovery, but it can use controlled imaging and hardware-specific techniques that ordinary software can't.
Decide whether a backup is the better answer
Recovery isn't always the best use of effort. If a verified backup contains the complete file, restoring it is generally safer than reconstructing a damaged destination. Check the backup rather than assuming it is current: restore a copy, open it with the relevant application, and confirm that it contains the needed version.
If you have multiple versions, choose the newest one that is known to be complete instead of automatically selecting the file with the latest timestamp. Synchronization services can replicate deletions or damaged files, while versioned backups may preserve earlier states. Look for retention history, snapshots, or an archive that wasn't connected during the power failure.
Once the important data is safe, replace questionable cables, test the external enclosure or power supply, and investigate whether the computer lost power because of an overloaded circuit, failing battery, or unreliable connection. A surge protector may help with some electrical events, but it isn't a substitute for regular backups or an uninterruptible power supply where an orderly shutdown matters.
The practical sequence is simple: preserve the source and destination, identify whether the operation was a copy or move, validate files instead of trusting their names, check filesystem health carefully, and only then retry or recover. If the original is intact, make a fresh verified copy. If it is missing and the drive is unstable, minimize use and consider imaging or professional recovery. The best outcome isn't merely getting the computer to show a file again; it is knowing that the file you recovered is complete and that you have another safe copy.