MetaDefender Drive v4.4.9

New Features

• Operator Accept Skipped/Threat Risk Admins can define approved skip reasons so Operators can bypass files or large archives that are unnecessarily delaying a scan, while also preapproving known safe or false positive files by hash. This helps scans complete faster while keeping skip decisions controlled and consistent.

• Skip By Hash Provide ability to skip trusted files by hash, reducing scan time and false-positive overhead.

• User reports include deleted files Scan reports now include a dedicated section listing each file that was removed during scanning, with its original path and cryptographic hash included before any boot-sector entries.

• MetaDefender Drive uses time and timeZone on Smart Touch Smart Touch Operator can set the time zone on Smart Touch and keep its clock in step, so scan times and reports carry the correct local time.

• Get all logs in any support package A support package collected from any one of MetaDefender Drive, MetaDefender Drive Toolkit, Smart Touch, or MetaDefender Drive In-Session are all included in the SupportPackage, so a single upload is enough to diagnose an issue.

• Provide posture check on MetaDefender Drive In-Session MetaDefender Drive In-Session verifies endpoint security posture before scanning, checking EDR, OS updates, and disk encryption in a single workflow.

• Dedicated workflow for Drive-Kiosk integration Kiosk Drive Integration is configured and managed under a dedicated workflow and with a new user interface.

Improvements and Bug Fixes

• MetaDefender Drive product's OPSWAT Central Management enrollment/unenrolment MetaDefender Drive, MetaDefender Drive Toolkit, and Smart Touch now display unified enrollment statuses so customers can instantly see whether their device is managed by Central Management.

• Administrators can push a MetaDefender Drive firmware upgrade from OPSWAT Central Management, so enrolled drives are updated centrally rather than one at a time by hand.

• A support package captured by booting MetaDefender Drive with Smart Touch carries the Smart Touch service logs alongside the drive's own, so a Smart Touch-layer fault can be diagnosed from that one archive.

• Support packages generated from MetaDefender Drive Toolkit include the Smart Touch logs, so a single archive covers the whole device instead of two separate collections.

• Archive scans report each file inside the archive as its verdict arrives, so a large archive shows steady progress rather than sitting at the same percentage for hours.

• Archives that no engine flagged are no longer reported as containing infected files, so a clean installer package passes rather than being blocked without a stated reason.

• MetaDefender Drive runs on the Pro Rugged Tablet RA02260, a device its boot environment previously did not handle.

• Files held inside an archive are reported with the correct verdict, so what a scan says about a compressed container matches what it actually contains.

• Scans that previously stuck at 98% finish normally rather than hanging for extended periods.

• A drive disconnected without shutting down can still be updated in MetaDefender Drive Toolkit: its file system is repaired first, and unreadable files are reported before flashing continues.

• MetaDefender Drive reconnects to OPSWAT Central Management when a lost connection is restored, so drive remains enrolled without manual intervention.

• The eject prompt on a Kiosk screen names the Eject button in the top-right corner, so an operator knows where to click instead of guessing how to remove the drive.

• Removing a drive that had no reports to sync ends with an informational message rather than a red failure, so operators do not investigate an error that never happened.

• Re-inserting a drive at a kiosk reuses the engines already downloaded to it, rather than pulling the whole definition set down a second time.

• Reports from a full in-session scan arrive with their passport page attached, rather than the report alone, so the result can be handed over as one document.

• When an update is triggered against an on-premises OPSWAT Central Management site that holds no engine packages, MetaDefender Drive Toolkit says so and points to the Updates setting, rather than stalling silently.