DriveForge 4.5.1

What's new in 4.5.1

!DriveForge

v4.5.1 — 2026-10-17

The same audit, carried on into the screens 4.5.0 did not reach — and this time every fix was measured on
real hardware before and after, not read. Nineteen changes, no new features: updating is safe from any
4.x, and nothing here changes a file format or a saved setting.

Two faults in here could have cost someone data. Both were found the same way: by asking the app to do the
dangerous thing and then checking the disk itself, rather than believing the dialog.

Fixed — a drive erased that you never chose

• The scheduled clone offered to erase a drive it was never scheduled for. With a 1 GB drive scheduled
and a second drive of the same model name connected, the next start announced *"The drive your scheduled
clone writes to is connected: … 32.0 MB … It ERASES this drive"* — a different disk entirely, already
selected, one Yes away from being formatted. The offer matched on the model name alone and took the first
hit, ignoring the size and serial number recorded in the very command line it had just read. The
unattended run refuses to guess in exactly that situation; the offer guessed. Both now ask the same
question in the same place, and the offer stays quiet when it cannot be certain.
• "Is this my drive?" was answered with a tolerance wider than most drives. The size had to be within
1 GiB — flat — so a 32 MB disk passed for a 1 GB one and the unattended run took it as its target. It
survived only because Windows does not fit on 32 MB. The margin is now one percent of the recorded size,
never more than 64 MiB.
• Two names for one file were offered as two copies. The duplicate finder counted directory entries
where it had to measure distinct storage: a hard-linked pair came back as a "duplicate set" and pushed the
reclaimable total up by a whole file, when deleting either name frees nothing at all. Both finders — exact
and "similar photos" — now compare the volume serial and file index.
• The protected folder only counted if you picked it before the scan. Choose it afterwards and the rule
ticked your master copy red and kept a different one. The deletion itself re-read the box and spared the
file, so the screen and the deed disagreed, and "keep 1 per set" quietly became keep 2.

Fixed — what the app did behind your back
…

Full release notes »