0x00000006 when connecting to shared printer — resolution guide (Windows 11/10)

Joe B.

Reviewed for technical accuracy

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

Fix printer error 0x00000006 — resolve Windows 11 network printer problems after updates

Technician

Hey! I can help you clear the 0x00000006 when connecting to shared printer error. This is a common shared printer connection error on Windows 11/10 and usually points to a printer driver mismatch error, Point and Print restrictions, or a stale queue on the client. We’ll clean bad packages, align driver versions (x64/x86), and reconnect to \\printserver\sharename properly.

Customer

I cannot connect to the shared printer after update. Since Patch Tuesday, every attempt throws 0x00000006. This is a small office with a Windows 11 Pro PC sharing an HP queue.

Technician

Got it. 0x00000006 is usually thrown when Windows blocks the client from installing the server’s driver. Typical triggers:
• Server/client have different driver models (Type 3 legacy vs Type 4), causing a printer driver mismatch error.
• Tightened Point and Print or SMB policies after updates → clients can’t download the package.
• Corrupt queue remnants on the client from a previous connection (old HP/Brother driver left behind).
• Credentials or name resolution issues (wrong cached password / DNS). We’ll fix each cause in order.

Customer

What’s the fastest way to fix printer error 0x00000006 on Windows 11?

Technician

5-minute fix for 0x00000006 (Windows 11/10):
1) On the client, remove the stuck connection in Settings → Bluetooth & devices → Printers & scanners.
2) Open Print Management → All Drivers → remove any leftover vendor packages for that model (HP/Brother/Canon).
3) Restart the Spooler: services.msc → Print Spooler → Restart. Or run net stop spooler && net start spooler as admin.
4) Reconnect using the UNC path \\ServerName\ShareName. If prompted for admin approval (Point and Print), accept only from your trusted server.
5) If it still fails, install a matching vendor or universal print driver locally first, then connect to the share.

Customer

It’s shared from a Windows 11 PC. Clients are Windows 10 and 11. Some connect; others throw the error. Could this be a Windows 11 network printer problem with driver types?

Technician

Yes — align the driver model across server and clients.
• Prefer a single package for all: HP/Brother Universal Print Driver (x64). Avoid mixing Type 3 & Type 4 for the same queue.
• On the sharing PC, install the x64 package and re-share the printer. On clients, remove legacy PCL5e/PS remnants before reconnecting.
• If your vendor offers PCL6 and PS, start with PCL6; switch to PS only for specialty apps.

Customer

I still cannot connect to the shared printer after update. Do I need to change any Point and Print or SMB settings?

Technician

Adjust Point and Print to allow the trusted server (Pro/Enterprise via gpedit):
• Computer Configuration → Admin Templates → Printers → enable Point and Print Restrictions and list your print server (FQDN). Set prompts to “Show warning and elevation prompt” if needed.
• Ensure the sharing PC exposes the print$ share and clients can read drivers. Clear cached creds in Credential Manager if auth loops.
• After policy refresh (gpupdate /force), reconnect to \\server\share.

Customer

What about fixing it without policies? We’re a small peer-to-peer workgroup.

Technician

Workgroup quick method:
• On each client, install the same vendor/x64 package locally (HP/Brother universal). Create a local TCP/IP port to the sharing PC’s IP (or the printer’s IP if available).
• Then connect to the share; Windows detects the driver already present and skips the blocked download that causes 0x00000006.
• Keep device names identical to avoid duplicate queues after Windows Updates.

Customer

Anything else I should check to prevent this error returning?

Technician

Prevention tips:
• Keep server and clients on the same PCL6 (or PS) version; don’t mix.
• Update the printer’s firmware and the print server’s NIC/SMB components.
• Avoid third-party “driver helpers”; they often leave stale packages that trigger 0x00000006.
• If the queue name changes, delete old connections before mapping the new share.

Customer

Great. Can you summarize the steps to fix the shared printer connection error on Windows 11/10?

Technician

Summary: Remove the old connection → purge leftover drivers → align driver model (prefer x64 Universal / PCL6) → restart spooler → reconnect via \\server\share. If updates tightened security, set Point and Print to trust your server. Still stuck? Open the chat — I’ll fix it live.

Quick answer: the accepted fix

Accepted fix for 0x00000006 when connecting to a shared printer: remove the old queue, delete stale vendor packages, install a matching Universal/PCL6 x64 driver, restart the Spooler, then reconnect to \\server\share. If blocked after updates, allow your print server in Point and Print Restrictions.

FAQ

Step-by-step (Windows 11/10)

1. Remove the old shared printer connection in Printers & scanners.
2. Open Print Management → delete legacy vendor Drivers for that model.
3. Restart the Print Spooler service.
4. Install the matching Universal/PCL6 x64 package locally.
5. Reconnect via \\ServerName\ShareName; if needed, trust the server with Point and Print Restrictions.

Optional: advanced checks

1. Unify driver model across server/clients (avoid mixing Type 3/Type 4).
2. Clear cached credentials in Credential Manager and re-authenticate.
3. Update printer firmware and the host PC’s NIC/SMB stack; confirm DNS resolves the server consistently.

Sources

• Microsoft — Point and Print restrictions
• Microsoft — Windows printing and driver models
• HP — Universal Print Driver (x64)
• Brother — Universal Printer Driver

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.