Every experienced Windows user has a story about an update that killed their WiFi, their audio, or their touchpad overnight. The update itself is fine — the problem is that Windows replaces your manufacturer’s carefully matched drivers with its own generic versions. The fix after the fact is tedious: identify each broken device, find the right driver on the OEM site, install, reboot, repeat.
The smart move is a driver backup before the update. It takes about five minutes, needs no third-party software, and gives you a one-command restore if anything breaks. Think of it as a seatbelt: you hope you never need it, but you always want it on.
Why this happens
- Windows Update overwrites OEM drivers: Microsoft pushes its own driver versions that may lack OEM customizations for audio, touchpads, and hotkeys.
- Feature updates reset the driver stack: Major updates rebuild driver bindings, and devices that worked yesterday can vanish or misbehave today.
- DriverStore gets pruned: Windows removes older driver versions to save space, eliminating your rollback options.
- Clean installs start from zero: If an update goes badly enough to require reinstallation, you lose every driver at once.
- OEM sites reorganize: Finding the exact driver for a three-year-old laptop model gets harder over time as support pages change.
- Third-party driver tools are unreliable: Many “driver backup” utilities bundle adware or fail to capture the full driver package.
- INF-only backups are fragile: Copying files by hand misses the driver store metadata Windows needs for a proper reinstall.
- Rollback windows expire: Windows only keeps the previous driver for a short time; after that, Device Manager’s “Roll Back Driver” button goes gray.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Create a DISM driver backup (the best method)
- Create a folder for the backup, for example
D:\DriverBackupor a USB drive folder. Avoid the system drive if you might reinstall Windows. - Open Terminal as Administrator.
- Run:
dism /online /export-driver /destination:D:\DriverBackup - Wait for the export to complete — DISM walks the entire driver store and copies every third-party driver package. This is the official, Microsoft-supported method, and it captures everything Windows needs for a clean restore.
Fix 2: Verify the backup is complete
- Open the backup folder and confirm it contains many subfolders, each with
.inffiles inside. - Check the total size — a healthy backup is typically hundreds of megabytes to a couple of gigabytes. A tiny backup means the export missed packages.
- Look specifically for your critical drivers: wireless (Intel/Realtek/MediaTek), graphics (NVIDIA/AMD/Intel), audio (Realtek), and chipset folders should all be present.
- Copy the folder to a second location (external drive or cloud storage). A backup that lives only on the drive it protects is half a backup.
Fix 3: Create a matching system restore point
- Open Control Panel → System → System Protection.
- Select your system drive, click Create, and name it something like “Before 24H2 update.”
- This gives you a second safety net: driver backup for surgical restores, restore point for whole-system rollback.
- Confirm System Protection is actually enabled for the drive — it is off by default on many fresh installs.
Fix 4: Document your current driver versions
- Open Device Manager and, for each critical device (display adapter, network adapter, audio), right-click → Properties → Driver tab and note the version and date.
- Save this list in a text file inside the backup folder. After the update, you can compare versions at a glance and spot which drivers Windows changed.
- Pay special attention to the Intel WiFi driver version and your GPU driver, since these break most often.
Fix 5: Pause updates until you are ready
- Go to Settings → Windows Update and use Pause updates for one to two weeks.
- Install the update manually when you have an hour free and your backup is verified — never right before a deadline or a trip.
- Keep the laptop plugged in during the update. Power loss mid-update is one of the few things a driver backup cannot fix.
Fix 6: Restore drivers after a bad update
- After the update, check Device Manager for yellow warnings or missing devices.
- For each broken device, right-click → Update driver → Browse my computer for drivers and point it at your backup folder. Check “Include subfolders.”
- Windows will find the matching INF and reinstall your original driver.
- If several devices broke at once, this per-device method still beats downloading everything again — and it is exactly the skill that also fixes missing network adapters .
Fix 7: Use pnputil for bulk restore of many drivers
- Open Terminal as Administrator.
- Run:
pnputil /add-driver "D:\DriverBackup\*.inf" /subdirs /install - This installs every driver package in the backup at once — useful when an update broke five things simultaneously.
- Reboot and verify in Device Manager. For authoritative background on driver management, the Microsoft Windows support hub documents these tools in detail.
Fix 8: Automate driver backups so you never forget
- Open Notepad and save a file called
backup-drivers.batcontaining:dism /online /export-driver /destination:D:\DriverBackup\%date:~10,4%-%date:~4,2%-%date:~7,2% - Right-click the batch file → Run as administrator whenever you want a timestamped backup — each run creates a dated folder.
- For full automation, open Task Scheduler, create a basic task running monthly, pointing at the batch file with “Run with highest privileges” checked.
- Monthly automated backups mean you always have a recent known-good driver set, not one from two years ago. Pair this habit with the OEM-first reinstall approach used for WiFi adapter repairs and driver problems become minor inconveniences.
Closing
Five minutes with DISM before an update saves hours of driver archaeology after one. Make the backup, verify it, and update with confidence — the worst case is now a two-minute restore instead of a ruined evening.
