Nothing gets a gaming session canceled faster than booting your PC after a routine driver update and finding that Windows no longer sees your graphics card at all. The symptom is easy to recognize: Device Manager shows only Microsoft Basic Display Adapter (or a generic “VGA Compatible Controller” with a warning icon), your monitor is running at a locked resolution like 1024×768, GPU monitoring apps such as MSI Afterburner or HWiNFO show no sensor data, and games either refuse to launch or drop to single-digit frame rates. On systems with both integrated and dedicated graphics, the GPU may simply vanish from the display adapter list entirely, with all output running through the iGPU.
The good news: this is one of the most common driver-update failures, and in the vast majority of cases your hardware is perfectly fine. Treat it as urgent only if it appeared alongside artifacts, black screens before the crash, or a recent power event, since those can indicate a hardware fault. Otherwise, work through the fixes below in order. Most readers resolve the issue within 30 to 60 minutes using the first three fixes alone.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Corrupted or partially installed driver | Device Manager shows a yellow warning icon on the GPU or Basic Display Adapter; installer logs in C:\ProgramData\NVIDIA Corporation\Installer2 or C:\AMD show errors | Easy |
| Old driver files conflicting with the new install | Problem started immediately after upgrading from an older driver version; DDU was never used | Easy |
| Windows Update overwrote or blocked the new driver | Device Manager driver date rolls back after a reboot; Event Viewer shows the driver reverted | Easy |
| GPU disabled in Device Manager or BIOS | GPU listed with a down-arrow icon, or missing from BIOS PCIe/peripheral page | Easy |
| PCIe slot or power connection issue | GPU fans don’t spin, no power LED, card loose after recent case work | Moderate |
| Secure Boot or firmware incompatibility with the new driver | Driver install fails with error codes like 43 or 31; occurs mainly on brand-new driver branches | Moderate |
| Failing GPU hardware | Symptoms persist across a clean Windows install and a known-good alternate system | Hard |
Fix 1: Restart and Reseat the Power Cycle
What causes it
Driver installers queue changes that only apply after a full shutdown. A fast-startup reboot can leave the PCIe bus in a stale state where the card enumerates incorrectly.
How to check
If you have not done a full shutdown since installing the driver, this is your first step regardless. Check whether your case or GPU power LEDs are lit.
What to do
Hold Shift and click Shut Down from the Start menu (Shift bypasses Fast Startup), unplug the PSU, flip its switch off, hold the case power button for 15 seconds to drain residual charge, then reconnect and boot. On laptops, shut down, unplug the charger, and if possible hold the power button for 30 seconds with the battery disconnected.
How to undo it
Nothing to undo — this changes nothing permanently. If the GPU still isn’t detected, continue to Fix 2.
Fix 2: Re-enable the GPU in Device Manager
What causes it
Sometimes a driver install fails partway and Windows disables the device, or it was disabled earlier and the new installer can’t initialize it.
How to check
Right-click Start and select Device Manager. Expand Display adapters. Look for a down-arrow icon on your GPU, or an entry with a yellow triangle showing code 22 (“disabled”), 31, or 43.
What to do
Right-click the GPU entry and choose Enable device. If it’s missing entirely, click View in the menu bar and select Show hidden devices, then enable anything grayed out. If you see code 43, right-click the device, choose Properties, and check the Device status box for the exact message before moving on.
How to undo it
Right-click the GPU again and choose Disable device if you ever need to force the system onto integrated graphics.
Fix 3: Roll Back the Driver
What causes it
If detection worked before the update, the new driver package itself may be incompatible with your card or Windows build — a known pattern when brand-new driver branches launch.
How to check
In Device Manager, right-click the GPU, choose Properties, then open the Driver tab. If the Roll Back Driver button is clickable, a previous driver version exists to return to.
What to do
Click Roll Back Driver, select a reason, and let Windows restore the prior package. Reboot and check Device Manager. If the button is grayed out, download the previous driver version manually from the NVIDIA or AMD driver archive, note its version number, and reinstall it after running Fix 4 (DDU) so the broken version is fully removed first.
How to undo it
Simply reinstall the newer driver package when a stable revision is available — roll back and forward are symmetric operations.
Fix 4: Clean Uninstall with DDU (Display Driver Uninstaller)
What causes it
Standard uninstalls leave behind registry keys, service entries, and DLLs in C:\Windows\System32\DriverStore\FileRepository. When the new driver installer encounters these leftovers, it can abort mid-install and leave no working driver at all.
How to check
If you upgraded over an old driver without using DDU and the problem persists after Fixes 1–3, leftover corruption is the most likely cause. Check Device Manager for repeated “ghost” entries under Show hidden devices.
What to do
Download Display Driver Uninstaller from the official Wagnardsoft site, disconnect from the internet (or set your Ethernet/Wi-Fi adapter to disabled in Network Connections) to stop Windows Update from grabbing a driver mid-process, and boot into Safe Mode (hold Shift while clicking Restart, then Troubleshoot → Advanced options → Startup Settings → Restart, then press 4). Run DDU, select your GPU vendor, and click “Clean and restart.” Windows will boot with basic display output. Then install the latest driver fresh; in the NVIDIA installer choose Custom → Perform a clean installation, and on AMD choose the Factory Reset install option.
How to undo it
Reconnect your network adapter and reinstall any vendor extras you removed (GeForce Experience/NVIDIA App or AMD Adrenalin) — the driver itself is what you want to keep.
Fix 5: Stop Windows Update from Replacing the Driver
What causes it
Windows Update aggressively pushes its own WHQL-certified driver packages, which can overwrite your fresh install with an older or mismatched one during the reboot cycle — a frequent complaint in the 2026 driver-branch cycle where OS builds lag behind GPU driver releases.
How to check
After a successful driver install, reboot and check the Driver tab date in Device Manager. If it reverted, Windows Update is interfering. Check Settings → Windows Update → Update history for a driver entry matching your GPU.
What to do
Go to Settings → System → About → Advanced system settings → Hardware tab → Device Installation Settings, click Yes then choose No (“Don’t download drivers from Windows Update”) and Save Changes. On Pro editions you can also use Group Policy Editor (gpedit.msc): Computer Configuration → Administrative Templates → Windows Components → Windows Update → “Do not include drivers with Windows Updates,” set to Enabled. Pause updates for 7 days while you confirm stability.
How to undo it
Set Device Installation Settings back to Yes and the Group Policy entry back to Not Configured once a stable driver is in place.
Fix 6: Check BIOS PCIe Settings and Re-seat the Card
What causes it
A failed install combined with a marginal physical connection can push the card into an undetected state. BIOS settings like primary display output set to iGPU-only, or PCIe link speed forced incorrectly, can also hide the card from Windows.
How to check
Enter BIOS/UEFI (usually Del, F2, or F12 during boot) and look under Advanced → PCI Configuration or the PCIe/peripheral page. If your card isn’t listed there at all, Windows cannot detect it — this is a hardware-level issue. Also check whether GPU fans spin at boot and whether PCIe power cables (6-pin, 8-pin, or 12V-2×6) are fully clicked in at both the GPU and PSU ends.
What to do
Set Initiate Graphic Adapter or Primary Display to PEG/PCIe (not iGPU or Auto). Set PCIe link speed to Auto or Gen5/Gen4 as appropriate for your board. Power down fully, unplug the PSU, press the card’s PCIe retention latch, remove the card, inspect the gold fingers for debris, and re-seat it firmly until the latch clicks. Reconnect all power cables and reboot.
How to undo it
Return BIOS display settings to Auto if you later change your configuration; the physical re-seat needs no undo.
Fix 7: Update the Chipset Driver and BIOS
What causes it
New GPU drivers increasingly rely on current PCIe and power-management code in the motherboard firmware and chipset drivers. An outdated BIOS can fail to hand the card to Windows after a driver reinitialization.
How to check
Open System Information (Win+R, type msinfo32) and note your BaseBoard Product and BIOS Version/Date. Compare against the support page for your motherboard model. For AMD systems, check whether the AMD Chipset Software in Settings → Apps is current.
What to do
Download the latest chipset driver from your motherboard vendor’s support page and install it, rebooting afterward. If a newer BIOS is available, update it using the motherboard’s built-in utility (such as ASUS EZ Flash, MSI M-Flash, or Gigabyte Q-Flash) from a FAT32 USB drive, following the vendor’s instructions exactly and never cutting power mid-flash. Reboot and reinstall the GPU driver if detection still fails.
How to undo it
BIOS updates generally can’t be reversed, but they rarely need to be. Chipset drivers can be rolled back via Device Manager → System devices → Driver tab if a new one misbehaves.
Fix 8: Test the Card in Another System
What causes it
This is the diagnostic step that separates software problems from hardware failure. If the card isn’t detected anywhere, the GPU itself (or its VRAM, power delivery, or PCIe interface) has likely failed.
How to check
Install the GPU in a second known-working PC, or test a different known-good card in your system. Also try a different PCIe slot if your motherboard has one, and swap the PCIe power cables for different ones from your PSU’s native set.
What to do
If the card works in another system, your motherboard slot or PSU is the problem — test the PSU with a wattage meter or substitute unit, and inspect the PCIe slot for bent pins or debris. If the card fails in two systems, contact the manufacturer’s RMA department (ASUS, MSI, Gigabyte, Sapphire, XFX, or whoever built your card) with your proof of purchase; most warranties run 2–3 years.
How to undo it
Return all hardware to its original slots and cabling after testing.
If Nothing Works
If your GPU remains undetected after all eight fixes, the likely culprit is hardware. Before declaring the card dead, try one final software test: install a fresh copy of Windows on a spare drive or use a Windows To Go USB. If the card is still invisible on a clean OS, stop troubleshooting software. For cards under warranty, initiate an RMA. For cards out of warranty, a local repair shop can sometimes reflow or diagnose VRAM faults, though replacement is usually more economical. If you need a working system immediately, temporarily running on integrated graphics will get you basic desktop use and older games while you sort out a replacement.
FAQ
Why did my GPU disappear right after a driver update?
The installer likely failed partway through, leaving no driver bound to the device, or the new package conflicts with leftover files from the previous version. Rolling back (Fix 3) or doing a DDU clean install (Fix 4) resolves this in most cases.
Is it safe to use DDU in Safe Mode?
Yes — that’s exactly how it’s designed to be used. Safe Mode loads only essential drivers, so DDU can remove the GPU driver completely without the display subsystem fighting back. Reconnect your network after rebooting so Windows can fetch any non-GPU updates you paused.
Will a BIOS update fix GPU detection problems?
Sometimes. It’s most likely to help if your motherboard firmware predates your GPU’s generation, or if PCIe link training issues prevent the card from initializing at boot. It’s Fix 7 rather than Fix 1 because it’s riskier and less commonly the cause.
How do I stop this from happening on the next driver update?
Download drivers directly from NVIDIA or AMD rather than relying on Windows Update, disable automatic driver delivery (Fix 5), create a restore point before installing, and use DDU for major version jumps rather than installing over the old driver. Skipping brand-new driver releases for a week or two also lets early adopters surface problems first.
