Scanner 0.1.0-rc.1

Meet your Windows scanner.

A local, read-only application that connects your Windows hardware and driver information to your private DrvBeacon report.

Why a local scanner?

Browsers cannot access Windows device inventory, installed-driver records, or Windows Update applicability information directly. The scanner uses Windows APIs on your PC and sends its technical report only to an approved DrvBeacon session you start.

Normal scans run with your current user permissions. Unavailable fields are reported gracefully; the scanner does not require administrator privileges by default.

What it scans

Computer model, CPU, memory, graphics, storage, Windows, devices, installed drivers, Device Manager problems, and applicable Windows driver updates.

What it does not scan

Documents, passwords, browser history, clipboard, microphone content, or camera content. It does not install, download, remove, or update drivers.

Private temporary reports

The scanner validates a temporary token before starting an upload scan. Reports require the browser session that created them and expire after 15 minutes by default. Serial numbers and system UUIDs are not requested; raw device-instance identifiers are replaced with per-scan tokens.

Download Scanner

Public downloads are not available yet. Unsigned release-candidate and development artifacts can be built from this repository; they are not an installer or a signed public release.

Windows x64

For 64-bit Intel and AMD Windows PCs.

Not available for download

Windows ARM64

For ARM-based Windows PCs. Requires native ARM64 validation before a public release.

Not available for download

The executable is not Authenticode signed. DrvBeacon product metadata is not a verified publisher identity. Do not disable Windows protections or certificate checks to run a build.

Development setup

  1. Build the correct architecture using the repository’s publish script. For localhost, use the separate development build.
  2. Keep the executable in a stable folder you control. Self-contained builds do not require a separate .NET installation.
  3. Optionally run .\DrvBeacon.Scanner.exe register-protocol from that folder. This explicitly registers only the current executable for your Windows user.
  4. Start a scan on the website, then select Open DrvBeacon Scanner. The browser may prompt before launch.
  5. To remove this executable’s registration, run .\DrvBeacon.Scanner.exe unregister-protocol before moving or deleting it.

No registration happens just by running a scan. Existing unrelated protocol handlers are not overwritten. The website cannot reliably detect installation, so a manual command remains available.

The final official HTTPS API domain has not been configured. Production builds fail closed for web uploads until it is selected; local testing uses a separate development build.