Find Files Lost During an Interrupted Copy or Move in Windows

Inspect both transfer endpoints, compare surviving content, and target recovery where the original bytes existed.
XAppSet Team
Published on November 14, 2026

If a cut-and-paste transfer stopped and the source appears missing, check both the original location and the destination before attempting recovery. A cancelled transfer may leave an intact source, a complete destination, and partial destination files in the same job. Preserve any usable copy and compare content. Do not use Ctrl+Z blindly: undo behavior depends on the operation history and is not a universal file-recovery method.

Laptop, notebook and a separate portable storage drive

Record the exact operation

Note whether you chose Copy or Cut/Move, the complete source and destination paths, the tool used, and the interruption. Determine whether the paths were on one volume, different volumes, removable storage, or a synchronized folder. Two different folders are not necessarily two different volumes.

Windows can move files in different ways. Microsoft’s MoveFileEx reference describes a cross-volume route that copies and then deletes the source. That API behavior explains why the endpoints matter; it does not prove how every third-party transfer application committed every file in your job.

Inspect source and destination without merging them

Open each actual location directly in File Explorer. Search for a missing filename at both endpoints and their relevant parent folders. A same-volume move may change the path without producing a second full data copy; a failed copy may leave the original untouched.

Use a simple working list with expected path, source presence, destination presence, size, and whether the file opens. Do not automatically accept “replace all,” delete apparent duplicates, or restart the whole move over the remaining copies. Preserve intact files to a separate destination first.

For a cloud destination, check the correct account on the web as well as the local folder. A local transfer finishing and a completed cloud upload are different events. Do not delete the source until the destination you intend to rely on is verified.

Compare a surviving pair

If both files exist, compare their contents. For critical files, calculate SHA-256 hashes on stable readable copies:

Get-FileHash -LiteralPath 'D:\Source\clip.mp4' -Algorithm SHA256
Get-FileHash -LiteralPath 'E:\Destination\clip.mp4' -Algorithm SHA256

Substitute real paths. Matching hashes establish a content match between those two files; they do not prove that the source was healthy before it was copied. See Microsoft’s hash documentation. Open the intended document or media and verify its required contents as well.

Recover only what is missing

If the source was deleted and no complete destination exists, minimize writes to the original source volume. Scan readable storage with XRecovery from another disk and export candidates separately. A partial destination is worth preserving, but it may never have received the missing bytes; scanning it cannot recover data that was not written there. Check backups and the original source first. If either device repeatedly fails reads, stop repeated transfers and assess that device’s readability before proceeding.

Windows deleted-file recovery guide

Privacy Overview
XAppSet

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.