How to Update Drivers Without Breaking Anything

Updated: October 2026

Driver updates are the one kind of patch that can fix a machine and break it the same afternoon. Most guides stop at three clicks in Device Manager and never say what to do when the new driver turns out worse than the one it replaced. This covers both: the fastest safe way to update drivers on one PC, and how to run driver updates across a fleet without losing a week to rollbacks.

TL;DR

• Windows Update first. Settings, Windows Update, Advanced options, Optional updates, Driver updates. It covers most hardware.
• Device Manager for one stubborn device. Right click the device, pick Update driver, then Search automatically.
• OEM site for GPUs and laptops. Vendor releases land well before Windows Update carries them.
• Skip driver updater apps. Security researchers class most of them as scareware.
• Ring your rollouts at fleet scale. Pilot group, deferral window, then everyone else.

What a Driver Update Changes on the Machine

A driver is the translator between Windows and a piece of hardware. Your GPU, your Wi-Fi card, your printer, the trackpad on a laptop: each one ships code that tells the operating system how to talk to it. Most of that code runs in the kernel, with the same privileges as Windows itself. That's why a bad driver doesn't throw a polite error. It takes the whole machine down.

So the reason to update is rarely "newer is better." It's one of three things. A bug you're hitting got fixed. A security flaw got patched, and kernel-level flaws are the ones attackers want most. Or you need a feature that only exists in a newer release, which is mostly a GPU story.

Kernel access is also why drivers are an attack surface and not just a stability risk. Attackers don't need to find a flaw in Windows if they can load a signed driver that already has one, run their code with kernel privileges, and switch off the security tooling from underneath. Microsoft ships a vulnerable driver blocklist for exactly this reason, and keeps adding to it. A driver update that closes one of those holes is worth taking promptly. A driver update that adds nothing but a version number is not.

The reason not to update is simpler. If the hardware works, a driver update is a change with no upside and real downside. Windows Latest reported in August 2026 that drivers were trashing Windows 11 stability more than any other factor, while Windows 10 stayed comparatively quiet. The fix for that isn't updating more often. It's updating on purpose.

How to Update Drivers on Windows 11 and Windows 10

There are four routes, and they don't overlap the way people assume. Pick by what the device is, not by which one you remember.

Windows Update. Open Settings, go to Windows Update, then Advanced options. Under Additional options, click Optional updates and expand Driver updates. Tick what you want and install. On Windows 10 the path is Settings, Update and Security, Windows Update, View optional updates. This is the safest of the four because Microsoft has already signed and staged what appears here.

Device Manager. Press Windows key and X, pick Device Manager, find the device, right click it and choose Update driver, then Search automatically for drivers. If Windows says the best driver is already installed, that's not the end of the road. It means Windows has nothing newer in its own catalog, which is a very different claim from "no newer driver exists."

The manufacturer's site. For a Dell, Lenovo, HP or Framework machine, go to the support page for that exact model, find the downloads section, and pull the chipset, storage and network drivers from there. This is where firmware lives too, and firmware is the piece Windows Update almost never handles.

GPU vendor tools. Graphics drivers move on their own schedule, and Windows Update is usually a release or two behind. NVIDIA, AMD and Intel all ship their own updater apps. These are the exception to the "avoid driver software" rule below, because they come from the company that wrote the driver.

How to Check Which Driver Version You Have

You can't decide whether to update something you haven't looked at. On one machine, Device Manager gives you the answer: right click the device, Properties, Driver tab. You get the version number, the date, and who published it.

The faster route is a command. Open an admin prompt and run pnputil /enum-drivers. That lists every third-party driver package on the machine with its provider, class, version and date, in one pass. In PowerShell, Get-WindowsDriver -Online does the same job and pipes into whatever you're building.

Read the date before the version number. Version strings are vendor-specific and tell you nothing across brands. A date does. A 2019 network driver on a 2024 laptop means the OEM driver set never got applied after imaging, which is a much bigger finding than any single pending update.

While you're in there, deal with anything showing as "Unknown device" or carrying a yellow warning triangle. Open Properties, go to Details, and switch the dropdown to Hardware Ids. That string identifies the chip, which is what you search for when the OEM page has nothing useful under the model name.

Why Driver Updater Apps Are a Bad Deal

Search the phrase and half the page is software that promises to scan your PC and fix every outdated driver at once. Most of it is scareware. The pattern is consistent: a free scan reports dozens of urgent problems, the fix sits behind a subscription, and the "urgent" drivers are mostly current.

Malwarebytes Labs has been documenting this category since 2015 under the heading "digital snake oil," and the mechanics haven't changed. XDA made the same case in 2026, pointing out that the tools charge for something Windows Update already does. The security cost stacks on top. Bundled adware and browser hijackers ride along with the installer, and a tool that fetches unsigned driver binaries from a random mirror is handing kernel access to whoever controls that mirror.

The three exceptions are the GPU vendor apps above, the OEM's own utility (Dell Command Update, Lenovo Vantage, HP Support Assistant), and whatever your RMM or endpoint management platform uses. All three have a named company behind the binary and a support contract attached.

What to Do When a Driver Update Breaks the Machine

This happens often enough to plan for. NVIDIA's GeForce 572.83 release triggered black screens and blue screens on some Windows 11 PCs in 2025, sometimes mid-install, sometimes after the reboot. In 2026 a conflict between Windows 11's USB-C changes and Intel's Innovation Platform Framework driver produced shutdowns, overheating and battery drain on some Dell machines. Later that year, after the August Windows 11 update KB5121003, the studio Embark confirmed the update had broken compatibility with a driver its game depended on.

Work the list in order. Stop as soon as the machine is stable.

1. Roll back the driver. Device Manager, right click the device, Properties, Driver tab, Roll Back Driver. Windows keeps exactly one previous version, so this only works if the update is recent and nothing has cleaned up after it.
2. Uninstall and let Windows fall back. Same Properties dialog, Uninstall Device, and tick "Attempt to remove the driver for this device" if it's offered. Reboot. Windows reinstalls its own generic driver, which is usually stable and usually slower.
3. Boot to Safe Mode if it won't start. Hold Shift while clicking Restart, then Troubleshoot, Advanced options, Startup Settings, Restart, and pick Safe Mode. Drivers load minimally there, which is enough to do step 1 or 2.
4. Use System Restore. If the driver came in with a batch of other changes, a restore point from before the update undoes the lot without touching your files.
5. Block the update from returning. Windows will happily reinstall the driver it just broke you with. On a single machine, Microsoft's "Show or hide updates" troubleshooter hides it. On managed machines, pause or decline the driver in your update policy instead.

Step 5 is the one people skip, and it's the one that turns a single bad afternoon into a recurring one.

Windows Can Now Pull a Bad Driver Back on Its Own

Microsoft announced Cloud-Initiated Driver Recovery on 13 May 2026. It lets Microsoft remotely replace a problematic Windows Update driver with a previously approved working version on affected PCs, without a technician touching the machine. The pilot ran from April to September 2026, with wider enforcement planned for Q4 2026 into Q1 2027.

It's a good safety net and a poor plan. It only covers drivers that came through Windows Update, which leaves out everything you pulled from an OEM site or a GPU vendor app. It fires on Microsoft's timeline, not yours. And by the time it reaches a machine, the user has already called you.

How to Update Drivers Across a Whole Fleet

Everything above assumes one PC in front of you. At fifty machines the calculus flips: the cost isn't the update, it's the variance. Twelve laptop models, four GPU generations, and a driver that's fine on eleven of them.

Microsoft Intune handles this through Windows driver update policies. You get a list of available driver updates for the devices you target, and you approve or pause each one before it goes anywhere. Approval can be automatic or manual. The pattern that works is deferral-based rings: several policies with different deferral periods, so a pilot group takes the driver first and the rest of the fleet follows a week or two later. Two constraints to know going in. A device can only sit in one driver policy, and the feature needs a Windows license carrying the Autopatch entitlement. Driver updates also aren't supported during Autopilot provisioning.

Reporting is the part worth checking before you commit to a tool. You want to see, per model, which driver version is deployed, which machines are behind, and which approvals are sitting in a pending state that nobody has looked at in three weeks. Driver update tooling that shows you a queue but not a compliance state leaves you guessing about the fleet you already have.

If your fleet is mixed, or you're an MSP running twenty client tenants, the RMM side of the house usually carries this instead. Driver approvals become part of the same patch policy that handles Windows and third-party apps: stage, pilot, schedule, report. Our patch management software roundup covers which platforms do driver approvals properly and which treat them as an afterthought, and unified endpoint management explains how driver state fits alongside the rest of the endpoint picture.

A Driver Policy That Survives Contact With Real Users

Whatever tool you use, the policy is what keeps this boring. Six things to settle before you turn anything on:

• Inventory by model, not by machine count. You're managing eleven hardware profiles, not four hundred endpoints.
• Keep a pilot ring of ten to twenty machines that includes at least one of every model, and put a technician's own laptop in it.
• Defer seven to fourteen days between the pilot ring and general release. Most bad drivers surface inside a week.
• Never auto-approve graphics, storage or chipset drivers. Those three cause the boot failures. Everything else can ride the automatic path.
• Pin a known-good version per model and write it down somewhere your whole team can reach at 2am.
• Write the rollback runbook before you need it. Steps 1 to 5 above, with your tool's specific clicks filled in.

None of this is exotic. It's the same staged-rollout discipline you already apply to Windows patches, pointed at the class of update most likely to take a machine offline.

The cadence question comes up constantly, and there isn't a calendar answer. Graphics drivers on machines doing graphics work get looked at monthly. Security-flagged drivers get handled on the same clock as any other security patch. Everything else can sit on a quarterly review where you check dates, catch the machines that drifted, and leave the working ones alone. Chasing every release is how you end up rolling back more often than you roll forward.

Where OpenFrame Fits

OpenFrame is an AI-native all-in-one MSP and IT platform, built for MSPs and for in-house IT teams running their own fleets. Endpoint management, patching including driver approvals, and native PSA sit in one place rather than three tools that each hold a third of the story. PSA is included, not a roadmap item.

That matters for driver work specifically, because a driver rollback is three jobs in most stacks: spot it in the RMM, roll it back on the endpoint, close the ticket in a separate PSA. When those live together, the AI agents can see the whole sequence, which is the difference between a suggestion and something that closes the loop. Pricing is built to stay affordable, and there's no lock-in on the way out. If you're weighing platforms on this, our endpoint management software guide lays out the field including where OpenFrame fits and where it doesn't.

Update Drivers Like a Patch, Not Like a Chore

The instinct most people have about drivers is backwards. They ignore them for two years, then update everything at once when something breaks, which is the worst possible time to introduce fifteen simultaneous changes to kernel-level code.

Treat a driver like any other patch. Know what's installed. Update it for a reason you can name. Stage it before it reaches everyone. Keep the way back open.

Do that and driver updates stop being the thing that ruins a Thursday.