DriveForge v4.3.3

v4.3.3 — 2026-09-28

Fixed

• A failed operation no longer leaves the progress bar claiming it is still working. When one ended with an
  error, the bar kept its last percentage and the line beneath it went on advertising a "Remaining" time that
  would never move again — directly above the dialog explaining the failure, with the Windows taskbar still
  showing a green progress bar underneath. The row is now cleared the moment the failure is known, before the
  dialog appears, and the elapsed time it reports is how long the work actually ran rather than how long the
  dialog was left on screen. This covers recovering files, recovering into a zip, imaging a drive, the surface
  test, exporting a bootable VHDX, moving a partition on both MBR and GPT disks, scanning for lost partitions,
  and setting up multi-boot.
• A failed multi-boot setup no longer leaves "Setting up multi-boot engine on Disk N..." on screen — including
  when it stops for a reason that is not an error at all: the target disk changing identity while the engine is
  still downloading.
• An operation that keeps its progress bar after a failure no longer quotes a "Remaining" time beside it.
  Wiping, shredding, backing up, writing an image and the capacity test deliberately leave the bar where the
  failure found it — on a destructive operation that number is the only thing on screen saying how far the write
  got — but the estimate next to it was still being calculated, and froze into a countdown that would never move.
  The bar stays; the estimate goes.
• Two exits that are not errors no longer leave the app saying it is working. Writing an image and formatting
  both stop before they start if the target drive turns out to have changed identity in the meantime; the status
  line survived that, and for formatting it survived a completed run too.

Under the hood

• Every build warning is gone — 299 of them, down to zero, with nothing about the app changed. Most (288)
  were nullable annotations sitting in files that had no nullable context; the project now switches that context on
  without switching on the nullable warnings, which makes the existing annotations legal without moving a single line
  of code. The rest were genuine leftovers: the WindowsDesktop SDK reference that has not been needed for years, two
  failure flags that were set and then never read, a progress-throttle field that had lost its reader, an always-zero
  addend in the file-carving size table, and a deliberately fire-and-forget screen update that now says so out loud.
  Each site was first examined for a missing check hiding behind the warning, rather than simply silenced — and the two
  real defects that search turned up are left for their own fix, since they change behaviour.

---

Full changelog