Laptop driver update state reference
A vocabulary for candidate packages, selected components, runtime activation, and retained records on a laptop.

A laptop update is component-specific
An update record can concern a wireless adapter, audio controller, touchpad interface, display function, chipset relationship, or another device. The laptop context explains how components coexist, but the package candidate and selected record belong to one defined hardware relationship.
State has a sequence and an owner
Available, matched, selected, staged, active, and retained describe different lifecycle points. Catalogs and package stores own some records, installation services own others, and device or runtime layers expose their own state. A single status label cannot represent every point in that sequence.
Platform dependencies are explicit
Internal laptop components can rely on firmware interfaces, embedded controllers, power transitions, and companion services. An update record can name those relationships without implying that every package in the same laptop family shares them.
Compare like with like
A meaningful comparison pairs package metadata with package metadata, device state with device state, and runtime interface state with runtime interface state. Mixing a package version with an endpoint or firmware status creates a misleading lifecycle story.
Reference facts
- Scope
- One laptop component or device relationship at a time
- State terms
- Available, matched, selected, staged, active, and retained
- Dependencies
- Firmware, embedded controllers, power, and companion services
Questions and answers
Does “updated” prove that every laptop component changed?
No. Update records normally have a device or package scope and do not describe the entire platform.
Can a device be selected but not active?
Yes. Selection and runtime activation are different lifecycle transitions.
Why can a laptop state look different across components?
Each component has separate identifiers, packages, services, firmware relationships, and runtime boundaries.