Network adapter updates: interface lifecycle reference

Adapter and interface are different objects

A network adapter can be integrated, add-in, USB-attached, virtual, or presented through another bus. Host software exposes a network interface with its own name, address properties, and state. Hardware identity and interface identity describe related but distinct records.

What a network package represents

A package can contain a miniport or function component, installation metadata, services, firmware coordination, and user-mode support. Its scope is the adapter contract. It is not the entire network stack, application protocol layer, router, gateway, or internet service.

Link state and application path

Enumeration and matching establish a device relationship; activation exposes an interface; link negotiation reports properties of the physical or wireless medium; protocol and application layers then use that interface. A link, interface, and application connection can change independently.

Version and release scope

Network release records may identify a package, binary, vendor extension, firmware bundle, or host-software channel. A version comparison should name the owner, adapter identity, architecture, and host interface contract rather than treating every number as the adapter’s one true version.

Physical and service boundaries

Cables, radios, antennas, access points, switches, credentials, name resolution, and provider service all sit around the host adapter. They can explain a connection observation without changing the host package or proving that one layer is responsible.

Questions and answers