How to Clean Install GPU Drivers with DDU (Step-by-Step 2026) | GamerHardware

To clean install GPU drivers with DDU, boot into Windows Safe Mode, run Display Driver Uninstaller to strip every trace of your old graphics driver, then install fresh drivers with a clean slate. This process fixes black screens, game crashes, stuttering, and performance drops that a normal driver update leaves behind – because Windows never fully removes old driver files on its own. For a broader overview, see the full PC gaming troubleshooting guide.

A standard driver update through GeForce Experience or AMD Adrenalin installs new files on top of old ones. Registry entries, leftover shader caches, and orphaned DLL files from previous versions stay on your system. Over time – especially after switching from AMD to NVIDIA or vice versa – this debris causes real problems. DDU (Display Driver Uninstaller) is a free tool by Wagnardsoft that scrubs all of it.

This guide walks through the full process for both NVIDIA and AMD GPUs on Windows 10 and Windows 11, including when you actually need DDU versus when a regular update is fine.

What DDU Does (and Why Windows Can’t Do It)

Windows has a built-in “Add or Remove Programs” option for graphics drivers. It does not work. When you uninstall NVIDIA or AMD drivers through Windows, it leaves behind registry keys, shader cache folders, Vulkan runtime entries, and old driver store packages. These leftovers cause conflicts when you install new drivers on top.

DDU (Display Driver Uninstaller) is a free tool maintained by Wagnardsoft that removes everything. It cleans the driver store, wipes registry entries, deletes leftover folders in Program Files, clears the shader cache, and removes scheduled tasks that the driver software created. It does all of this while running in Safe Mode so Windows can’t reload driver files mid-cleanup.

What DDU Removes That Windows Doesn’t

The shader cache point matters more than most people think. NVIDIA and AMD both store compiled shaders in your AppData folder. When these get corrupted or contain data from an older driver version, you get stuttering in games – especially during the first few minutes of a session while the GPU recompiles shaders.

Before You Start: Checklist

Spend five minutes preparing before you boot into Safe Mode. Once you’re in Safe Mode, you won’t have internet access (DDU disables it by default), so you need everything downloaded first.

Download These Three Things

1. DDU itself – Download from Wagnardsoft’s official site. Always get DDU from the official source. Third-party download sites bundle adware.
2. Your new GPU driver – For NVIDIA, go to nvidia.com/drivers. For AMD, go to amd.com/support. For Intel Arc, go to intel.com/download-center. Always use the manual product search – never the auto-detect tool. Auto-detect serves the wrong SKU more often than it serves the right one on mixed-GPU or laptop systems.
3. Extract DDU – DDU comes as a self-extracting 7-zip archive. Run it and extract to a folder on your desktop. Do not run it yet.

Which DDU Version You Need

DDU 18.1.5.2 (April 2026) is the current stable release. Earlier versions miss Windows 11 24H2 driver paths and fail to remove the NVIDIA App and FrameView SDK cleanly. Check the version in DDU’s top-right corner before running. If you downloaded DDU months ago, grab a fresh copy – Wagnardsoft ships updates every 6-8 weeks to track new driver packages.

Add DDU to Your Antivirus Exclusions

Windows Defender, Malwarebytes, and most third-party AV tools flag DDU as a potentially unwanted program (PUP) because it modifies the driver store. This isn’t a false positive you can ignore – real-time scanning blocks DDU mid-clean and leaves your driver state half-removed. Add the DDU folder to your AV exclusions list before running. In Windows Security, go to Virus & threat protection > Manage settings > Add or remove exclusions > Add an exclusion > Folder.

Do Not Run DDU from OneDrive or a Synced Folder

Extract DDU to a plain local folder – your Desktop, Downloads, or a dedicated C:DDU path. Running DDU from OneDrive, Dropbox, Google Drive, or any cloud-synced location causes file-lock errors mid-clean because the sync client holds handles on the executable. Network drives fail the same way.

Laptop or OEM Desktop Owners: Use the Vendor Driver

If your machine is an MSI, ASUS, Dell, HP, Lenovo, Razer, or other OEM laptop (or a pre-built desktop with custom GPU hardware IDs), skip the generic NVIDIA or AMD download. Go to your laptop vendor’s support page, search your exact model, and grab their validated GPU driver. OEM BIOSes and driver packages sometimes contain custom hardware IDs that reject generic vendor drivers with a “not compatible” error. MSI, Dell, and Lenovo explicitly warn about this. If the OEM page lists a driver older than six months, try the generic vendor driver first – but keep the OEM version on hand as a fallback.

Close These Programs Before Running DDU

Quit every overlay, monitoring, and GPU utility before you reboot into Safe Mode. Even if Safe Mode won’t load them, several leave scheduled tasks or startup entries that interfere with the new driver install. Close and disable startup for:

• MSI Afterburner and RivaTuner Statistics Server (RTSS) – hooks persist across Safe Mode
• EVGA Precision X1 – installs its own overlay that conflicts with fresh NVIDIA drivers
• NZXT CAM, ASUS Armoury Crate, Razer Synapse – these call GPU APIs during boot
• Discord, Steam, and GeForce Experience overlays – disable in each app’s settings before reboot
• OBS, Streamlabs, and any recording software

Optional But Smart: Create a Restore Point

Type “Create a restore point” in the Windows search bar, click the result, select your system drive, and click “Create.” Name it something like “Before DDU.” If anything goes wrong, you have an instant rollback option. This takes 30 seconds and has saved plenty of people from headaches. For extra safety on a work machine, create a full system image through Control Panel > Backup and Restore (Windows 7) – it still works in Windows 11.

Step-by-Step: Clean Install with DDU

The full process takes about 15-20 minutes. Most of that is waiting for Windows to boot in and out of Safe Mode.

Step 1: Boot into Safe Mode

Windows normally loads GPU drivers at boot. If the driver is loaded, DDU can’t fully remove it – the OS holds file locks on active drivers. Safe Mode loads a basic Microsoft display adapter instead, giving DDU unrestricted access to every NVIDIA, AMD, or Intel file. Your screen will look terrible in Safe Mode: low resolution, no scaling, basic colors. That’s normal and means the GPU driver is not loaded, which is exactly what you want.

There are two reliable ways to reach Safe Mode. Method A works on most systems. Method B is the fallback when Method A hangs or the Startup Settings menu refuses to load, which happens more often on Windows 11 24H2.

Method A: Shift + Restart

Open the Start Menu, hold Shift, and click Restart. This opens Windows Recovery Environment. Navigate to Troubleshoot > Advanced Options > Startup Settings > Restart. When the blue Startup Settings screen appears, press 4 or F4 for “Enable Safe Mode” (without networking). Press 5 or F5 only if you need networking – for DDU, you don’t.

Method B: msconfig (More Reliable on Windows 11)

If Method A fails or loops back to the lock screen, use msconfig instead. Press Win+R, type msconfig, and hit Enter. Go to the Boot tab, check Safe boot, select Minimal, click OK, and restart. Windows will boot directly into Safe Mode. After you finish DDU and restart, open msconfig again and uncheck Safe boot – otherwise Windows will keep booting into Safe Mode every time. This route avoids the Startup Settings menu entirely and sidesteps the WinRE keyboard/mouse bug that occasionally hits Windows 11 24H2 installs.

Windows 11 24H2: Your PIN Will Not Work in Safe Mode

Windows 11 24H2 changed how Safe Mode handles Windows Hello credentials. Your PIN fails silently – you type it in and get returned to the login screen with no error. You must sign in with your full Microsoft account password instead. Before you reboot, go to account.microsoft.com on your phone and confirm you remember your password. If you only know your PIN, reset your password first. Users who forget this step get locked out of Safe Mode and have to use the bcdedit fallback (see the “Stuck in Safe Mode?” section later).

BitLocker: Have Your Recovery Key Ready

If your system drive is encrypted with BitLocker (most Windows 11 Pro and business laptops ship with it on by default), Safe Mode may prompt for your 48-digit BitLocker recovery key. Your normal password won’t unlock the drive in Safe Mode. Before you reboot, sign in to account.microsoft.com/devices/recoverykey or your work/school account portal and copy the recovery key to your phone or a printed page. Without it, you cannot reach the DDU download you just saved to your encrypted drive.

Step 2: Run DDU

Navigate to the folder where you extracted DDU and run Display Driver Uninstaller.exe. If Windows SmartScreen pops up, click “More info” then “Run anyway.” DDU is safe – it’s been the standard driver removal tool since 2012.

When DDU opens, you’ll see three things that matter:

• Device type dropdown (top right) – select “GPU”
• Device dropdown (below it) – select “NVIDIA” or “AMD” depending on what you’re removing
• Three buttons on the left – “Clean and restart”, “Clean and do NOT restart”, and “Clean and shutdown”

Step 3: Choose Your Clean Option

DDU’s left-side panel shows three distinct buttons, and each maps to a different scenario. Pick wrong and you either wait an extra reboot cycle or boot into a dead display with no GPU at all. Use this as your decision guide:

Clean and Restart (Same Card, Most Cases)

This is the default choice for 90% of users. Use it when you’re keeping the same physical GPU and just want a fresh driver install – fixing crashes, resolving a bad update, or doing annual maintenance. DDU removes everything, restarts Windows, and drops you at the desktop with the Microsoft Basic Display Adapter loaded. You then run the new driver installer normally.

Clean and Shutdown (When You Are Physically Swapping GPUs)

Pick this when you’re replacing the GPU in your case – upgrading from an RTX 3060 to an RTX 5070, swapping an old Radeon for a new one, or moving from iGPU to discrete. DDU cleans, then powers the system off. Swap the card while the PC is off, boot back up, and Windows will use the Microsoft Basic Display Adapter until you install the new GPU’s driver. This prevents the old driver from briefly loading against a card it doesn’t match, which can cause installer errors or bootloop on some AMD boards.

Clean and Do NOT Restart (Multi-Vendor Cleanup)

Use this when you’re switching brands – AMD to NVIDIA or vice versa – and need to clean both vendors’ leftovers before reboot. After DDU finishes the first brand, change the device dropdown to the other brand and run it again. Only then restart. You can also use this option if you want to manually run the AMD Cleanup Utility or NVCleanstall after DDU before rebooting. For normal single-GPU maintenance, ignore this button.

DDU shows a log of everything it removed. On a system with years of driver updates, this list gets long – registry keys, file paths, services all scroll by. Let it finish completely before doing anything. Interrupting DDU mid-clean leaves the driver state half-removed and forces you to start over.

Step 4: Install Fresh Drivers

After your PC restarts into normal Windows, your display will be running the basic Microsoft adapter at low resolution. This is expected. Run the driver installer you downloaded earlier.

For NVIDIA: Run the installer, select “Custom (Advanced)” and check the box for “Perform a clean installation.” Yes, even after DDU. This tells the NVIDIA installer to write fresh settings files instead of inheriting any remaining preferences. Install only the driver and PhysX. Skip GeForce Experience unless you specifically need ShadowPlay – it adds background processes that consume resources.

For AMD: Run the Adrenalin installer and choose “Full Install” or “Minimal Install.” Full includes Adrenalin Software (AMD’s control panel). Minimal installs just the driver. If you had performance issues before, start with Minimal – you can always install Adrenalin later. AMD’s installer doesn’t have a “clean install” checkbox since you already cleaned with DDU.

Step 5: Restart and Verify

Restart your PC one more time after the driver installs. A clean reboot after driver install catches edge cases where the driver loaded partially on first boot. Then run through the verification checklist below before you celebrate.

Verify in Device Manager

Open Device Manager (Win+X, click Device Manager) and expand Display adapters. You should see your GPU listed by its full name – “NVIDIA GeForce RTX 4070”, “AMD Radeon RX 7800 XT”, “Intel Arc A770” – with no yellow warning triangle. A yellow triangle with “Code 43” means the driver installed but the GPU rejected it (usually a DCH vs Standard mismatch, covered later). If you see “Microsoft Basic Display Adapter” here, the driver install failed and you need to re-run the installer.

Double-click the GPU entry and check the Driver tab. The Driver Provider should be NVIDIA, AMD, or Intel – not Microsoft. The Driver Version should match what you downloaded. For a second confirmation, press Win+R and run dxdiag. The Display tab shows the driver version, VRAM, and WDDM version – all three should match your GPU and the new driver. GPU-Z (free, from TechPowerUp) gives you an even cleaner readout with clocks, memory type, and BIOS version.

Restore Your Display Settings

DDU wipes your display configuration along with the driver, so your monitor boots at default refresh rate and HDR off. Walk through this list to get back to where you were:

• Refresh rate – Settings > System > Display > Advanced display > Choose a refresh rate. Pick your monitor’s max (144 Hz, 165 Hz, 240 Hz, etc.). This defaults to 60 Hz after a clean install.
• G-Sync or FreeSync – In NVIDIA Control Panel, go to Display > Set up G-SYNC and re-enable it. In AMD Adrenalin, Gaming > Display > AMD FreeSync. These reset to off after DDU.
• HDR – Settings > System > Display > HDR. Enable per-monitor. Windows 11 also has a “Use HDR” shortcut (Win+Alt+B).
• ICC color profile – If you ran a calibrator (X-Rite i1, ColorChecker, or similar), re-apply the profile. Settings > System > Display > Color profile > Add, point to your saved .icc file.
• Multi-monitor arrangement – Desktop right-click > Display settings > drag monitors to match your physical setup. DDU forgets this.
• NVIDIA/AMD per-game profiles – If you used NVIDIA Profile Inspector or AMD’s per-game settings, those are gone. Re-create them as needed.

Finally, launch a game. Check for the issue that prompted the clean install. Stuttering should be gone. Crashes should stop. If the original problem is still present after all of this, the issue isn’t driver corruption – jump to the troubleshooting section.

NVIDIA vs AMD vs Intel (Arc / iGPU)

The DDU process is identical for all three vendors. The differences show up during the fresh driver installation – installer options, companion software, and per-brand quirks that bite users who copy instructions from a different vendor’s guide.

NVIDIA-Specific Tips

NVIDIA bundles GeForce Experience (now being retired in favor of the NVIDIA App), HD Audio driver, PhysX, FrameView SDK, and the NVIDIA Control Panel in one installer. You don’t need all of these. At the Custom installation screen, uncheck everything except Graphics Driver and PhysX System Software (low overhead, some older games still require it).

Skip GeForce Experience unless you specifically use ShadowPlay for recording. GFE runs background services, pushes notifications about “Game Ready” drivers, and uses about 300-400 MB of RAM at idle. The NVIDIA App is its replacement and is worth installing if you want automatic driver updates after your clean install is done. The NVIDIA Control Panel installs separately through the Microsoft Store on Windows 10/11 – the installer’s version is the legacy one.

After installing, open NVIDIA Control Panel and set “Power management mode” to “Prefer maximum performance” for your games. DDU resets this to the default “Optimal power” setting, which can cause clock speed fluctuations during gameplay.

Express vs Custom (Advanced): Which to Pick

NVIDIA’s installer opens with two options. Express is the default and installs every component – driver, GFE/NVIDIA App, audio driver, PhysX, FrameView, USBC driver. Custom (Advanced) lets you pick and forces a “Perform a clean installation” checkbox you can enable.

The short version: after DDU, always pick Custom and always check “Perform a clean installation.” The checkbox forces NVIDIA to write fresh settings files instead of inheriting any preference fragments DDU missed. Express rarely gives you anything extra worth the tradeoff in control.

Game Ready vs Studio Drivers

NVIDIA ships two driver branches from the same download page. Game Ready drivers (GRD) update on day-one with new game launches and carry the latest optimizations. Studio drivers (SD) are certified for creative apps (DaVinci Resolve, Blender, Adobe), get fewer updates, and skip the day-one game tuning. Pick Game Ready if you game and occasionally do content creation. Pick Studio only if you do professional creative work full-time and value stability over frame-rate optimizations. Both use the same underlying driver – the difference is release cadence and which workloads got extra QA testing.

DCH vs Standard Driver Type: Check Before Installing

NVIDIA publishes two driver package formats. DCH (Declarative, Componentized, Hardware support apps) is Microsoft’s newer driver model and the default for Windows 10 1809+. Standard is the legacy monolithic package and is no longer offered for modern consumer cards. You cannot install DCH over Standard or vice versa – the installer refuses with “The driver is not compatible.” DDU usually cleans both types, but on older systems that upgraded from Windows 7/8 you can end up with a Standard driver leftover that blocks DCH installs.

To check which type you have: open NVIDIA Control Panel > Help > System Information. The Driver Type field reads either “Standard” or “DCH.” If you get an “incompatible” error after DDU, re-run DDU and check the “Remove old registry” option under DDU Settings. That catches Standard-era registry keys that survive a normal clean.

AMD-Specific Tips

AMD Adrenalin Software has a built-in “Factory Reset” option. Do not use this as a substitute for DDU. AMD’s Factory Reset only removes what AMD installed – it misses orphaned registry keys, third-party overlay hooks, and Vulkan runtime fragments. DDU goes deeper.

After a DDU clean install, AMD’s driver tends to re-enable several features you might want off:

• Radeon Anti-Lag – on by default, can cause input delay in some games (the opposite of what it claims). Test with it off first.
• AMD Chill – frame rate limiter that aggressively drops FPS when you’re idle in-game. Annoying in menus.
• Enhanced Sync – causes black screens on some monitor combinations. Leave it off unless you’ve confirmed it works with your panel.

Full Install vs Minimal Install

AMD’s Adrenalin installer asks whether you want a Full Install or a Minimal Install after DDU. The difference matters more than NVIDIA’s equivalent:

Start with Minimal Install if you just did DDU because of crashes – Adrenalin’s overlay is responsible for a meaningful share of “driver” crashes that aren’t actually the driver. You can install the full Adrenalin Software later by re-running the installer and picking Full. Unlike NVIDIA’s clean-install checkbox, AMD’s installer has no such box because DDU already did that job.

Ryzen Users: Install Chipset Drivers First

If your CPU is Ryzen (any generation), install the AMD Chipset Drivers before the GPU driver – not after. The chipset package sets up power states, PCIe enumeration, and the AMD Platform Security Processor driver that the GPU driver expects to find. Install in this order after DDU finishes:

1. Download the latest chipset package from amd.com/support/chipsets matching your motherboard chipset (X670, B650, X670E, B850, etc.)
2. Run the chipset installer, reboot
3. Then install the GPU driver (Adrenalin)
4. Reboot one more time

Skipping the chipset step is a common cause of “AMD driver installed fine, but games still crash” complaints on Ryzen builds. Intel CPU users can ignore this.

Intel Arc / iGPU-Specific Tips

Intel’s graphics story has two separate tracks: Arc discrete cards (A380, A580, A750, A770, B580, B770) and the integrated GPU in 11th-gen-and-newer Intel CPUs (UHD Graphics, Iris Xe, or Arc Graphics on Meteor Lake / Arrow Lake). Both use the same driver package, downloaded from Intel’s Download Center.

DDU handles Intel drivers the same as NVIDIA or AMD. In the device dropdown after selecting GPU, choose “Intel” as the vendor. If your system has both an Intel iGPU and a discrete NVIDIA or AMD card (common on laptops), DDU has a “Clean all GPUs” option that wipes every vendor at once – use that instead of running DDU three separate times.

For install: run the Intel Graphics Driver .exe from Intel’s site. There’s no Custom/Express split – Intel uses a single installer flow. After install, Intel Graphics Command Center is optional and available through the Microsoft Store. Intel Arc Control (the overlay + streaming tool for Arc discrete cards) installs as a separate download. Unlike NVIDIA Control Panel, there’s no performance mode switch – Intel handles power management through Windows power plans.

One gotcha: laptops with Arc Graphics (Meteor Lake / Arrow Lake) sometimes need the OEM-packaged driver instead of Intel’s generic one. Dell XPS, ASUS Zenbook, and HP Spectre laptops in particular reject the generic Intel driver on newer models. Check your laptop vendor’s support page first.

Common Mistakes People Make

After helping hundreds of users troubleshoot driver issues across forums and community boards, these are the mistakes that come up repeatedly.

Running DDU Without Safe Mode

This is the most frequent mistake. DDU technically runs in normal Windows, and it even shows a warning when you do it. But running DDU outside Safe Mode means Windows still has driver files loaded and locked. DDU can’t delete locked files. The result is a partial removal that causes more problems than the original issue. Always boot Safe Mode first.

Downloading DDU from Random Sites

Searching “DDU download” returns multiple sketchy sites that bundle DDU with adware installers. Only download from wagnardsoft.com or the official Guru3D thread. The real DDU never asks to install toolbars, browser extensions, or “optimization” software.

Not Disconnecting Internet Before Installing

Windows Update has an aggressive habit of auto-installing GPU drivers. If you’re connected to the internet after DDU finishes, Windows might download and install an older driver from Microsoft’s catalog before you can install the one you downloaded. DDU has an option to “Prevent downloads of drivers from Windows Update” – make sure it’s checked in DDU’s Options menu before you clean.

Using DDU for Every Minor Update

DDU is a tool for problems, not routine maintenance. If you’re on NVIDIA driver 572.xx and updating to 573.xx with no issues, just update normally through GeForce Experience or the NVIDIA website. Reserve DDU for brand switches, post-update problems, or your annual “fresh start” cleanup.

Forgetting to Re-Apply Settings

DDU wipes everything. Your NVIDIA Control Panel 3D settings, your AMD Radeon per-game profiles, your color calibration – all gone. If you have specific resolution settings, refresh rate overrides, or per-game configurations, write them down or screenshot them before running DDU.

Forgetting Windows 11 Memory Integrity Blocks DDU

Core Isolation > Memory Integrity (also called Hypervisor-Protected Code Integrity or HVCI) blocks drivers with unsigned kernel-mode components – and DDU’s driver-store cleanup sometimes trips this check on Windows 11. Symptoms: DDU completes, reboots, and the new driver installs but won’t load, with Device Manager showing Error Code 39 or 52. Fix: go to Windows Security > Device Security > Core Isolation details, toggle Memory Integrity off, reboot, install the driver, then turn Memory Integrity back on after a clean reboot cycle. Leave it on long-term for security – just disable it during clean installs on Win11 if you hit the error.

What If DDU Doesn’t Fix Your Problem?

DDU solves about 85-90% of driver-related GPU issues. But if you still have crashes or black screens after a clean install, the problem is likely hardware or something else in your software stack.

Check These Next

• GPU overheating – Open HWMonitor or GPU-Z and check temperatures under load. If your GPU hits 90C+ in games, the thermal paste might be dried out or your case airflow is choked. No driver fix addresses thermal throttling.
• Faulty PCIe slot or cable – Reseat your GPU in the PCIe slot. Try a different power cable from your PSU. Loose connections cause intermittent black screens that look like driver issues but aren’t.
• Insufficient PSU wattage – A GPU drawing more power than your PSU can supply causes random shutdowns and crashes under load. Check your PSU rating against your GPU’s TDP requirement.
• RAM issues – Bad RAM causes crashes that get blamed on GPUs constantly. Run Windows Memory Diagnostic or MemTest86 to rule this out.
• Windows corruption – Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an admin Command Prompt. Corrupted system files can prevent drivers from installing correctly.

Stuck in Safe Mode? (bcdedit Fallback)

If Windows keeps booting into Safe Mode after DDU finishes – usually because you used msconfig but forgot to uncheck Safe boot, or because a Windows update re-enabled the safe boot flag – run this from an Administrator Command Prompt:

bcdedit /deletevalue {default} safeboot

Reboot. Windows should load normally. If that doesn’t work, try the alternate command bcdedit /set {current} safeboot minimal to explicitly set it, then bcdedit /deletevalue {current} safeboot to remove. This is the same command PC36 and Microsoft support docs point to for stuck Safe Mode loops. If Command Prompt itself won’t open, boot to WinRE (hold Shift and click Restart from the login screen) and open Command Prompt from Troubleshoot > Advanced Options.

Black Screen Persists? Try a Different Port

If your monitor stays black after the install completes, the driver may have defaulted to the wrong display output. Power off, swap the cable from DisplayPort to HDMI (or HDMI to DP), and boot again. Some NVIDIA 40-series and 50-series cards default to a different output after a clean install than they used before. If the monitor comes alive on the swapped port, you can swap back once you’re in Windows and configure the right port in display settings. Also check that the cable is plugged into the GPU, not the motherboard – a surprising number of “black screen after DDU” reports turn out to be a cable in the iGPU port.

Installer Says “Not Compatible with This Windows Version”

NVIDIA and AMD dropped support for older Windows 10 builds in 2024. If your installer refuses with “not compatible with this version of Windows,” you need either an older driver or a Windows update. Check your Windows build: press Win+R, type winver, hit Enter. If it reads 20H2, 21H1, or older, update Windows first via Settings > Windows Update > Check for updates. If Windows Update can’t advance you (common on domain-joined corporate machines), download the Windows 11 Installation Assistant or run the 22H2/23H2 enablement package manually. After Windows is on a supported build, re-run the GPU driver installer. If you’re stuck on a specific Windows build for compatibility reasons, use NVIDIA’s or AMD’s driver archive to find the last version that supports your build.

DDU Settings Worth Changing

DDU’s default settings work fine for most people. But a few options in the Options menu are worth knowing about.

Prevent Windows Update Driver Downloads

Under DDU’s Options, check “Prevent downloads of drivers from Windows Update when DDU cleans.” This stops Windows from silently reinstalling drivers before you get to install your chosen version. This is the single most important setting change in DDU.

Remove GeForce Experience / AMD Adrenalin Folders

DDU can optionally remove the user data folders for GeForce Experience and Adrenalin. Enable this if you want a truly fresh start. The tradeoff: you’ll lose any saved ShadowPlay recordings paths, game optimization profiles, and AMD per-game settings. For a troubleshooting clean install, that’s usually what you want.

Remove PhysX

If you’re switching from NVIDIA to AMD, remove PhysX. AMD GPUs don’t use it, and leftover PhysX libraries can cause startup errors in some older games that try to detect NVIDIA hardware. If you’re staying on NVIDIA, leave PhysX alone – DDU will remove the old version, and your new driver installer will put the current one back.

Specific Options Table: When to Toggle Each

DDU’s Options menu has more switches than most users ever touch. This table covers the ones worth knowing:

The “Clean Shader Cache (Only)” button deserves a special note: it wipes AppData shader cache without touching the driver. If stuttering appeared after a specific game patch or driver version but everything else works, try this first before a full DDU clean. Takes 10 seconds, no Safe Mode needed, no reboot.

Automating DDU: Command-Line Flags for IT Pros

DDU supports command-line automation for scripted deployments. The flags work from any elevated Command Prompt or PowerShell, and the tool writes a log to the DDU folder when run this way. Core flags worth knowing:

Example usage: "Display Driver Uninstaller.exe" -silent -cleannvidia -restart runs a full NVIDIA clean and reboots with no UI. IT shops deploying new GPU drivers across a fleet can chain DDU silent mode with the vendor’s silent-install installer in a single PowerShell or MDT task sequence. The tool still requires Safe Mode for a complete clean, so wrap the sequence in a bcdedit safeboot toggle or schedule the task to run at next boot after a Safe Mode reboot.

When to Use DDU vs. Other Solutions

DDU fixes driver problems. Not all GPU problems are driver problems. Here’s how to decide what tool to reach for.

AMD Cleanup Utility (First-Party AMD-Only Tool)

AMD ships its own cleanup tool at amd.com/cleanuninstall. It’s AMD-only (doesn’t touch NVIDIA or Intel), runs in Safe Mode or normal Windows, and AMD officially recommends it for troubleshooting Adrenalin install issues. Cleanup takes 15-20 minutes and requires a reboot.

Use AMD Cleanup Utility instead of DDU when: you have an all-AMD system, the problem is specifically with Adrenalin Software (crashes, won’t open, install errors), and you want AMD’s official first-party tool for warranty-case troubleshooting. Use DDU instead when: you need a deeper clean (registry, driver store, scheduled tasks), you’re switching brands, or AMD Cleanup Utility didn’t fix the problem. DDU catches more edge cases. AMD Cleanup Utility is lighter-weight and carries AMD’s official blessing. Both exist because they serve different situations.

NVCleanstall (Installer Customizer, Not a DDU Replacement)

NVCleanstall from TechPowerUp is sometimes listed alongside DDU as an alternative, but they do completely different jobs. NVCleanstall is a pre-install tool: it takes an NVIDIA driver package and lets you strip components (telemetry, HD audio, USB-C driver, NVIDIA App) before you install it. DDU is a post-install cleanup tool that removes whatever is already on your system.

Use them together, not as substitutes. The workflow is: DDU cleans the old driver in Safe Mode, reboot to normal Windows, then run NVCleanstall to build a slimmed-down NVIDIA installer, then run that custom installer. NVCleanstall does not replace DDU’s registry cleanup or driver-store removal, and using it alone on a system with corrupted driver leftovers won’t fix the underlying mess.

Standard Windows Uninstall (When It’s Enough)

For routine driver updates on a working system with no issues, skip DDU entirely. Open Settings > Apps, find “NVIDIA Graphics Driver” or “AMD Software,” click Uninstall, and install the new version from the vendor. This is the lightweight path for cases where the driver is clean and you just want the latest version. It’s faster than DDU, doesn’t need Safe Mode, and is the right tool for 80% of routine updates. DDU is reserved for when Windows uninstall isn’t enough.

2026 update: The RTX 5070 and RX 9070 XT redefined mid-range GPU value. Our GPU guide covers current recommendations.

Frequently Asked Questions

Is DDU safe to use?

DDU is safe. It only removes display driver files, registry entries, and related software – it does not touch Windows system files, personal data, or other hardware drivers. The tool has been maintained since 2012 and is recommended by NVIDIA and AMD community managers on official forums. The worst outcome from using DDU incorrectly is a low-resolution display until you install new drivers.

Can I run DDU without Safe Mode?

You can, but you shouldn’t. Running DDU in normal Windows means the GPU driver is loaded and file-locked by the operating system. DDU can’t delete locked files, so the removal is incomplete. Wagnardsoft’s workaround if you absolutely can’t reach Safe Mode: run DDU in normal mode, reboot, run DDU again, reboot again. The two-pass cycle catches most of what gets left behind on pass one. Still, a single Safe Mode run removes more than two normal-mode runs combined. Always boot Safe Mode when possible – DDU itself warns you about this when it detects it’s running outside Safe Mode.

How often should I use DDU?

Most gamers only need DDU when something goes wrong – crashes after a driver update, switching GPU brands, or troubleshooting display issues. A once-per-year clean install is reasonable maintenance if you update drivers frequently. Using DDU for every minor driver update is overkill and wastes time for no benefit.

Does DDU work on Windows 11?

DDU works on Windows 10 and Windows 11, both Home and Pro editions. The Safe Mode boot process is identical on both operating systems. Make sure you’re running the latest version of DDU (check wagnardsoft.com) since older versions may not clean all Windows 11-specific driver paths.

Will DDU delete my game settings or save files?

No. DDU only removes GPU driver files, control panel settings, and driver-related caches. Your game saves, Steam library, installed games, and in-game settings are stored separately and are not touched. The only settings you lose are NVIDIA Control Panel or AMD Adrenalin profiles – resolution, refresh rate, per-game 3D settings, and color calibration.

What happens if DDU causes a black screen?

After DDU removes your driver, Windows falls back to the basic Microsoft display adapter. Your screen might briefly go black during the restart – that’s normal. If you get a persistent black screen after DDU, wait 2-3 minutes for Windows to detect the basic adapter. If still black, boot into Safe Mode again and install the new driver from there. In 12+ years of DDU’s existence, permanent damage from the tool has never been documented.

Why does my screen look low-res or show “Microsoft Basic Display Adapter” after DDU?

That’s expected, not a bug. DDU removed your GPU driver, so Windows loaded its generic fallback – Microsoft Basic Display Adapter. You’ll see low resolution, wrong refresh rate, no scaling, and washed-out colors until you install the new GPU driver. This is the exact state DDU was supposed to leave you in. Run the NVIDIA, AMD, or Intel installer you downloaded before rebooting. The display returns to normal within a few seconds of the driver loading. MSI’s support docs call this state out specifically because so many users think DDU broke their GPU.

Does DDU remove the NVIDIA App, GeForce Experience, and FrameView SDK?

DDU 18.1.5.2 and later remove all three by default. Earlier DDU versions only handled GeForce Experience and left the NVIDIA App and FrameView SDK behind because those are separately installed components. If you used an older DDU version, check Settings > Apps for “NVIDIA App” and “NVIDIA FrameView SDK” and uninstall them manually. Then re-run DDU 18.1.5.2+ to clear the user data folders. This is the most common reason users report “my clean install wasn’t actually clean” – stale NVIDIA App telemetry hooks survive older DDU versions.

DCH or Standard driver – which do I have and does it matter?

On Windows 10 1809+ and all Windows 11 builds, you have DCH. Standard drivers are only installable on Windows 10 pre-1809 or older Windows versions, and NVIDIA stopped publishing Standard packages for current-generation cards in 2022. To check: open NVIDIA Control Panel > Help > System Information > Driver Type. If it reads “Standard” on a modern Windows build, you’re on a legacy package and should run DDU before installing any current driver. You cannot install DCH over Standard or vice versa – the installer refuses with a compatibility error.

Installer says “not compatible with this Windows version” – what now?

Your Windows build is older than the driver requires. Press Win+R, type winver, and check your build number. NVIDIA and AMD current drivers require Windows 10 21H2 or newer, Windows 11 22H2 or newer. If you’re on 20H2, 21H1, or older, update Windows via Settings > Windows Update. If Windows Update is stuck, download the Windows 11 Installation Assistant from Microsoft. Only after Windows is on a supported build will the GPU driver install. As a fallback, NVIDIA’s and AMD’s driver archives list the last driver version that supported each older Windows build.

Installer says “could not find compatible graphics hardware” – what now?

Three causes. First: you downloaded the wrong driver – an RTX 4070 driver won’t install on an RTX 3060. Double-check your card’s exact model in Device Manager and re-download. Second: on a laptop, the generic vendor driver is rejecting your OEM-custom hardware ID. Download the driver from your laptop vendor (MSI, Dell, ASUS, HP, Lenovo) instead. Third: the GPU is disabled or disconnected. Power off, reseat the card in the PCIe slot, check both power cables, boot, and re-run the installer. Faulty PCIe connections show up as this error more often than actual “no GPU” scenarios.

DDU is stuck at “Cleaning…” for 10+ minutes – is it frozen?

Usually not. DDU slows down when it hits large driver-store packages (common after years of driver updates) or when your AV is scanning each removed file. Give it 15 minutes before assuming it froze. If it still hasn’t moved, press Ctrl+Alt+Delete, open Task Manager, and check if “Display Driver Uninstaller” is using CPU or disk. Active CPU/disk = still working, leave it alone. Zero activity for 5+ minutes = actually frozen. In that case, force-quit DDU, reboot into Safe Mode again, disable your antivirus real-time scanning, and re-run DDU. Antivirus interference is the most common cause of stuck DDU runs.

Can I use DDU for Intel Arc GPUs?

Yes. DDU supports Intel GPU drivers as of version 18.0, covering Intel Arc discrete cards (A-series, B-series), Iris Xe integrated graphics, and Arc Graphics on newer Intel CPUs. In the device-vendor dropdown after selecting “GPU” as device type, pick “Intel” and proceed normally. If your laptop has both an Intel iGPU and a discrete NVIDIA or AMD GPU (a common optimus/hybrid setup), use DDU’s “Clean all GPUs” option to wipe both vendors in one pass. Intel’s own support documentation at intel.com/support specifically recommends DDU for clean driver reinstalls.

Do I install AMD Chipset drivers before or after the GPU driver?

Before. On Ryzen systems, AMD Chipset Drivers set up PCIe enumeration, CPU power states, and the Platform Security Processor service that the GPU driver expects. Install the chipset package first, reboot, then install the Adrenalin GPU driver, reboot again. Skipping chipset installation on a Ryzen build causes random crashes that get blamed on the GPU driver. Intel CPU users can ignore this – Intel chipset drivers come from Windows Update automatically. Get the AMD chipset package from amd.com/support/chipsets matching your motherboard chipset (X670, B650, X870, etc.), not the Ryzen CPU generation.

I’m stuck in a Safe Mode boot loop – how do I get out?

Windows is honoring a safeboot flag that didn’t get cleared. Open an elevated Command Prompt (if you can’t reach Windows, boot to WinRE by holding Shift while clicking Restart at the login screen, then open Command Prompt from Troubleshoot > Advanced Options). Run bcdedit /deletevalue {default} safeboot and reboot. Windows should load normally. If that specific command fails, try bcdedit /deletevalue {current} safeboot instead. This typically happens when users enable Safe boot via msconfig but forget to uncheck it after the DDU session. Microsoft support threads and PC36 both document this exact fix.