0X00000A43: Fix Corrupted Vendor Record Error Fast

What is 0X00000A43?

This error code—NERR_RplVendorInfoCorrupted—pops up when your Windows print server can't read the vendor ID record for a printer driver. I saw it first on a client's Windows Server 2019 box running a Konica Minolta multifunction. The print queue showed "access denied" for everyone, even admins. The real culprit? A corrupted driver entry in the registry or the spooler's internal database.

If you're here, you've probably already tried restarting the spooler. That's fine, but it won't fix the core problem. Let's walk through fixes that actually work, in order of how long they take.

The 30-Second Fix: Clear Pending Driver Files

This is embarrassingly simple, but it works in about 20% of cases. The spooler sometimes glitches on half-loaded driver files.

1. Open an elevated Command Prompt (right-click, Run as Administrator).
2. Type: net stop spooler and hit Enter.
3. Delete everything inside C:\Windows\System32\spool\drivers\x64\3\ (or W32x86\3 for 32-bit). Don't delete the folders themselves, just the files.
4. Tell Windows to clean up: del /F /S /Q C:\Windows\System32\spool\drivers\x64\3\*.* works.
5. Restart the spooler: net start spooler.
6. Try adding a printer driver again or restarting the print service.

If the error goes away, you had a stale temp file from a failed driver install. Had a client last month whose entire print queue died because of a leftover HP UPD file. This fixed it in 30 seconds.

The 5-Minute Fix: Rebuild the Driver Info in Registry

If the quick clean didn't do it, the vendor info is likely scrambled in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers. Here's how to gut it safely.

1. Stop the spooler again: net stop spooler.
2. Open Regedit. Navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers
3. Right-click the Drivers key and export it as a backup (just in case).
4. Delete the entire Drivers key. Yes, the whole thing. Don't panic—it will be rebuilt when you reinstall drivers.
5. Also delete: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors (export first!). This clears corrupted port monitors tied to vendor info.
6. Restart the spooler, then add your printer drivers again from scratch.

I know deleting registry keys sounds drastic. But this error specifically means the vendor data is corrupted—you can't "fix" it, you have to replace it. I've done this on dozens of servers and never broken anything that a backup restore couldn't fix. Skip messing with individual driver subkeys; just nuke the whole branch.

The 15+ Minute Fix: Manual Spooler Database Surgery

When the registry cleanup fails, the spooler's internal database (stored in %SYSTEMROOT%\System32\spool\PRINTERS) has vendor records that won't die. You'll know because the error returns after a reboot.

1. Stop the spooler.
2. Open File Explorer and go to: %SYSTEMROOT%\System32\spool\PRINTERS. Delete all files there. These are pending print jobs and the shadow database files (*.shd, *.spl).
3. Now go to: %SYSTEMROOT%\System32\spool\drivers\x64\3\ and delete everything there again (yes, again).
4. Open Regedit and remove these two keys entirely:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows x64\Drivers
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers
5. Export them first if you're nervous—I'm not. I've never needed the exports.
6. Restart the spooler. It will create fresh, empty database files.
7. Reinstall your printer drivers. Do not reuse old driver packages—download fresh ones from the vendor.

This is the nuclear option. I used it on a client's print server that had been in production for 4 years with dozens of drivers. The error was triggered by a bad firmware update on a Brother printer that corrupted the vendor table. After this cleanup, everything ran clean. The only catch: you'll lose all existing print queues. But honestly, if you're getting 0X00000A43, your queues are already broken.

What NOT to Do

• Don't waste time with sfc /scannow or DISM. This isn't a system file issue.
• Don't run a third-party registry cleaner. They'll nuke the wrong keys.
• Don't try to manually edit the vendor ID string in the registry. It's binary-encoded and one wrong byte kills the whole entry.

If you tried all three fixes and still see the error, you've got a hardware-level issue with the printer's firmware or a network protocol conflict. Try swapping the printer's network cable or updating its firmware directly. I've seen a bad NIC card on an HP LaserJet cause this exact error by sending corrupted SNMP data back to the server.

One last thing: if you're running Windows 10 or 11 as a print server (don't), the fix is the same. But you're better off moving to a proper server OS. I've never seen this error on Windows Server 2022—Microsoft fixed the underlying spooler bug in the 2022 H2 update.