Updating drivers on Windows 11 is simple in theory and surprisingly easy to get wrong in practice. The wrong source, the wrong order, or a blind “update everything” sweep can leave you with broken Wi-Fi, silent audio, or a misbehaving GPU. This guide covers the safe method: which drivers to update, where to get them, in what order, and how to recover when something goes sideways.
The golden rule: update with a purpose. A driver update should fix a problem, add a feature you need, or close a security hole — not satisfy an urge for the newest version number. Every driver change is a small risk; take it only when there’s a payoff. And always prepare a way back before you start.
Why this happens
- Drivers go stale: Old drivers develop incompatibilities with new Windows builds and applications.
- Windows Update lags behind: Microsoft’s driver catalog trails chip vendors by months on key drivers.
- Generic drivers lack features: Windows’ built-in drivers cover basics but miss maker-specific tuning.
- Security vulnerabilities: Old drivers occasionally carry security flaws that updates patch.
- New hardware needs new drivers: Added devices need drivers Windows doesn’t include.
- Corruption accumulates: Driver files degrade over time through disk errors and failed updates.
- Conflicting update sources: Mixing Windows Update, maker, and vendor drivers creates version conflicts.
- No recovery plan: Most driver disasters are really “no restore point” disasters.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Prepare a recovery path first
Before touching any driver, create a System Restore point: search “Create a restore point,” select your system drive, and click Create. Note your current driver versions for anything you plan to update (Device Manager, device Properties, Driver tab). Download new drivers before uninstalling old ones — critical for network drivers, where a failed update leaves you offline with no way to download the fix. Our driver backup guide covers saving working drivers for quick restoration.
- Create a System Restore point.
- Record current driver versions for planned updates.
- Download new drivers before removing old ones.
- Keep a phone or second device handy for emergency downloads.
- Know how to boot into Safe Mode before you need it.
Fix 2: Use Windows Update for baseline drivers
Open Settings, Windows Update, and install all available updates, then check Advanced options, Optional updates, Driver updates — Microsoft lists certified driver updates here that are safe to install. This is the right source for obscure hardware (card readers, sensors, fingerprint readers) where the maker’s site is hard to navigate. Let Windows handle the long tail of minor devices; save your manual effort for the drivers that actually matter, as Microsoft’s Windows support pages document for the update process.
- Install all regular Windows Updates first.
- Check Optional updates, Driver updates.
- Install certified drivers for minor hardware.
- Reboot after the batch.
- Verify everything still works before continuing.
Fix 3: Get graphics drivers from the GPU maker
Graphics drivers deserve special treatment — they’re the most impactful and most frequently updated. Use NVIDIA’s download page for GeForce or Intel’s Driver & Support Assistant for Intel graphics (AMD owners should use AMD’s driver support page). Always choose the clean install option to wipe the old driver completely. For laptops, check the maker’s support page first — some models need the tuned maker driver rather than the reference one.
- Identify your exact GPU in Device Manager.
- Download from the GPU maker’s official page.
- Choose clean/custom install, not express.
- Check the laptop maker’s page for tuned variants.
- Reboot and verify with a quick graphics test.
Fix 4: Get network and chipset drivers from the laptop maker
Wi-Fi, Bluetooth, and chipset drivers are the ones most likely to break when sourced wrong. Download these from your laptop manufacturer’s support page for your exact model — Dell , for example; HP and Lenovo offer equivalent per-model downloads. Install chipset first, then network, then Bluetooth, rebooting between major ones. These maker packages include the correct firmware pairings and power profiles that generic drivers miss.
- Download chipset, Wi-Fi, and Bluetooth packages for your model.
- Install the chipset driver first and reboot.
- Install Wi-Fi, then Bluetooth, rebooting after each.
- Verify connectivity before moving on.
- Keep the installers saved for future reinstalls.
Fix 5: Update remaining devices via Device Manager
For anything left — audio, camera, touchpad, card reader — right-click the device in Device Manager and choose “Update driver,” then “Search automatically.” If Windows finds nothing but you know an update exists, use “Browse my computer” and point it at a driver you downloaded from the maker. Don’t force updates on devices that work fine; the automatic search is conservative by design. If a device shows a warning icon, that’s your signal it actually needs attention — see our ELAN touchpad guide for a worked example.
- Right-click the device, Update driver, Search automatically.
- Or browse to a manually downloaded driver.
- Skip devices that already work correctly.
- Prioritize devices showing warning icons.
- Reboot after updating input or audio devices.
Fix 6: Avoid driver updater utilities
Uninstall any third-party “driver booster” or “driver updater” tools — they routinely install wrong drivers, bundle unwanted software, and charge for free updates. The only semi-exceptions are vendor tools like Intel DSA or NVIDIA GeForce Experience, which come from the chip maker itself. If a sketchy updater already ran, check Device Manager for devices with new warning icons and roll back the drivers it changed (Driver tab, Roll Back Driver). Then create that restore point you skipped and do it properly.
- Uninstall third-party driver updater tools.
- Check Device Manager for new warning icons.
- Roll back any drivers the tool changed.
- Use a restore point if rollback isn’t available.
- Stick to maker and vendor sources going forward.
Fix 7: Recover from a bad driver update
If an update breaks something, act quickly: in Device Manager, open the device’s Properties, Driver tab, and click Roll Back Driver. If that’s grayed out, uninstall the device with “Attempt to remove the driver for this device” ticked, then install your saved working version. If Windows won’t boot properly, use Safe Mode (Shift+Restart, Troubleshoot, Startup Settings) and roll back from there. As a last resort, use System Restore to return to the point you created in Fix 1 — this is why you created it.
- Try Roll Back Driver in the device’s Driver tab.
- Or uninstall with driver removed and reinstall the old version.
- Boot into Safe Mode if normal boot is broken.
- Use System Restore as the final fallback.
- Block the bad driver version from reinstalling via Windows Update.
Closing
Safe driver updating is 90% preparation and source discipline: restore point first, maker and vendor sources only, targeted updates with a reason, and a tested way back. Do that and driver updates become routine maintenance instead of Russian roulette. The drivers that matter most — graphics, Wi-Fi, chipset — reward the extra care; everything else can ride along with Windows Update.
