Capture before recovery
Failed-device state and traces preserve evidence that a removal or reinstall could otherwise reset.
Technical case study · PROJECT BREAKDOWN
An evidence-led investigation into a Wi-Fi Code 10 startup failure on one Lenovo Legion laptop. Driver traces, recovery tests, and a documented configuration workaround.
The adapter failed during startup while the original signed driver package remained installed. The investigation follows the failure through device state, trace evidence, and controlled recovery tests.
Failed-device state and traces preserve evidence that a removal or reinstall could otherwise reset.
The investigation compares failing and working states while retaining the original signed driver package.
Captured events, static country-table reconstruction, and user-reported follow-up are documented as different forms of evidence.
Single-system research · Vendor traces · Binary analysis · Recovery experiments
The core parts of the project, and the responsibility of each.
Collects Code 10 startup information and vendor trace events around a controlled restart.
Examines the matching driver binary's control flow and country-table structures.
Compares recovery behavior and saved configuration across adapter restart and reboot.
Record the failed state
Capture a controlled restart
Compare traces and code
Document results and limits
The features, boundaries, and implementation choices that shape the project.
The present MT7925 adapter reported Code 10 and status 0xC000009E. A command returning success did not by itself establish device recovery.
The captured failing start reached firmware-ownership acknowledgement before a later band-capability initialization failure.
Removing the exact Wi-Fi device node and rescanning recovered the device while keeping the existing signed driver package.
An offline binary candidate was constructed and checked but never installed. It is distinct from the configuration workaround used on the investigated laptop.
A summary of the documented case. The repository contains the full trace analysis and test context.
What the project uses, and where each technology fits.
Captures device state and vendor startup events.
Runs documented tracing and controlled recovery comparisons.
Inspects the matching Windows PE driver and its data structures.
Disassembles selected routines to compare embedded diagnostics with trace events.
How to explore the project, what it needs to run, and the current release status.
The public repository contains findings and source tools. Raw system captures and vendor binaries remain local.
One Lenovo Legion Pro 5 16ADR10 with a MediaTek MT7925 adapter; findings do not establish a universal repair.
The original signed driver remained installed. The experimental binary candidate was not deployed, and no driver package is distributed here.
Read the full report for the evidence, configuration context, and limitations. This page does not distribute driver packages or present the workaround as a general recommendation.