Fix STATUS_DRIVER_DATABASE_ERROR (0XC000036D) Fast

Quick Fix: Restart the Print Spooler (30 seconds)

This error shows up when Windows can't process the driver database—usually after a bad driver install or a failed Windows Update. I've seen it on Windows 10 22H2 and Windows 11 23H2 most often. Nine times out of ten, just restarting the print spooler does it.

1. Press Win + R, type services.msc, hit Enter.
2. Scroll to Print Spooler. Right-click it, select Restart.
3. Wait 10 seconds, then try your printer or scanner again.

If that didn't work, the driver database itself is probably corrupt. Don't waste time—move to the next step.

Moderate Fix: Clear the Driver Database Cache (5 minutes)

Windows stores driver info in a hidden system folder. When that folder gets corrupted—like after a failed driver install for a Brother HL-L2370DW I dealt with last month—you get this error. Here's how to nuke it safely.

1. Open Services (services.msc), stop Print Spooler again. Leave it stopped.
2. Open File Explorer to C:\Windows\System32\spool\drivers.
3. Delete everything inside the drivers folder. Yes, everything. Windows will rebuild it.
4. Go back to Services, start Print Spooler.
5. Restart your computer.

This clears out corrupt driver files that cause the 0XC000036D error. I've done this on maybe 20 machines—only failed twice (both had deeper corruption). If it works, you're done. If not, keep going.

Advanced Fix: Rebuild the Driver Store (15+ minutes)

Sometimes the corruption is deeper—it's in the driver store itself (C:\Windows\System32\DriverStore\FileRepository). This is where Windows keeps all approved driver packages. Had a client whose entire small office network died because of a bad HP LaserJet driver that corrupted the store. This fix requires admin rights and a bit of patience.

1. Open Command Prompt as Administrator.
2. Run this command to check the driver store for corruption:

   DISM /Online /Cleanup-Image /RestoreHealth

   Wait for it to finish (can take 10 minutes). If it finds issues, it'll fix them from Windows Update.
3. If DISM found nothing, run this to clear the driver store cache:

   pnputil /delete-driver * /force

   Warning: This removes all third-party drivers. You'll need to reinstall printer, scanner, and graphics drivers after. But it's the nuclear option that works when nothing else does.
4. Restart, then reinstall the driver that was causing the problem.

One more thing—if you're on Windows 11 23H2 or later, there's a known bug where driver database corruption happens after cumulative updates KB5034765 or KB5034848. If you see that update in your history, uninstall it first (Settings > Windows Update > Update history > Uninstall updates), then run the DISM fix.

I've had people ask about registry edits for this error. Skip them—they rarely help and can mess up your system. Stick to these three steps. Nine out of ten times, the quick or moderate fix gets you back to work.