Windows cannot connect to the printer
The attempt to attach to a printer failed, usually a printer shared from another computer or a print server. Windows normally shows a hexadecimal code alongside this sentence, and that code tells you far more than the sentence does. Without a code it is a general connection failure covering credentials, drivers and networking.
What causes it
- The sharing computer is offline, asleep or unreachable by name
- A driver could not be transferred from the server to your PC
- Your account lacks permission on the shared queue
- A security update changed the authentication the server must support
- The local Print Spooler is stopped or in a bad state
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.
Note the hexadecimal code
Read the exact code in the dialog, such as 0x0000011b, 0x00000709 or 0x0000007e. Each has a distinct cause and fix, and troubleshooting blind wastes time. Write it down before dismissing the dialog.
Check the host is reachable
In File Explorer type \\hostname and press Enter. If the share does not open, fix the network path first; the printer cannot be reached while the computer hosting it cannot. Make sure that machine is awake and on the same network.
Restart the Print Spooler on both ends
Press Windows+R, type services.msc, press Enter and restart Print Spooler on your PC and on the host. Then retry the connection. This resolves a surprising share of connection failures on its own.
Install the printer driver locally
Download the manufacturer's driver for the exact model and install it as administrator on your PC before connecting. Once the driver is present locally, the connection no longer depends on the server providing driver files, which is the step that fails most often.
Connect directly by IP
Open Settings › Bluetooth & devices › Printers & scanners › Add device › Add manually › Add a printer using an IP address or hostname. Choose TCP/IP Device and enter the printer's own address from its network configuration page. This bypasses the shared queue completely.
Update the sharing computer
Run Windows Update to completion on the machine that shares the printer and restart it. Version mismatches introduced by print security updates are a leading cause of sudden connection failures on networks that worked for years.
Clear stale credentials
Open Control Panel › Credential Manager › Windows Credentials and delete saved entries for the host. Reconnect and enter hostname\username when prompted. Old cached credentials produce connection failures that look like network problems.
Remove and re-add the queue
Delete the printer in Settings, remove its driver package in printmanagement.msc, restart, and add it again. A half-created queue from an earlier failed attempt will keep failing until it is cleared.
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
Which code is the most common?
0x0000011b, caused by the print authentication hardening, and 0x0000007e, caused by driver transfer failures, account for a large share of cases.
Can I connect without the host PC being on?
Not through a share. If the printer has its own network connection, add it by IP and the host becomes irrelevant.
Do I need the exact same driver as the server?
Not if you connect by IP. For a shared queue, matching driver names and versions avoids most conflicts.
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.