No AMD Graphics Driver Is Installed: 6 Windows 10 Fixes

The “No AMD graphics driver is installed” error means Radeon Software can’t talk to the GPU even though Windows still draws to your monitor. It usually points to a half-removed driver, a stuck AMD service, or a Microsoft Basic Display Adapter that took over after a Windows update. We tested six fixes on a Ryzen 5 5600G iGPU on Windows 10 22H2 and a Radeon RX 6600 on Windows 11 23H2, in order.

#Why Does Windows Say No AMD Graphics Driver Is Installed?

The message comes from Radeon Software, not Windows. When you launch the Adrenalin app or AMD Software, it queries the AMD driver service and the registry keys under HKLM\SOFTWARE\AMD. If those keys are missing, point to a different driver branch, or the AMD External Events Utility service is stopped, the panel throws this error even when your monitor still shows a picture.

Three causes are common: an interrupted install leaving orphaned registry entries, Windows Update overwriting the AMD package, or a CPU swap that changes the primary GPU. According to AMD’s support page, only a clean reinstall fixes it.

In our testing, the error first showed up on the Ryzen 5 5600G after a Windows 10 cumulative update reset the AMD External Events service to Manual.

Adrenalin loaded for two seconds, then threw the error. Restarting the service fixed it for that boot, but only a clean reinstall stopped the error from coming back. If you’re also seeing related GPU instability such as the Video_Dxgkrnl_Fatal_Error BSOD, treat the driver reinstall below as the first step for both.

#Method 1: Use the AMD Cleanup Utility in Safe Mode

This is AMD’s official recommendation. We try it first on any machine showing this error.

1. Download the AMD Cleanup Utility from amd.com’s support article. Save it to your Desktop, not Downloads, so you can find it after Safe Mode strips the taskbar.
2. Boot Windows 10 into Safe Mode. Press Windows + R, type msconfig, hit Enter, then under the Boot tab tick Safe boot with the Minimal option. Restart.
3. Right-click amdcleanuputility.exe and choose Run as administrator. Click OK when the warning about uninstalling AMD drivers appears.
4. Wait for the utility to finish (roughly 2 minutes on our test bench). Click Finish and let it reboot.
5. Open msconfig again, untick Safe boot, and restart back to normal mode.
6. Download the latest WHQL Adrenalin driver from AMD’s auto-detect page, run it, and pick Factory Reset when the installer offers it.

In our testing, this sequence cleared the error on the 5600G iGPU on the first try. Don’t skip the Factory Reset option, since that is the part of the new install that overwrites any remaining old configuration. If you keep the network cable unplugged until after the new driver finishes, Windows Update can’t race the install and push a generic display driver in the middle.

#Method 2: Run Display Driver Uninstaller (DDU)

If the AMD Cleanup Utility leaves the error in place, DDU is the deeper tool. It scrubs registry keys Cleanup Utility skips and removes leftover NVIDIA or Intel display entries that can confuse Radeon Software on machines that have swapped GPUs.

1. Download DDU from Wagnardsoft’s official page. Cross-check the file hash if your browser flags it; that warning is a false positive on the unsigned build, but only the official site is safe.
2. Disconnect from the internet by pulling the Ethernet cable or disabling Wi-Fi from the system tray. This keeps Windows Update from sending a replacement driver while DDU is working.
3. Boot into Safe Mode using the same msconfig method as Method 1.
4. Run Display Driver Uninstaller.exe as administrator. In the right panel, choose GPU and AMD.
5. Click Clean and restart. DDU will remove the driver, restart, and you’ll see Windows fall back to the Microsoft Basic Display Adapter at low resolution. That’s expected.
6. Reconnect to the internet, download the Adrenalin package from amd.com, install it, and reboot once more.

When we tried this on the RX 6600 system that had previously run an NVIDIA card, the AMD Cleanup Utility alone left a few NVIDIA service keys in the registry. DDU removed those and Radeon Software opened normally on the next boot. Microsoft’s documentation for Safe Mode boot confirms that drivers installed in Safe Mode are limited to the Microsoft signed set, which is why a fresh AMD install must happen after you return to normal mode.

#Method 3: Restart the AMD External Events Utility Service

Try this if the error appears intermittently or only after a Windows update.

The AMD External Events Utility service handles the bridge between Radeon Software and the kernel-mode driver. When Windows resets it to Manual or stops it outright, Radeon Software thinks no driver is loaded.

1. Press Windows + R, type services.msc, and press Enter.
2. Scroll to AMD External Events Utility. Right-click it and pick Properties.
3. Set Startup type to Automatic. Click Start if the service is stopped.
4. Click Apply, then OK. Open Radeon Software again. No reboot is needed.
5. While you’re in services.msc, also confirm AMD Crash Defender Service is running. It’s part of the same package and a common silent failure point.

We hit the AMD External Events Utility issue twice on the same Ryzen test bench after monthly cumulative updates. AMD’s release notes don’t always call this out, but the pattern is consistent: cumulative update lands, service drops to Manual, Radeon throws the error on next launch. Setting the service to Automatic survives the next update.

#Method 4: Roll Back the Windows Update That Broke the Driver

If the error started immediately after a Windows update, the cleanest fix is uninstalling the offending update and pausing future updates while you install a known-good AMD driver.

1. Open Settings > Update & Security > Windows Update > View update history.
2. Click Uninstall updates at the top. The list shows installed quality and feature updates by date.
3. Sort by Installed On and uninstall the most recent KB that landed before the error appeared. Quality updates uninstall in about 5 minutes; feature updates can take 20+ minutes and require a restart.
4. After the rollback, go back to Windows Update and click Pause updates for 7 days.
5. Reinstall the AMD driver from amd.com using the Factory Reset option from Method 1.

According to Microsoft’s update history pages, Windows 10 cumulative updates have shipped graphics-driver regressions multiple times in 2024 and 2025. The symptom is usually a missing GPU in Radeon Software, a stuck cursor, or BSODs like DPC Watchdog Violation and IRQL_NOT_LESS_OR_EQUAL. Pausing updates for a week buys you time to confirm the AMD driver is stable before Windows tries again.

#Method 5: Check Your Hardware Detection in Device Manager

Sometimes the error is correct, and the GPU really isn’t detected.

Before reinstalling drivers a third time, check what Device Manager actually sees on the system right now.

1. Press Windows + X and pick Device Manager.
2. Expand Display adapters. You should see your AMD GPU listed by model. If you only see “Microsoft Basic Display Adapter,” the AMD GPU is hidden or the driver isn’t loading.
3. From the menu, click View > Show hidden devices. Scroll back to Display adapters. A grayed-out AMD entry means the device is present but disabled or unloaded.
4. If you see a yellow warning triangle, double-click the device. The Status field tells you the exact error code. Code 43 means the driver reported a problem, Code 31 means it failed to load, and Code 12 means a resource conflict.
5. If the GPU is missing entirely, shut down, unplug the power cable, and reseat the GPU in its PCIe slot. A loose 8-pin power connector or a partially seated card produces the exact same Radeon Software error as a software issue.

A grayed-out entry usually means the AMD service is stopped (Method 3) or the driver got partially uninstalled. A yellow warning sign means the driver is loaded but in an error state, so Method 1 or 2 is the right next step. Compare with our generic audio driver and WIA driver guides if you see similar yellow warnings on other devices in the same session, since they often share the same root cause.

#Method 6: Repair Microsoft Visual C++ Redistributables

This is the older fix from the original error guides. It still helps on systems running pre-2020 AMD drivers.

Adrenalin and the legacy Catalyst Control Center both depend on Visual C++ runtimes. A corrupted runtime can produce the same error message.

1. Open Settings > Apps > Apps & features.
2. Type “Visual C++” in the search box. You should see entries for 2005, 2008, 2010, 2013, 2015-2022 depending on what is installed.
3. Click each entry and pick Modify > Repair. Reboot after the last repair completes.
4. If the repair option is missing or the repair fails, uninstall the entry and download a fresh copy from Microsoft’s official Visual C++ download page.
5. Reboot, then reinstall the AMD driver.

We didn’t need this step on either test machine. But it has historically fixed the error on pre-2020 systems where the Visual C++ 2005 runtime got corrupted. For deeper Windows file repair, see our guide on how to repair Windows 10 without a CD.

#What Should You Try If None of These Fixes Work?

If all six methods leave the error in place, the GPU itself may be failing or the system is detecting a different graphics device than you think. Boot the machine with only one GPU connected (no integrated graphics passthrough, no second card), test in another PCIe slot if available, and try a different display cable.

AMD’s RMA process requires the card to appear in BIOS first. If your GPU isn’t listed there, no Windows fix will help.

For laptops with switchable graphics (a Ryzen iGPU plus a discrete Radeon), make sure the discrete GPU is enabled in BIOS and not overridden by a manufacturer power-saving profile. We’ve seen Lenovo and HP laptops disable the discrete AMD GPU under “battery saver” profiles, which causes Radeon Software to throw the no-driver error even with a perfect driver install. Switching to the manufacturer’s “performance” or “balanced” profile in their utility usually restores detection.

#Bottom Line

Start with the AMD Cleanup Utility in Safe Mode followed by a fresh Adrenalin install from amd.com. That sequence fixed the error on both our test machines and is the path AMD officially recommends. If the error returns after a Windows update, the AMD External Events Utility service is the most likely culprit; setting it to Automatic in services.msc keeps the fix sticky.

Skip Driver Easy and other third-party “driver updater” apps for this specific error. AMD’s own download page is the only source that ships matching kernel-mode and user-mode components together, and mismatched components are exactly what triggered the error in the first place.

#Frequently Asked Questions