If something goes wrong

Scan freezes or runs forever

• Try another USB port or cable; cheap hubs often throttle or brown out the drive.
• Let large drives run overnight; close other heavy apps and pause sync tools hitting the same volume.
• Watch Task Manager: if disk is pegged at 100% for hours with no errors, it may still be working; note whether the byte counter or filename list is still moving.
• Clicking sounds from the drive mean stop; consider professional cloning before the heads cause platter damage.

File won’t open after recovery

• May be partially overwritten; try another recovered copy with a similar size or path fragment.
• Wrong extension happens with carved files; test renames carefully and keep backups of originals before experimenting.
• Office and ZIP files fail loudly on tiny corruption; media may “almost” play. That pattern often means incomplete clusters, not a bad player.
• Encryption needs your password; recovery can’t bypass it.

Drive not listed

• Check in Windows Disk Management if the disk is online, initialised, and has a letter (or needs one assigned).
• Reseat SATA/USB; try a different enclosure or a direct SATA connection on a desktop.
• Some RAID or dynamic-disk layouts confuse simple volume lists; what you see in Disk Management is the source of truth.
• Virtualisation software and some disk-image tools can mount images as drives; confirm you selected the physical device you meant.

Safe download

• Prefer a download path you already use; compare file size and version to notes from that same path when you have them.
• Read each installer screen; skip extra offers you don’t want.
• If SmartScreen or your browser warns, pause and verify the URL and hash before you override.

Preview lies, file is fine (or the reverse)

• Thumbnails are hints, not proof; always open the recovered file from disk.
• If the preview is garbage but the saved file opens, trust the saved copy.
• If the file won’t open anywhere, try another recovered candidate or accept partial overwrite.

App closes, or antivirus blocks Recuva

• Update Windows and drivers; note the exact error text if it repeats.
• Add a temporary allow rule for the Recuva folder after you verify the binary source; don’t disable all protection.
• If something blocks the installer, verify the file source, then add a one-off allow rule; see Blog for storage tips.

“Unknown device” or disconnect loops

• Try the rear motherboard ports; front panels and passive hubs are common weak links.
• Listen for clicking; repeated head parks mean stop and consider professional help.
• Another PC or a live USB environment can tell you if the enclosure is the fault.

“Out of space” or can’t write recovered files

• Confirm the destination drive really has free space for the largest files you ticked, plus overhead.
• Run Recuva as a normal user first; if the folder is admin-only or on a network share with odd ACLs, pick a simpler path like D:\Recovered.
• FAT32 volumes cannot hold single files above 4 GB; use exFAT or NTFS for big videos.

Huge result list or sluggish UI after Deep Scan

• Deep Scan on large disks can return tens or hundreds of thousands of rows; sorting and scrolling may feel slow. Narrow with filters before you select all.
• Recover in batches instead of one giant queue; it keeps failures easier to retry.
• Close other RAM-heavy apps; very wide result sets are memory hungry.

Quick Scan shows nothing

• Quick Scan relies on live filesystem structures; after a format, heavy reuse, or TRIM on an SSD, the “deleted but listed” entries may be empty even when raw clusters still hold fragments.
• Run Deep Scan on the correct physical volume, not a different letter that points at another partition.
• Unlock BitLocker first; an encrypted volume looks empty to undelete tools until it is mounted with keys.
• On SSDs, keep expectations realistic: TRIM may have cleared free space already.

More context: SSDs and TRIM, Recovery flow.

Scan stops when the PC sleeps

• Windows suspends USB stacks and may park external disks on sleep; a multi-hour Deep Scan can stall or appear to reset when you return.
• Use AC power and temporarily prevent sleep for the session; avoid closing the lid unless you changed the lid action for that run.
• After wake, confirm the drive letter is unchanged before recovering, some hubs remount with a new letter.

Longer notes: Sleep and long scans.

Mapped drive or NAS misbehaves

• SMB shares and NAS paths depend on the network stack; timeouts and credential prompts can make a scan look hung before enumeration finishes.
• Remap the share from Explorer, open a file manually, then launch Recuva against that stable drive letter.
• When possible, scan on the machine that physically hosts the data instead of over a flaky Wi‑Fi hop.
• Pause heavy backup jobs on the NAS during the scan to reduce lock contention.

Expectations: Mapped drives and NAS.