BBTech Laptop Inspection Tool

BBTech refurbishes and tests laptops, and the step that used to depend on a technician's memory was drivers: which device is missing one, which is running on a generic Microsoft driver, where the right package is, and whether the fix actually took. The tool answers all of that from one screen. A technician presses Start Inspection and gets the laptop's identity, every hardware category with a status, each device's hardware ID, driver provider, version, date, INF, signature and Device Manager problem code, and the official source for anything that needs replacing.

It is an inspection tool first. No drivers are bundled; packages are downloaded from the laptop manufacturer, the hardware manufacturer or Microsoft only when needed, and kept in a folder the technician chooses. Physical hardware testing is a separate BBTech process, and the tool never presents a driver result as one.

One PowerShell process, read-only and without administrator rights, returns the computer, BIOS, operating system, CPU, RAM, every PnP entity with its hardware and compatible IDs and problem code, the signed drivers, video, monitors, physical disks, network adapters, audio endpoints and OEM services in about six to twelve seconds. A parser turns that into typed system and device records; a classifier assigns each device a category from its PCI or USB class code, NDIS medium, setup class or name pattern, and separates virtual devices; a status rule grades each driver as OK, missing, error, disabled, generic, warning or unknown.

The engine folds those into one result per category and a final verdict: Ready, Issues Found, Manual Inspection Required or Driver Installation Required. A full inspection with internet access also asks the official sources whether a newer driver exists. Every slow step runs on a worker thread, so the interface never freezes. The classifier's tests run against a real captured ThinkPad scan kept as a fixture, alongside malformed-data cases.

Fix Driver Issues is a chain: find, download, install, verify, scan again. Resolution adapters parse the Lenovo, Dell and HP catalogues for the exact hardware ID and expected version, fall back to Windows Update, and otherwise offer the official link; firmware is never installed automatically. Downloads go through a URL allow-list that refuses HTTP, spoofed domains, credentials in the URL and redirects off the allow-list, and each file is checked by size, hash and Authenticode signature before anything runs.

Installation refuses unsigned packages, commands outside the package and INF files without a catalogue, maps exit codes (0, 3010 restart pending, failures) honestly, and uses pnputil, the vendor's silent installer, MSI or Windows Update as the package dictates. Verification re-queries the device and reports verified, still broken, wrong version, device gone or restart pending. The rule throughout is no false success: Installed only when Windows confirms it, Verified only after the fresh check passes.

98 automated tests cover hardware ID parsing, detection on the captured scan, the inspection engine, catalogue parsers and ranking, the download allow-list and failure modes (hash mismatch, 404, interrupted, truncated, unofficial redirect), installation refusals and exit codes including zip-slip, the end-to-end fix workflow, the download location rules, and reports and history. Every test uses an isolated data folder and none installs a driver or changes Windows. A test mode with six scenarios shows an orange simulated-data banner on every screen and in every report.

The build script produces a one-folder build, an Inno Setup installer with silent flags, and a portable single EXE that keeps its history, logs and settings next to itself on the BBTech USB drive. Reports export as PDF, TXT, CSV and JSON, and the runtime depends on PySide6 and requests only. The user guide, architecture, driver resolution, installation, testing and troubleshooting documents ship with the repository.