Network-adapter package lifecycle reference
The identity, package, interface, and runtime layers that describe a network adapter over its lifecycle.
Adapter identity
A network adapter can be physical, integrated, virtual, or presented through a bus device. Its identity includes the transport and hardware context, while host software exposes a network interface with its own name, address properties, and state. Those two identities should not be treated as interchangeable.
Package roles
A network package can contain a miniport or function component, installation metadata, service relationships, and supporting user-mode pieces. The package describes how host software can represent the adapter; it does not become the entire network protocol stack above it.
Interface lifecycle
Enumeration and matching establish the device relationship. Activation creates or updates the network interface representation, and runtime components exchange commands, link events, and packet data with the adapter. Link state, interface state, and application connectivity are separate observations.
Version records in context
Network driver versions can identify a package, a miniport binary, a vendor extension, or a co-installed component. A useful record names the layer and transport before comparing versions or release notes.
Reference facts
- Adapter forms
- Physical, integrated, virtual, or bus-presented
- Core runtime role
- Connect network stack abstractions to adapter commands and data
- Distinct states
- Device identity, interface state, link state, and application path
Questions and answers
Is a network interface the same as the adapter hardware?
No. The interface is a host-software abstraction backed by an adapter and several software layers.
Does a network driver contain TCP/IP?
Not generally. A driver connects the network stack to adapter-specific behavior; protocol layers above it have separate roles.
Can one computer have multiple records for one adapter?
Yes. Hardware identity, interface identity, package components, and virtual representations can each have separate records.