Skip to main content
Illustration for the windows update driver version management guide

How Windows Update Manages Driver Versions

Why Windows can offer a lower-looking version, how targeting and ranking work, and what administrative controls mean for future servicing.

By Sarah Jenkins Updated 2024-03-01Reviewer: Sarah Jenkins (2024-05-11)

Windows Update selects from packages declared applicable to a device. Its decision combines targeting metadata with Plug and Play ranking rather than comparing the largest visible number alone.

Topic 1

Different version branches

OEM, component-vendor, and Microsoft packages can encode dates and versions differently. A package described as older may contain a more specific subsystem match or an extension validated for the complete PC model.

Topic 2

Dynamic targeting

Microsoft can use hardware IDs, system models, operating-system builds, safeguard holds, and telemetry-based rollout groups to offer or withhold a driver. Catalog publication therefore does not mean every compatible system receives the package.

Topic 3

Control boundaries

Optional-update choices, update-hiding metadata, Group Policy, MDM, and device-installation restrictions operate at different layers. A broad exclusion affects future releases as well as the currently observed package.