Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
FixesError codesComponentsCommandsWindows updatesWindows 11
Research statusMethodology
Devices & drivers · reviewed troubleshooting

Driver install failed or changed unexpectedly: inspect SetupAPI.dev.log before reinstalling everything

Use Windows’ device-installation log to verify what driver package Windows tried to install, when it happened and whether signing/install errors were recorded.

Applies to: Windows 11Change risk: LowReviewed: 2026-09-17
Do this first
  1. Record the hardware/device instance and approximate time the driver changed.
  2. Open C:\Windows\INF\setupapi.dev.log as a read-only text file.
  3. Search near the matching timestamp and device/INF identifiers.
  4. Preserve the relevant section before rolling back, reinstalling or removing a driver package.

What this problem usually means

Microsoft documents SetupAPI.dev.log as the plain-text device-installation log used to verify and troubleshoot Plug and Play/driver installations, including signing problems. The default location is %SystemRoot%\inf\setupapi.dev.log.

Ordered repair path

Work from the narrowest fix to the broader one.

1

Use the installation log to establish chronology

Low risk

Why this belongs here: The log can show which device-installation section ran and whether the installation/signing path reported an error.

  1. Find the newest section matching the affected device or driver package.
  2. Compare its timestamp with Windows Update, Device Manager and the time the symptom began.
  3. Note INF/package names and explicit failure text rather than inferring failure from unfamiliar log lines.
2

Choose rollback/update/reinstall based on the actual change

Medium risk

Why this belongs here: A driver that failed to install, a newly introduced regression and a missing driver require different actions.

  1. If a new driver immediately introduced the symptom and rollback is available, use the device-specific rollback path.
  2. If installation failed/signing blocked, address the documented install error rather than deleting unrelated drivers.
  3. If the device remains missing, return to Device Manager/PnP detection and hardware checks.
Stop condition

When this guide stops being the right path

Do not delete SetupAPI.dev.log, force-remove driver-store packages, disable signature enforcement, or use broad driver-updater tools merely because the log contains warnings.

If the problem is still not fixed

Continue with the affected Device Manager code, driver rollback/reinstall guide, or hardware-vendor support using the exact package/device evidence you preserved.

Evidence

Sources reviewed for this page

Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.

Related authority records

Continue with the same failing system

These links share the same component or repair context; they are not generic keyword suggestions.

GuideDriver problem or hardware failure? Build the evidence before replacing parts or reinstalling Windows

Use device state, driver chronology, repeatability and vendor diagnostics to decide when Windows troubleshooting should hand off to hardware support.

ErrorCode 12 — Device Manager Code 12: Windows cannot find enough free resources for the device

Code 12 is a resource-allocation problem; confirm the exact device before changing other hardware or firmware settings.

ErrorCode 22 — Device Manager Code 22: the device is disabled

Code 22 means Windows sees the device but it has been disabled; enable the device before reinstalling drivers.

GuideDriver problem after Windows Update: update, roll back or reinstall the right device

Use timing and Device Manager status to choose between a newer driver, rollback and device-specific reinstall.

GuideNetwork adapter missing in Windows 11: prove device detection before TCP/IP repair

If Windows cannot enumerate the Wi-Fi/Ethernet adapter, DNS flushes and browser resets are the wrong layer; focus on Device Manager, hardware detection and the correct driver.

CommandPnPUtil — enumerate problem devices

List Plug and Play devices that currently report a problem code without modifying their drivers.