NewAI Content Creation is now live in Early Access
Turning Point Training Instituteby Training Center
Skip to content
0%
Module 10 — Operating System, Software and Account TroubleshootingLesson 2 of 4
Video lesson

Updates and Drivers

BeginnerVideo lesson
9 min readBeginner

Where you are: Module 10 — Operating System, Software and Account Troubleshooting · Lesson 10.2 · Based on Chapter 10 (§10.3) of Dr. Tahseen Al Doori's Troubleshooting Essentials.

What you'll be able to do

  • Recognise when a sudden fault is likely to have been caused by a recent update or driver change.
  • Roll back a driver, uninstall an update or use System Restore, choosing the smallest change that works.
  • Report a faulty update to the vendor and pause it temporarily.
  • Explain why a system must never be left permanently unpatched as a workaround.

Watch: Updates and Drivers

The video follows a fictional designer's laptop whose display starts to flicker after an overnight graphics driver update. It shows the book's response as a sequence, the Windows 11 Roll Back Driver steps, three ways back from a bad change, and how the case is closed and documented. As you watch, ask:

  • What evidence links the fault to the update, rather than to coincidence?
  • Why use the smallest rollback first?
  • Why is pausing an update acceptable, but switching updates off permanently is not?

Updates: necessary, and occasionally the cause

Updates fix security problems and bugs. Security fixes close weaknesses that attackers could otherwise use, so keeping systems updated is one of the most important protections they have. Occasionally, though, an update introduces a new fault: a driver that does not suit a particular graphics card, or a patch that conflicts with an older application.

A driver is the small piece of software that lets the operating system control a hardware device, such as a graphics card, printer or network adapter. Because drivers sit between hardware and software, a faulty driver can produce dramatic symptoms: flickering screens, devices that disappear, or a computer that crashes during startup.

The book's guidance starts from a simple observation: if a problem began immediately after an update, that update is the first theory to test. This is the "What changed?" question from Module 2, and the rollback technique from Module 6.

The book's response

Confirm the timingRoll back driver or updateOr System RestoreReport to vendorPause it until fixedInstall corrected version
  1. Confirm the timing. Check the update history and the event log. Did the fault begin straight after the update, on the device that received it?
  2. Roll back the update or driver. Device Manager on Windows offers Roll Back Driver.
  3. Or use System Restore to return the system to an earlier working state when a single rollback is not possible or does not help.
  4. Report the problem to the vendor, so that a corrected version can be produced.
  5. Pause automatic updates for that component until a corrected version is released, so the faulty version does not simply reinstall itself.
  6. Install the corrected version and verify.

Never leave a system permanently unpatched as a workaround. A pause is temporary. An unpatched system stays exposed to every security problem fixed since the pause began, which can be far more damaging than the fault the update caused.

Three ways back, smallest first

Choose the narrowest tool that undoes the change. The smaller the rollback, the less else you disturb.

ToolWhat it undoesWhen to use it
Roll Back DriverOne device's driver, returned to the previous versionA fault in one device after a driver update
Uninstall an updateOne Windows updateA fault that followed a specific update
System RestoreSystem files, settings and installed programs, back to a restore pointNarrower options are not available or do not help

All three change the system, so the planning rules from Step 4 of the methodology apply: record the current state, make sure data is backed up, and know how you would reverse the rollback itself.

Beyond the book (2026 note): Current Windows 11 menu paths, from Microsoft's own support pages. Roll Back Driver (administrator rights needed): right-click Start, select Device Manager, expand the category, right-click the device, select Properties, open the Driver tab, select Roll Back Driver, choose a reason, select Yes, and restart if prompted (Update drivers through Device Manager in Windows). Uninstall an update: Start > Settings > Windows Update > Update history, then under Related settings select the option to uninstall updates, choose the update and select Uninstall; some updates cannot be uninstalled, and Microsoft advises understanding the risks before removing a security update (How to uninstall a Windows Update). System Restore: Control Panel > Recovery > Open System Restore, or press Windows key + R and run rstrui.exe; Microsoft states it undoes system changes without affecting personal files (System Restore). Pause updates: Start > Settings > Windows Update, then pick a date on the Pause updates control. The pause covers Windows updates generally, not a single component; it can run for up to 35 days, and updates resume automatically when it expires (Pause updates in Windows). On a Mac, updates are under Apple menu > System Settings > General > Software Update (Update macOS on Mac). In managed organisations, update policy is usually set centrally, so check with IT before pausing anything.

Worked example

(Fictional scenario.) A designer's laptop screen starts to flicker on a Monday morning, and the external monitor stays blank.

  1. Identify. When? Since the morning restart. What changed? The update history shows a new graphics driver installed overnight. Who? Only this laptop; colleagues with the same model did not receive the driver yet.
  2. Theory. The new graphics driver is incompatible with this laptop's display setup.
  3. Test. The event log shows display driver warnings beginning at the first startup after the update. The timing matches.
  4. Plan. The smallest rollback is Roll Back Driver for the display adapter. The designer's files are saved to the company's cloud storage, and the current driver version is recorded so the change can be reversed.
  5. Implement. Device Manager, Display adapters, Properties, Driver tab, Roll Back Driver. The laptop restarts.
  6. Verify. The flicker has gone and the external monitor works. The designer confirms both screens behave normally in their usual applications.
  7. Document and follow up. The ticket records the driver version, the symptoms and the rollback. The fault is reported to the vendor and, following IT policy, updates are paused on this laptop. Twelve days later a corrected driver is released; it is installed and tested, and the pause is lifted. The laptop is fully patched again.

Try it

This activity is observation only. Do not roll back, uninstall or pause anything on your own computer.

  1. On a Windows computer, open Settings > Windows Update > Update history and list the three most recent updates with their dates. (On macOS, use the Software Update screen described in the 2026 note above; on Linux, check your package manager's history.)
  2. Open Device Manager and find your display adapter. On its Driver tab, note the driver date and version, and whether Roll Back Driver is available. Close the window without making changes.
  3. Write a short plan, in the book's six-step sequence, for this report: "Since yesterday's update, my laptop's Wi-Fi keeps disconnecting."

You have finished when you have recorded three recent updates, your display driver's version and date, and a six-step written plan that includes a report to the vendor and a time limit on any pause.

Knowledge check

A fault began immediately after a graphics driver update. Which Windows tool lets you return to the previous driver for that device?

Why should you choose the smallest rollback that works?

A faulty update has been rolled back and reported to the vendor. Which approach does the book recommend next?

Why must a system never be left permanently unpatched as a workaround?

Answers explained

  1. a — Roll Back Driver returns one device to its previous driver; ipconfig /release affects network addressing, Disk Cleanup removes files, and a private window affects only the browser.
  2. b — the narrowest rollback undoes the suspected change while leaving everything else as it was; larger rollbacks exist, System Restore keeps personal files, and verification is always required.
  3. d — the book says to pause automatic updates for that component until a corrected version arrives; permanent switch-off, reinstalling and closing without follow-up are all wrong.
  4. c — updates fix security problems, so a permanently unpatched system stays vulnerable; the other options are not reasons the book gives and are not true in general.

Key takeaways

  • A fault that appears immediately after an update makes that update the first theory to test.
  • Roll back with the smallest tool that works: driver, then update, then System Restore.
  • Report the fault to the vendor and pause the update only until a corrected version arrives.
  • Never leave a system permanently unpatched; install the fix and verify.

Sources