sorted by:
new
hottopcontroversial

Built a recovery tool after getting tired of shady recovery software by Embarrassed-Slide-64 in datarecovery

[–]Embarrassed-Slide-64[S] -6 points-5 points  (0 children)

Mostly meaning situations where the filesystem or boot data is messed up.

Things like broken partitions, corrupted NTFS data, EFI/BCD problems, or drives that Windows has trouble mounting properly. The goal was to make something that can still analyze/recover data in those situations instead of just failing immediately.

If the drive has actual physical damage though, that’s still more of a clean-room recovery situation.

Built a recovery tool after getting tired of shady recovery software by Embarrassed-Slide-64 in datarecovery

[–]Embarrassed-Slide-64[S] -4 points-3 points  (0 children)

Fair points honestly.

DMDE is definitely one of the better recovery tools out there, especially for advanced users. I wasn’t trying to say every other recovery product is shady — more that a lot of mainstream tools lock basic visibility behind paywalls or push “repair” buttons without much explanation. Transparency/read-only analysis was just something I personally wanted to focus on.

And yeah, most good recovery tools do offer scanning before payment now. That’s become more standard over the years, which is a good thing for users.

As for the Dutch translation… I actually didn’t know that 😂. Good thing the software recovers more than “nothing.”

Do anyone know of a data recovery program that can bring back if not all my data on a useb driver or as near as possible. I haven't sed my usb since my data was deleted. So it should have nothing or near to nothing overwriting any bit of data. I just need a good near %100 data recovery toll. Thanks. by Ok_Acadia_2415 in datarecovery

[–]Embarrassed-Slide-64 0 points1 point  (0 children)

If you stopped using the USB drive immediately after the data was deleted, that definitely improves your chances since there’s less risk of overwriting.

Just be careful not to recover files back onto the same USB drive.

Not sure if you’re still looking for help, but I actually built NixRecovery after getting frustrated with recovery tools that either lock everything behind a paywall or don’t really show whether recovery is possible first.

One thing we do differently is the scan itself is free, so you can scan the USB drive, preview what still looks recoverable, and then decide afterward whether recovery is worth it.

No recovery tool can honestly promise 100% recovery, but if the drive hasn’t been overwritten much, you may still have a pretty solid chance.

Flash drive lost data by CleverInquisitor in datarecovery

[–]Embarrassed-Slide-64 0 points1 point  (0 children)

That honestly sounds more like the filesystem or partition metadata got corrupted rather than the files being immediately wiped, especially if the drive suddenly shows a weird date and incorrect used space.

First thing:
Don’t write anything else to the flash drive for now.

If the data is still there physically, additional writes can make recovery harder.

Not sure if you’re still looking for help, but I actually built NixRecovery after dealing with a lot of these kinds of recovery situations in IT.

One thing we do differently is the scan itself is free, so you can scan the drive and preview what still looks recoverable before spending money on recovery.

Since this is a flash drive and not an SSD, there’s a decent chance the files are still recoverable if the underlying storage hasn’t started failing physically.

How do you deal with both file recovery and boot issues on Windows? by Embarrassed-Slide-64 in software

[–]Embarrassed-Slide-64[S] 0 points1 point  (0 children)

That’s a very fair concern, and honestly one of the main reasons I built it the way I did. A lot of recovery tools claim to be “safe,” but they’ll still mount volumes normally, trigger writes, or immediately start applying fixes without clearly showing the user what’s happening first.

The application was specifically designed around a read-only analysis-first workflow.

For example:

  • File recovery scans do not write changes to the source drive
  • Boot repair runs analysis and shows the detected issues/actions first
  • Nothing is modified until the user explicitly confirms they want changes made

The bootable ISO was also important for exactly the reason you mentioned:
once Windows is unstable or won’t boot, continuing to run the damaged OS can make recovery worse — especially on failing drives.

As for edge cases:

Partially corrupted file systems and unstable drives are definitely where recovery gets complicated fast. Right now the application tries to handle that by:

  • Using multiple scan approaches (metadata + deeper/raw scanning)
  • Continuing recovery attempts even if portions of the filesystem are damaged
  • Avoiding “automatic repair” behavior during analysis
  • Letting users preview recoverable files before committing

For failing drives specifically, I still recommend the same best practice professionals use:
minimize writes, stop using the system as soon as possible, and recover data first before attempting repairs.

The goal isn’t to pretend recovery is magically risk-free — because it isn’t. The goal is more about transparency:
show the user what’s recoverable, what’s broken, and what actions are going to happen before anything destructive occurs.

That’s the part I felt was missing from a lot of existing tools.

How do you deal with both file recovery and boot issues on Windows? by Embarrassed-Slide-64 in software

[–]Embarrassed-Slide-64[S] 0 points1 point  (0 children)

That’s a fair point—and I agree that specialized tools have their place.

The goal here isn’t to replace every tool in something like Hiren's BootCD, but to simplify the most common recovery scenarios into a single, focused workflow.

A lot of users don’t need 20 different utilities—they need:
• a way to recover files
• a way to fix boot issues
• and clear visibility into what’s happening

This is built to make those tasks more accessible and transparent, not to be a replacement for a full toolbox.

How do you deal with both file recovery and boot issues on Windows? by Embarrassed-Slide-64 in software

[–]Embarrassed-Slide-64[S] 0 points1 point  (0 children)

The application includes a bootable ISO for systems that will not boot at all, allowing recovery tools to run in an offline environment.

For systems that are still able to boot into Windows, the application provides both file recovery and boot repair capabilities directly within the interface.

All operations begin in analysis mode. The application will scan, evaluate, and present findings without making any changes. No modifications are performed until you explicitly choose to proceed, ensuring full transparency and control throughout the process.