DriverGuard

Free while we’re in preview

Get DriverGuard

Copy a folder's exact bytes now, so you can put one file back later.

The Mac button is for Apple Silicon. On an older Intel Mac, get this one instead.

One file, both ways. Double-click it for the window. Run the same file from a command prompt with arguments and it behaves as the command-line tool, because the engine is inside it. Nothing else to download and nothing to keep beside it.

Early preview. The window has been built and run, but not yet on a real Windows PC or Mac, so expect rough edges. The engine underneath it is fully tested.

One file, no installer
Runs on your machine, offline
Source code published below

Free while in preview. It isn’t signed yet, so Windows or macOS will ask you to confirm the first time you open it. here is exactly what to click. At launch, DriverGuard is included in every plan along with the rest of the range.

What a snapshot is here

Not a list of hashes. DriverGuard hashes every file under the directory with SHA-256 and copies the real current bytes into a snapshot store, mirroring the directory structure. That’s the whole reason it can restore anything: the content is sitting there, not just a fingerprint saying something changed.

Then, later

check compares the directory as it stands now against a snapshot and splits the answer into CHANGED, REMOVED and ADDED. Added files are informational. Changed or removed files make it exit non-zero, which is enough to wire into a scheduled job that shouts at you.

Putting one file back

rollback --file config/settings.ini restores that single file to the bytes it had at snapshot time. Without --apply it tells you what it would do, whether that’s overwriting a changed file or recreating a deleted one, and touches nothing. Name a path that was never in the snapshot and you get a clean error.

Where the name oversells it

It’s a directory watchdog, not a driver tool. No Windows driver store inventory, no update-source verification, no SetupAPI rollback. Point it at a drivers folder, a config folder, or anything else you want to be able to undo.

Questions about DriverGuard

What does DriverGuard do?

DriverGuard takes a full copy of a folder you need to stay exactly as it is — drivers, settings, licences, anything you would rather not find quietly altered. Later it tells you precisely what has changed, gone missing or turned up since. If something has been changed for the worse, it can put a single file back to exactly what it was, byte for byte.

Will DriverGuard delete my files?

No. Anything DriverGuard takes away is moved into a folder you choose, with its path kept, so you can look through it and put anything back. It also prints the entire plan first and stops until you tell it to go ahead.

Does DriverGuard send anything over the internet?

No. There is no network code compiled into DriverGuard at all, nothing in the binary can open a socket. 88 of the 100 programs here are like that.

Does DriverGuard run on a Mac?

Yes. There are builds for Apple Silicon and for Intel Macs, as well as for Windows and Linux, one file each, with no installer and nothing to uninstall.

Is DriverGuard free?

Yes, while Techlosoft is in preview: no account, no card, and nothing switched off. Later it is part of a plan covering all 100 programs rather than sold on its own, and anything you download now carries on working.

Reading on the job itself

How to back up drivers before an update Copy the driver store to somewhere off the machine before you change anything, and record a hash of every f...

The rest of Driver Safety Center

Drivers and the state a machine was in before you touched them: a saved copy, a version list, a sealed record, and a way back.

DriverPilot

Vertical Ready

Inventory a driver folder before and after an update, then diff the two.

DeviceDriver

Pro Ready

Seal a driver folder's fingerprints, then prove months later that not one byte changed.

DriverRollback

Team Ready

Snapshot a driver tree, then get the exact bytes back. Dry run unless you insist.

Advanced & technical details Command-line builds, source code, checksums and a recorded session, for developers and IT teams

A working CLI prototype of the "every change reversible" core: snapshot a critical directory with real backup copies of every file, detect what changed later, and roll back a specific file to its snapshotted state. Real driver-store inventory and OS-level driver rollback need privileged Windows-only SetupAPI access and are on the roadmap.

Naming status

Working name only — brand verdict **RENAME** (High). Collision: Driver Guard. Rename before launch.

What it draws on

Existing paid software whose best ideas shaped this program: IObit Driver Booster Pro, Driver Easy Pro, Auslogics Driver Updater, Revo Uninstaller Pro.

Command line

There is nothing extra to install. The program you download is the command-line tool as well: give it arguments instead of double-clicking it and it runs as one, with its output on your terminal. The standalone builds below are the same engine on its own, for machines where you would rather not ship a window at all.

driverguard - file-integrity watchdog with real restore-point copies

Usage:
  driverguard snapshot <dir> --store <storedir> [--label mylabel]
  driverguard check <dir> --store <storedir> [--against <label-or-latest>] [--json]
  driverguard rollback <dir> --store <storedir> --file <relative-path> [--against <label-or-latest>] [--apply]
  driverguard list --store <storedir> [--json]

Commands:
  snapshot   Walk <dir> recursively, hash every regular file, and copy each
             file's current bytes into <storedir> as a restorable snapshot.
  check      Compare <dir>'s current state against a stored snapshot and
             report CHANGED / REMOVED / ADDED files.
  rollback   Restore one file at <dir>/<relative-path> from a snapshot's
             backup copy. Dry-run by default; pass --apply to actually write.
  list       List all snapshots present in <storedir>.

Run 'driverguard <command> -h' for command-specific flags.

Recorded from the shipped binary, not written by hand.

Windows (amd64) macOS (Apple Silicon) macOS (Intel) Linux (amd64)

Source

Every file the program is built from:

console.go · console_test.go · guided.go · main.go

SHA-256 checksums · build instructions & scope notes · full build plan