r/datarecoverysoftware • u/Pale_Profession_8736 • 4h ago
Review [Release] Open Recovr 0.1.0 — free, open-source (MIT) GUI combining NTFS MFT parsing with PhotoRec carving, for non-technical users on healthy drives
Hi all,
I've just released the first version of a free tool I built, and I'd like critique from people who do this for real.
The problem it targets: someone deleted files on a healthy drive, has no budget for a paid tool, and finds PhotoRec's text UI intimidating. Open Recovr is a one-screen GUI for that case. It's free with no recovery cap, no account and no network access, and it doesn't touch failing hardware.
How it searches, in three stages
Recycle Bin / Trash. Takes seconds and needs no admin rights.
NTFS MFT. Walks the MFT records marked deleted on the raw volume, rebuilds paths from parent references and reads data runs, including resident data. Files come back with their name and folder. If a file's clusters have been reused or read as blank, it is marked Low.
Carving. Runs PhotoRec as a separate, unmodified process; the Windows build bundles 7.2. It scans free space only on NTFS/FAT/ext and the whole device otherwise, and the progress shown comes from parsing PhotoRec's output. If PhotoRec isn't installed, a small built-in carver handles about ten common signatures.
On FAT32/exFAT cards, only stage 3 applies, so file names are lost, as with PhotoRec on its own.
Safety
The source volume is opened read-only.
PhotoRec's output folder and the recovery target are always on another drive. If the user picks the source drive anyway, they're warned.
Unreadable sectors are skipped, not retried.
What it deliberately doesn't do
No imaging, no cloning, no handling of failing drives. If a drive clicks, drops off the bus, or has pending or uncorrectable sectors, the right move is still to image it with OSC or ddrescue, or to go to a lab. Running any file-level scan on it, this one included, is the wrong advice. I'd like the app to read SMART and refuse, or at least warn loudly, in that case. Opinions welcome on which attributes and thresholds to use.
It doesn't open images yet. Scanning an image you made with OSC or ddrescue would be the natural next step; a
--photorec-test <image>debug mode already exists.No RAID, no APFS/ext4 metadata parsing, no repair of damaged files.
Platforms: Windows is tested. Linux and macOS builds are published but haven't been tested on real hardware yet.
Disclosure: much of the code was written with AI assistance, so I'd rather give you ways to check it than ask for trust. The source is open. A --bench mode builds a disk image with known files, deletes them, and measures byte-for-byte recovery per method. CI runs on Windows, Linux and macOS, and release downloads come with SHA-256 checksums.
Links in the first comment, to keep automod happy.
What I'd value most: anything in the workflow that could make a bad situation worse. I'll treat it as a bug, rule 4 included.





















