Waypoint

What Waypoint is

Waypoint detects, sources, and installs drivers on Windows. It exists to fix the structural problems in the driver-pack tools technicians reach for, like Snappy Driver Installer, rather than give them a new coat of paint. There are two ways in: a command line built for automation and an IT toolchain, and a desktop app built for a person working through one machine at a time.

It's honest about where it is. Today Waypoint reads your real device tree and tells you exactly what it would do. It does not install a driver for you yet; that's the last gate it's working toward, and it won't pretend otherwise.

Provenance and safety first

The whole design starts from one rule: you should always know where a driver came from, and nothing irreversible should happen without a way back.

• Every candidate shows its source. No anonymous blobs pulled out of a pack. If Waypoint suggests a driver, it tells you where it got it.
• Ambiguous matches are refused. When several devices share one hardware ID, Waypoint blocks them until you confirm each by hand. On a real test machine that was 103 of 233 devices, and it's the exact failure mode behind one of Snappy Driver Installer's long-standing bugs.
• Nothing installs without a net. A batch requires a restore point first, replaced drivers are backed up before they're touched, and a signature policy gate stands in front of the whole thing.
• Every action is logged. An append-only audit trail records what happened, so a machine's history is something you can actually read back.

Before anything runs, Waypoint lays the installed driver next to the candidate and compares them field by field, so the change is visible instead of assumed.

A command line and a window

Both front ends sit on one shared core.

The command line is Native AOT: a single waypoint.exe that needs no runtime installed and no network, which is exactly the state a machine tends to be in when it needs a driver tool. scan, plan, apply, and driverpack all speak JSON and return contract exit codes, so they drop straight into scripts, Intune, or a PDQ job. apply is a dry run unless you pass --apply.

The window is for the technician: a triage tree that groups devices by tier and PnP class, and an installed-versus-candidate card that puts the two side by side before any decision. It ships as a signed MSI or a portable zip.

What works today

Waypoint is pre-alpha and specific about what that means. Validated on real Windows 11 hardware:

• Device enumeration through CfgMgr32, cross-checked against Get-PnpDevice for an exact match; 233 devices read in about 400 milliseconds.
• Hardware-ID ambiguity detection and blocking.
• scan, plan, apply, and driverpack as dry runs, with the full safety chain: signature gate, backup, restore point, audit log.
• The desktop window for scanning and inspection.
• Signed MSI and portable builds, with and without a bundled runtime.

Not there yet: installing. apply --apply has never run against a live driver, driver sources so far only cover Dell, Lenovo, and HP, and the builds are self-signed, so their reputation with SmartScreen and antivirus is still unproven. These are named gates, not surprises.

Why it's GPL

Waypoint is GPL-3.0-or-later, on purpose. The tool people currently reach for is closed and abandoned, and that is the exact problem Waypoint is trying not to become. Copyleft means anyone who ships a modified version has to publish their source, so a fork can't quietly turn into the next unmaintained binary nobody can inspect.

At a glance

Language

C# on .NET 8

CLI

Native AOT, no runtime needed (waypoint.exe)

GUI

WPF desktop app (waypoint-desktop.exe)

Platform

Windows

Stage

v0.2.0-alpha.1, pre-alpha (reads and plans; no install yet)

License

GPL-3.0-or-later

Source

github.com/TrashPanda2481/Waypoint-Driver-Manager