Investigate a device problem that began after an update

Confirm the sequence before assigning blame

An update near the start of a problem is a useful clue, not proof. Windows Update history can show recent quality, feature, and driver updates. Device Manager can show the affected device’s driver provider, date, and version. Compare those records with the first failed task, but also consider a newly attached dock, changed cable, app update, permission change, low battery event, or a problem that only became noticeable then.

State the symptom precisely and reproduce it once. “Wi-Fi is broken” is less useful than “the adapter is present, but disconnects only after sleep on the home network.” Test whether the same device behaves differently after a normal restart, on another network, or without accessories. If the symptom disappears when the dock or peripheral is removed, preserve that result instead of replacing a laptop driver immediately.

Inspect the affected device and make one response

Open Device Manager, locate the device, and choose Properties. Record the General-tab status and the Driver-tab details. If the issue clearly began after a driver change and Roll Back Driver is available, rollback is the narrowest response. It restores the preceding driver for that device rather than undoing unrelated software. Restart if requested and repeat the original task.

If rollback is unavailable, do not force a driver from a component-maker site merely because the device name looks familiar. Check the exact laptop model’s official support page and Windows Update for a compatible package or a known resolution. A manufacturer may package graphics, power, audio, or wireless support differently for one laptop family. Install only the package relevant to the evidence, then test before making a second change.

1. In Settings, review Windows Update history; in Device Manager, record the device status and driver version.
2. Restart Windows and repeat the specific failed task with nonessential accessories removed.
3. Use Roll Back Driver only for the affected device when a recent matching driver is evident and the control is available.
4. If rollback is not an option, use Windows Update or the exact laptop manufacturer package, restart, and retest.

Read the result and choose the failure branch

Expected result: the original task works after the restart, and the symptom does not recur in the same conditions. Record what changed and pause there. Avoid applying a collection of optional drivers simply because one rollback helped; the evidence only supports the component you tested.

If the issue remains, check the device status or error code and return to the physical or settings layer. For example, test a direct display connection instead of the dock, confirm camera privacy permissions, or use a different network. If the device is absent, fails before Windows loads, or produces repeated crashes, further driver swapping may obscure a hardware, firmware, or power issue. Take the record to the laptop maker’s support channel.

A Windows feature or quality update is not the same thing as a driver update. If Windows Update history shows a system update but the device-driver date did not change, do not describe the event as a driver regression. Use the recovery options Microsoft documents only after you understand their scope and have backed up important files. The narrowest useful action is preferable: fix an app permission in the app, a cable at the cable, a device driver at that device, and a wider Windows problem through the appropriate recovery path.

Frequently Asked Questions