Fix Printer Error 0x00000BC8 (Core Driver Package Not Found)

Yeah, this error is a pain. You're trying to install or update a printer driver in Windows and get hit with ERROR_CORE_DRIVER_PACKAGE_NOT_FOUND (0x00000BC8). Usually pops up after a failed driver update or when Windows Update left a half-baked driver behind. The culprit here is almost always a corrupted or orphaned driver package in the Windows driver store.

The Direct Fix — Clear the Driver Store

Don't bother with the printer troubleshooter or reinstalling the same driver manually. That rarely helps here. What you need to do is wipe the stale driver package from the driver store (DriverStore) and do a clean install.

1. Press Win + R, type printmanagement.msc, hit Enter. This opens Print Management.
2. In the left pane, expand Print Servers > your computer name > Drivers.
3. Look for any driver entries related to your printer model. Right-click and Remove each one. If it fails to remove, move to step 4.
4. If Print Management won't let you delete the driver (common with stuck packages), you need to kill it from the driver store directly. Open an administrative Command Prompt.
5. Run pnputil /enum-drivers and look for your printer's published name (e.g., oemXX.inf). Note the oemXX.inf filename.
6. Force remove it with pnputil /delete-driver oemXX.inf /force.
7. Restart the Print Spooler service: net stop spooler & net start spooler.
8. Now reinstall the printer driver fresh — download the latest package from the manufacturer's site (not Windows Update). Run the installer as administrator.

Why This Works

Windows stores all your device drivers in a protected area called the driver store. When a printer driver package gets partially installed or corrupted (usually from a botched Windows Update or a failed uninstall), Windows can't locate the .inf file it needs. That's error 0x00000BC8 — it literally says "core driver package not found." By manually deleting the driver package from the store using pnputil, you force Windows to rebuild the entry clean. No leftover junk, no confusion.

Less Common Variations & Workarounds

Sometimes the issue isn't driver corruption — it's a permission problem. If you see this error when adding a network printer (especially in a domain environment), check these things:

• Group Policy blocking driver installation: Run rsop.msc and look under Computer Configuration > Administrative Templates > Printers > Allow installation of drivers using kernel-mode drivers. Make sure it's not set to Disabled.
• Print spooler service crashes: If the spooler keeps dying during install, run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth. Corrupted system files can mess with driver store operations.
• 32-bit vs 64-bit mismatch: If you're installing a printer shared from a different OS architecture, the driver package might not match. Use Print Management to add a second driver version (e.g., x64 and x86) on the print server.

Prevention — Stop It Coming Back

This error often reappears if you let Windows Update manage printer drivers. Turn that off. Go to Settings > Windows Update > Advanced options > Optional updates > Driver updates and uncheck any printer driver offered. Download drivers only from the manufacturer's site. Also, when uninstalling a printer, don't just delete the printer — go into Devices and Printers, right-click the printer, select Remove device, then tick Remove driver when prompted. Keeps the driver store clean.

One last thing: if you're managing multiple printers in a business, use pnputil /export-driver oemXX.inf C:\DriversBackup before removing anything. Saves your ass when you need to revert.