The hardest part of driver maintenance isn’t installing anything. It’s figuring out which file you’re actually supposed to download in the first place. I’ve watched people spend an hour on a vendor support page, grab the wrong package, and then wonder why Windows throws a “not compatible” error. The driver was fine. The choice was wrong.
Here’s how I track down the right driver, in the order that wastes the least time.
Identify the device before you go looking
You can’t search for a driver until you know the exact hardware. “Realtek audio” isn’t enough. There are dozens of Realtek codecs and they don’t share packages.
Open Device Manager (right-click Start, select Device Manager). Expand the category for your device. Right-click the entry and open Properties, then the Details tab. Change the Property dropdown to Hardware Ids. That first long string is your fingerprint. Copy it into a search engine and you’ll land on the right product far more reliably than guessing from the device name.
For GPUs, the model name is printed clearly and you don’t need the Hardware ID route. But for network adapters, card readers, and audio chips, the ID saves a lot of dead ends.
Go to the source, not a driver aggregator
Microsoft’s own guidance is blunt about this: the manual method “relies on drivers first being downloaded from the device manufacturer’s website.” That’s step one, and it’s the step people skip.
Type your exact model name plus “drivers” into a search engine, then take the link that lands on the manufacturer’s official site. Engadget’s walkthrough of GPU updates describes exactly this approach and notes it works for AMD and Intel cards alike. For NVIDIA, you go to the company’s Driver Updates page and search by product name and series, or use the dropdowns.
What you’re avoiding: third-party sites that repackage installers with bundled software, or hand you a stale build with a version number that looks newer than it is. If a download page has more ads than driver notes, close the tab.
One exception: OEM machines
If you’re on a laptop or pre-built from MSI, ASUS, Dell, HP, Lenovo, or Razer, go to the vendor’s support page first and search your exact model. This matters most for GPUs. OEM BIOSes and driver packages sometimes carry custom hardware IDs that reject the generic vendor driver with a “not compatible” error. MSI, Dell, and Lenovo all warn about this on their support pages.
If the OEM page lists a driver older than about six months, I’ll try the generic vendor driver first, but keep the OEM version downloaded as a fallback.
Match the architecture and Windows version
Every download page asks for this and people click through it carelessly. Get it right:
- Windows version: Windows 10 and Windows 11 drivers are often separate. Some vendors also split 22H2/23H2 builds.
- Architecture: 64-bit (x64) unless you’re on ancient 32-bit hardware. Nearly everything modern is x64, but the dropdown will still offer both.
- Device variant: If your adapter has a “v2” or a different part number, that’s a different download.
Microsoft’s Device Manager instructions stress downloading the driver “that match the version and architecture of Windows.” Cheap to check, expensive to get wrong.
Should you just let Windows Update or a companion app handle it?
Sometimes, yes. Windows Update covers a lot of ground. According to Microsoft, it automatically updates drivers for “network adapters, printers, scanners, and video cards,” and those drivers are “normally recent and up to date.”
But there’s a catch. Windows Update serves stable drivers, and for a GPU that sometimes means the build the vendor shipped six months ago. If you’re chasing a specific game fix, Windows Update won’t get you there. That’s a manual job.
Companion apps split the difference. The NVIDIA App has a Drivers tab. AMD’s Adrenalin software sends you into a separate AMD Install Manager (yes, it’s annoying to have two utilities). Intel’s Graphics Software puts an Install All button front and center. All three handle the download-and-install loop without you touching a file. Pick this route if you want current drivers without hunting.
Manual install through Device Manager
Once the file is on disk, this is the path. It works for any device category, not just GPUs.
- Download the driver and uncompress it if it’s a ZIP. Note where it landed.
- Right-click Start, open Device Manager.
- Expand the category (Printers, Network adapters, Display adapters) and right-click the specific device.
- Select Update driver.
- Choose Browse my computer for drivers.
- Click Browse, point to the folder holding the driver files, and confirm.
- Click Next. Windows installs the driver if it recognizes a newer version.
You may see “The best drivers for your device are already installed.” That message means Windows compared versions and decided nothing needed changing. If you know a newer version exists, you’re probably pointing at the wrong folder, or the installer expects to be run as an .exe instead. Try double-clicking the downloaded executable directly.
When the new driver breaks something
Newer isn’t always better. Engadget notes that a fresh GPU release can cause crashes or performance issues, and that Windows Update has started automatically reverting problematic drivers for that reason. Knowing how to go backward matters as much as knowing how to go forward.
Two ways to roll back:
- Built-in rollback: In Device Manager, open the device’s Properties, go to the Driver tab, and use Roll Back Driver if it’s available. Windows keeps the previous version for a while.
- Manual rollback: Download the older version from the manufacturer’s site and install it the same way you installed the new one. You can also use Update Driver, pick “Browse my computer for drivers,” then “Let me pick from a list of available drivers” to see if an older version is already sitting on your system.
To confirm the rollback worked, check the driver version in Properties and test the device. If you want to dig deeper, Event Viewer will show related errors from the failure window.
Before you touch anything
Create a system restore point. This one habit has saved me more times than any driver tool. It takes thirty seconds and gives you a single button to undo a bad install.
Then, before installing, close overlay and monitoring utilities. MSI Afterburner, RivaTuner, Discord overlay, GPU-Z: quit them. Even rebooting into Safe Mode, several of these leave scheduled tasks and startup entries that can interfere with a clean install. Not every driver needs this, but the ones that go wrong tend to be the ones where you left Afterburner running.
My actual rule for driver updates
Don’t update just because a newer version exists. A working driver you haven’t touched is quieter than a newer one you have. Update when you’re chasing a fix, need a feature, or a security bulletin says so. For everything else, leave it alone.
When you do update: manufacturer’s site, correct architecture, restore point first, close the utilities. That’s the whole process. The search for the right file is the part that trips people up, and the Hardware ID trick is the thing that fixes it.