DriveForge 4.4.2 다운로드

A few sentences in the program point you at another task by name - "...you can restore it back to a drive later
with 'Restore image'". The name was written into the sentence, so the sentence was translated into all sixteen
languages and the name was not: in Romanian the text sent you to 'Restore image' while the button beside it read
'Restaurează imagine', and in Japanese to a label that was not on screen at all. Those sentences now carry a
reference to the task rather than its name, filled in from the same text the sidebar puts on the button, so the
two cannot disagree again - including after a rename.

This also carries everything from 4.4.1, which was not published here, so upgrading from 4.4.0 brings all of it:

- Choosing a base colour while in Light mode made the window unreadable - near-black panels under near-black
text - and "Reset to default" painted the panels in exactly the text colour. The only way out was a restart.
- Start-up overwrote your saved theme and accent with the defaults on every launch, so any appearance choice
survived exactly one restart. The window looked right for that session, which is why it never looked wrong.
- Drive health was decided by reading the drive's translated health label for the English word "OK", so the
three languages that properly translate it - Chinese, Japanese and Hindi - reported healthy drives as failing
and advised replacing them. Nothing was ever blocked and no data was at risk; the damage was the advice.
- The language list is in an order again: English first, then alphabetical by the name you actually read.
- The program opens on "Create Windows USB" rather than a clone task, so a destructive operation is no longer
the one under the cursor at launch.
- Sixteen translations still described an older, smaller recovery tool - NTFS only, no disk images, no preview.
- Changing language no longer blanks the Drive tools card, nor leaves the health trend note, the Clean total or
the Recover result in the language you just left.
- The About box had been reporting the wrong version since 4.4.0; it now comes from the build itself.