Windows · Operating system
0x00000002

Windows error 0x00000002 - operation could not be completed

Windows reports that a file it needed for the printer could not be found. It surfaces when adding a printer, installing a driver, or setting a default, and the underlying complaint is a missing driver file or a broken registry pointer to one. The operation stops before anything is written.

Moderate Windows 11Windows 10Local, USB and network printers

What causes it

  • The driver package is incomplete because the download was interrupted or extracted badly
  • A previous uninstall removed driver files but left registry entries pointing at them
  • The driver was written for a much older Windows release and its files no longer exist
  • The Print Spooler cannot read its own driver store
  • The printer is being installed from a network share where the driver files are unavailable

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.

  1. Restart the Print Spooler first

    Press Windows+R, type services.msc, press Enter, right-click Print Spooler and choose Restart. Then retry the action that failed. A spooler holding a stale reference to a removed driver will often clear it on restart, and this costs nothing to try.

  2. Remove the half-installed printer and its driver

    Go to Settings › Bluetooth & devices › Printers & scanners, remove the printer, then open printmanagement.msc and go to Print Servers › your computer › Drivers. Right-click the matching driver and choose Remove driver package rather than just Remove. This clears both halves of the broken install.

  3. Download a fresh driver from the manufacturer

    Get the current package for your exact model from the manufacturer's support site, choosing Windows 11 64-bit unless you know you are on something else. Do not reuse an installer that failed previously, since a truncated download is a common cause of this exact code. Right-click the installer and choose Run as administrator.

  4. Clear the spool folder

    Stop Print Spooler in services.msc, delete the contents of C:\Windows\System32\spool\PRINTERS, then start the service again. Leftover jobs referencing a driver that no longer exists can keep the error alive after the driver itself is gone.

  5. Add the printer manually with a built-in driver

    In Printers & scanners › Add device › Add manually, choose Add a local printer or network printer with manual settings, pick the existing port or create a TCP/IP port, and on the driver page select a Microsoft IPP Class Driver or a generic PCL driver. This proves whether the vendor package is the problem.

  6. Repair system files

    Right-click Start, choose Terminal (Admin) and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth. Restart afterwards. If the missing file belongs to Windows rather than the vendor, this restores it from the component store.

  7. Check you are not installing across a broken share

    If you are adding a printer shared from another PC, open \\thatcomputer in File Explorer first. If the share itself is unreachable, the driver files genuinely are not there and the error is accurate. Fix the network path or install the printer directly by IP instead.

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

Does 0x00000002 mean the file is missing from my PC or the server?

Either. When adding a shared printer it is usually the server copy; when installing locally it is usually an incomplete driver package on your own machine.

Will a Windows built-in driver work instead?

For most modern network printers yes, via the IPP class driver. You may lose vendor-specific finishing or scanning features.

Should I edit the registry to remove the old printer?

Try printmanagement.msc first. It removes the same entries safely, and manual registry deletion often leaves the print subsystem in a worse state.

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.