Windows error 0x000003eb when adding a printer
Windows started installing the printer driver and then reported that it needs to restart to finish, or that the operation cannot complete in its current state. The install is left incomplete, so the printer either does not appear or appears but will not print. It is a driver-staging problem rather than a hardware fault.
What causes it
- A pending restart is blocking driver files from being replaced
- An older version of the same driver is locked by the running spooler
- A partially removed printer left registry entries that the installer trips over
- Windows Update installed a competing driver for the same device at the same time
- The driver package is not signed in a way current Windows will stage
How to fix it, in order
Work down the list and stop when the printer recovers. The steps are ordered from most likely and least invasive to last resort.
Restart the PC before anything else
This code often literally means a reboot is required to complete file replacement. Restart Windows fully rather than using Fast Startup shutdown, then try adding the printer again as the first thing you do. Many cases end here.
Restart the Print Spooler and clear the queue
Press Windows+R, type services.msc, press Enter, stop Print Spooler, delete everything in C:\Windows\System32\spool\PRINTERS, then start the service. This releases file locks that prevent the installer replacing driver components.
Remove the partial printer and driver
Go to Settings › Bluetooth & devices › Printers & scanners and remove any entry for the model, including greyed-out duplicates. Then open printmanagement.msc › Print Servers › your computer › Drivers and use Remove driver package on the matching driver. Restart before reinstalling.
Install the manufacturer driver as administrator
Download the current package for your exact model and Windows version, right-click the installer and choose Run as administrator. Let the installer add the printer itself rather than adding it first through Settings. Vendor installers stage their own files in the correct order.
Pause Windows Update during the install
Open Settings › Windows Update and choose Pause updates for one week. If Windows Update pushes its own driver for the same printer mid-install, the two writes collide. Resume updates once the printer is working.
Fall back to a manual TCP/IP install
In Printers & scanners › Add device › Add manually › Add a printer using an IP address or hostname, create a TCP/IP port to the printer's address and choose a generic PCL or IPP class driver on the driver page. If this succeeds, the vendor package is at fault, not Windows.
Check the PrintService log
Open eventvwr.msc, go to Applications and Services Logs › Microsoft › Windows › PrintService, right-click Admin and enable the log if needed, then reproduce the failure. The entries usually name the driver file that could not be staged.
Stopping it happening again
When it is not worth fixing yourself
If you would rather not work through this alone, a printer specialist can take a look with you on a screen-share and tell you honestly whether the machine is worth saving.
Frequently asked questions
Do I really need to restart?
Often yes. Windows cannot replace driver files that are currently loaded, and the restart is what releases them.
Will removing the driver package delete my other printers?
Only printers using that exact driver. Other models keep their own driver packages.
Is Fast Startup a problem here?
It can be, because a shutdown with Fast Startup does not fully reinitialise the system. Use Restart rather than Shut down.
Questions & comments (0)
No comments yet. Describe your printer model, operating system and the exact message you see; comments appear after review.
Ask about this page
Your comment appears after our team approves it. Or sign in to post faster.