0x00004005 printing error — permissions & spooler dependencies

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Windows 11/10, Printers, Drivers, Networking, Office Equipment

Fix 0x00004005 printing error — repair permissions & Print Spooler / RPC dependencies

Technician

Hey! Let’s tackle the 0x00004005 printing error. This code usually appears while connecting to a shared printer or sending a job, and it points to permissions issues or broken Print Spooler dependencies (RPC/DCOM/HTTP). Tell me: are you adding a network printer via SMB/Standard TCP/IP or printing to a local USB device? We’ll reset ACLs, verify services, and clear the spooler cache.

Customer

Windows 11 can’t connect to our office HP on the server share — “Operation failed with error 0x00004005”. Other users print fine. I also see “Access denied” sometimes.

Technician

Got it. On Windows 11/10 this error is often caused by:
• Broken spooler dependencies — RPC Endpoint Mapper, DCOM Server Process Launcher, and sometimes HTTP (for IPP) not running.
• Incorrect permissions on the spool folder (C:\Windows\System32\spool) or registry HKLM\System\CurrentControlSet\Control\Print.
• Hardened Point and Print restrictions or GPO requiring admin to install drivers from unapproved servers.
• Corrupted jobs in the queue or a driver store problem (PCL XL error/PostScript error jobs stuck).
We’ll verify services, reset ACLs, clear the queue, then re-add the printer using Standard TCP/IP or a trusted share.

Customer

Where do I check those dependencies and permissions?

Technician

5-minute fix for 0x00004005 — Windows 11/10:
1) Open services.msc. Set Print Spooler to Automatic and start it. Ensure RPC Endpoint Mapper, DCOM Server Process Launcher, and Remote Procedure Call (RPC) are running (these are the spooler dependencies).
2) Clear the queue: Stop Spooler → delete files inside C:\Windows\System32\spool\PRINTERS → start Spooler.
3) Reset spool folder permissions (as admin):
icacls "C:\Windows\System32\spool" /grant administrators:F system:F "creator owner":F /T
4) If adding from a server, connect using \\printserver\queue that’s listed in GPO: Package Point and Print – Approved servers, or install via Standard TCP/IP port to bypass share issues.
Try printing again. If 0x00004005 persists, we’ll repair registry ACLs and policy.

Customer

I stopped the Spooler and cleared PRINTERS. Still getting the same error when I try to add the shared printer.

Technician

Check Point and Print restrictions: On Windows 11/10, updates require admin elevation for untrusted print servers.
• Pro/Enterprise (GPO): Computer Configuration → Admin Templates → Printers → enable Package Point and Print – Approved servers and add your print server FQDN. Set Point and Print Restrictions to Do not show warning / Elevation prompt = Disabled for approved servers.
• Workgroup/Home: temporarily add the printer using Standard TCP/IP port (JetDirect/IPP), or install the driver package locally first.

Customer

If I try TCP/IP, the port adds, but the job errors out. Could this be registry permissions?

Technician

Reset Print subsystem permissions:
• Open regedit → navigate to HKLM\SYSTEM\CurrentControlSet\Control\Print. Right-click → Permissions → ensure Administrators and SYSTEM have Full Control. Inherit to subkeys (Printers, Environments, Monitors, Providers).
• In C:\Windows\System32\spool → Security tab → give Administrators, SYSTEM, and Creator Owner Full Control; Users = Modify.
• Restart Spooler. Test print. If you hit PCL XL error or PostScript error, reinstall a fresh x64 package driver and delete stale packages via Print Management.

Customer

Do I need WSD or Standard TCP/IP? We’re mixing both.

Technician

Use Standard TCP/IP (JetDirect/IPP) for stability. WSD relies on discovery services that can trip dependency or permission errors. For IPP printing ensure HTTP service is present and Spooler dependency is satisfied. For SMB shares, verify Print$ share permissions and that your user is allowed to print. A clean TCP/IP port + correct driver avoids 0x00004005 in most cases.

Customer

Anything else to repair if the spooler keeps crashing?

Technician

Repair system files & reinstall drivers:
1) Run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth.
2) In Print Management, remove old Drivers and Ports → Install the vendor’s Type 4 x64 package or universal driver.
3) Recreate a Standard TCP/IP port with the printer’s static IP. Test from a local admin account to rule out user-profile ACL issues.

Customer

Great. Can you give me steps specific to Windows Home (no GPO)?

Technician

Windows 11/10 Home — workaround:
• Install the printer package driver from the vendor first.
• Add the device using Standard TCP/IP or direct USB; avoid WSD during testing.
• Ensure Spooler/RPC services are running and spool folder permissions are reset with icacls as above.
• If connecting to a server share triggers 0x00004005, temporarily copy the .INF package locally and install as admin.

Customer

Thanks. Please summarize the fix path so I don’t miss anything.

Technician

Summary: Fix 0x00004005 printing error by verifying Print Spooler dependencies (RPC/DCOM/HTTP) → clear spool cache → reset spool folder & registry permissions → align Point and Print policy or use Standard TCP/IP → reinstall a clean x64 package driver. Need help mapping your GPO or resetting ACLs safely? Open the chat — I’ll walk you through it live.

Quick answer: the accepted fix

Accepted fix for 0x00004005 printing error: start Print Spooler and required RPC/DCOM services, clear PRINTERS folder, reset permissions on spool folder & Print registry keys, then add the printer via Standard TCP/IP port or an approved Point and Print server and install a clean x64 package driver.

FAQ

Step-by-step (Windows 11/10)

1. Verify Print Spooler, RPC Endpoint Mapper, DCOM Server Process Launcher, and Remote Procedure Call (RPC) are running.
2. Stop Spooler → clear C:\Windows\System32\spool\PRINTERS → start Spooler.
3. Reset permissions on spool folder and HKLM\...\Print registry keys.
4. Approve print servers in GPO Point and Print or add via Standard TCP/IP port.
5. Remove stale drivers; install a clean x64 package/universal driver; test print.

Optional: advanced checks

1. Run SFC/DISM to repair system files if the spooler keeps failing.
2. Ensure printer has a static IP and avoid WSD when stability is required.
3. Audit Print$ share permissions on the server if connecting via SMB.

Sources

• Microsoft — Print Spooler service & security guidance
• Microsoft — Point and Print restrictions (GPO)
• Microsoft — Reset file and registry permissions (icacls)

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.