Printer driver install fails with Access Denied

Quick answer: Stop the Print Spooler service, delete %WINDIR%\System32\spool\drivers\W32x86, restart the spooler, then reinstall the driver.

If you're seeing the dreaded “Access Denied” error when installing a printer driver, what's actually happening here is that Windows has leftover driver packages or permissions on the driver store that block new installs. This usually happens after a previous printer driver was removed incorrectly, or you're trying to install a driver that conflicts with an existing one that's still registered in the print spooler's database.

Most people hit this after upgrading from an old printer to a new one — the old driver lingers, and Windows thinks you're trying to overwrite a protected file. The account you're using might be an admin, but the print spooler service runs as SYSTEM, and if old driver files are locked by the spooler or have corrupted ACLs, you get Access Denied.

Fix Steps

1. Stop the Print Spooler. Open an elevated command prompt (Run as Administrator). Run net stop spooler. Leave the window open.
2. Delete the driver folder. In that same prompt, run del /f /s /q %WINDIR%\System32\spool\drivers\W32x86\*.* and then del /f /s /q %WINDIR%\System32\spool\drivers\x64\*.* (if you're on 64-bit Windows). This wipes all driver files. If you get a “file in use” error, you forgot step 1.
3. Clear the driver registry keys. Run reg delete “HKLM\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers” /f (or “Windows NT x86” for 32-bit). This removes driver references that the spooler checks.
4. Restart the spooler. Run net start spooler.
5. Install the driver again. Run your printer setup as Administrator. It should proceed without the Access Denied error.

The reason step 3 works is that even after deleting the files, Windows still has registry entries that map the driver to the “already installed” state. Clearing those forces the system to treat the install as fresh. I've seen this fix work on Windows 10 22H2 and Windows 11 23H2 with HP and Canon drivers.

Alternative Fixes If the Main One Fails

• Use the Print Management console. Press Win+R, type printmanagement.msc. Under “Print Servers > Local > Drivers,” right-click any old driver and remove it. If that's grayed out, you've got permission issues — go back to the manual wipe.
• Take ownership with icacls. If delete commands fail on step 2, run icacls %WINDIR%\System32\spool\drivers /grant Administrators:F /T first. This forces full control for the admin group. Some enterprise-managed machines lock these folders tight — this bypasses that.
• Disable driver signing enforcement temporarily. On rare cases with unsigned drivers, Windows 10/11 may throw an Access Denied to block the unsigned driver. Boot into Advanced Startup (hold Shift while clicking Restart), go to Troubleshoot > Advanced Options > Startup Settings > Restart, then press 7 to disable driver signature enforcement. Install the driver, then reboot normally.

Prevention Tip

Don't delete printer drivers by just removing the device from Devices and Printers. That leaves the driver behind. Instead, always remove the driver explicitly via Print Management or by running printui /s /t2 (opens the driver removal dialog). If you're replacing a printer, remove the old driver first — it saves you the Access Denied headache later. I keep a script handy that stops the spooler and purges the W32x86 folder before any new printer install. It's overkill for most people, but if you manage multiple printers, it's worth the 10 seconds.

Note: This issue is specific to Windows. On macOS, printer driver permission errors are nearly nonexistent because CUPS handles drivers differently. If you're on Linux, Access Denied during driver install usually means a permissions issue with the lp group — not the same problem at all.