User guide
Illustrated guide for Datattoo Recovery Technician. The PDF matches the signed download currently published on this site.
- Safety before scanning: Stop writing to the affected drive. Never recover onto the source. SSD TRIM can erase recoverable clusters.
- Portable launch and signature verification: When a signed build is published, verify Authenticode publisher and SHA-256 before running. Datattoo is fully portable—you can copy the executable to a thumb drive or memory card and run it from there. Accept the EULA when prompted; no separate installer is required for portable use.
- Required privileges: Run with the privileges needed for volume access (often Administrator).
- Select the correct source: Drive letter, partition, physical source where exposed, or raw disk image.
- Opening a raw image: Provide the image file and optional partition offset. Unsupported formats are not claimed.
- Quick Metadata scan: Metadata-oriented discovery. It does not silently become Deep Carving.
- Deep Carving scan: Signature-oriented discovery that may generate fallback names when metadata is missing.
- Pause, resume, cancel, and safe exit: Stop long jobs cleanly; do not force power-off mid-write to the destination.
- Search, filtering, sorting, and selection: Narrow candidates before recovery.
- Filename provenance and original-path confidence: Treat missing or low-confidence names/paths as evidence limits, not product defects. FAT deleted short names may show an explicit
[unknown]first-character marker when the deletion marker overwrote the original byte and no authoritative LFN survives. - Recoverability condition versus final outcome: Pre-recovery conditions estimate chance/quality of evidence. Complete / Partial / Unverified / Failed are assigned after recovery and validation.
- Preview and warnings: Read warnings before selecting candidates.
- Choosing a destination: Different volume, enough free space, source ≠ destination.
- Recovering files: Recover selected candidates, then read the validation report.
- Final report and SHA-256: Keep hashes and warnings with the job record.
- Logs: Installed builds use
%APPDATA%\DatattooRecovery\Logs; portable runs useData\Logsbeside the executable. - When to stop: Clicking, burnt smell, flood damage, or unreliable detection → hardware laboratory, not another logical scan.
Troubleshooting
- No useful candidates: Data may be overwritten or TRIMed.
- Permission errors: Elevate privileges and ensure no exclusive lock blocks the source.
- Partial or Unverified after recovery: Treat as validation outcomes; do not relabel them as Complete.
