Fix it now
Office does not print by itself; it hands every job to the Windows spooler, so a broken default printer or a failed connection to a shared queue stops Word, Excel and Outlook at once. 0x00000709 is Win32 1801, “The printer name is invalid”. Fix the default first, then rebuild the connection.
Get-Printer | Format-Table Name, Type, DriverName, PortName
Get-Printer | Where-Object { $_.Name -eq (Get-CimInstance Win32_Printer | Where-Object Default).Name }
- Open Settings, Bluetooth and devices, Printers and scanners. Turn off “Let Windows manage my default printer”, then set the default yourself and confirm it survives a reboot.
- Print a Windows test page from the printer’s own properties. If that fails too, the queue is at fault and Office is not involved.
- Remove the shared printer and add it again, so the connection is rebuilt rather than repaired.
- If the failure is 0x0000011b, bring the print server and the clients to the same update level, server first. Nothing on the client alone reliably settles this one.
- As a durable route while you sort the server out, install the manufacturer’s driver on the client and connect the device through a standard TCP/IP port instead of the shared queue.
- Retry from Word and then from Outlook, because they use the print path differently.
Do not delete queues that point at decommissioned servers and leave the driver behind. Remove the driver as well, from Print server properties on the Drivers tab, or the same failure comes back with the next connection.
If both applications print, stop here. If not, the next section explains which of these codes Microsoft actually publishes a meaning for, and which it does not.
Why it happens
Every Office application asks the print system for the default printer while it is starting, because page size, margins and printable area all depend on it. If the default points at a queue that cannot be opened, the failure surfaces in page setup, in print preview and in printing. Users report that Word is broken. The spooler is what is broken, and the same fault is waiting in every other application that prints.
0x00000709 is the older and simpler of the two. Microsoft publishes it as Win32 1801, ERROR_INVALID_PRINTER_NAME, “The printer name is invalid”. The name handed to the print system is not one it can use: the queue was renamed or removed, the stored default points at a server that has gone, or Windows has just switched the default to something unusable because the option to manage it automatically is on.
0x0000011b is different, and the honest answer about it is not the one usually given. Decimal 283 is absent from Microsoft’s published Win32 error code list, which runs from 282 straight to 288. Microsoft publishes no meaning for it. What Microsoft does publish is that Windows 11 version 22H2 changed how machines communicate during printing, moving print-related client-server traffic to RPC over TCP by default, and it documents the settings that control that. So treat the number as a marker that you are looking at a shared-queue connection failure across the print RPC path, and diagnose the path rather than the code.
The other two are documented and useful. 0x0000007c is Win32 124, ERROR_INVALID_LEVEL, “The system call level is not correct”, which in a print context means the two sides disagree about the shape of the information being asked for. 0x00000bcb is Win32 3019, ERROR_PRINTER_DRIVER_DOWNLOAD_NEEDED, “The specified printer driver was not found on the system and needs to be downloaded” – which is why installing the driver on the client first is the fix rather than a workaround.
The default printer is stale or keeps changing
You have this one if 0x00000709, and the default printer in Settings is one you do not recognise or one that no longer exists.
- Turn off “Let Windows manage my default printer”. It changes the default to whatever you used last, including queues that have gone.
- Set the default explicitly and confirm it survives a reboot.
- Remove queues pointing at decommissioned servers, and their drivers with them.
- If the stored default seems stuck, remove and re-add the printer rather than editing it by hand.
The client and the print server are at different update levels
You have this one if 0x0000011b or 0x0000007c when connecting to a shared queue, while a directly attached printer works.
- Bring the print server fully up to date, then the clients. Doing only one side is what creates the mismatch in the first place.
- Reconnect the queue on one client and test before rolling anything out.
- Where the server cannot be updated promptly, connect clients to the device through a standard TCP/IP port as an interim measure.
Advice to add an undocumented registry value that relaxes print authentication circulates widely for this code. Microsoft does not publish such a value, and the settings it does publish for print RPC are listed in the reference section below. Configure those instead of a value nobody can point you at.
The driver cannot be installed by the user connecting
You have this one if 0x00000bcb, or a prompt for administrator credentials when adding the shared printer, leaving the connection half made.
- Install the driver on the client first, with the manufacturer’s package and administrative rights, then connect to the shared queue.
- Where many clients are affected, deploy the driver through your management tooling ahead of the printer connection.
- Check the print server publishes a driver matching the client architecture. A client cannot use a driver built for a different one.
- Where policy restricts driver installation to administrators, that is deliberate hardening. Deploy centrally rather than relaxing it.
The path to the print server is failing
You have this one if Opening the server by name in Explorer also fails, or works only sometimes.
- Confirm the server name resolves and the machine is reachable before touching anything about printing.
- Try the server’s address instead of its name. If that works, you have a name resolution problem, not a print problem.
- Check the spooler service is running on the server, not just on the client.
- Where print traffic uses RPC over TCP, confirm the RPC endpoint mapper port and the ephemeral port range are open between client and server.
Full reference
What each code is, and is not
| Code | Published meaning | Source |
|---|---|---|
0x00000709 |
Win32 1801, ERROR_INVALID_PRINTER_NAME: the printer name is invalid | Microsoft Learn |
0x0000007c |
Win32 124, ERROR_INVALID_LEVEL: the system call level is not correct | Microsoft Learn |
0x0000011b |
Decimal 283 is absent from the published Win32 error list. No meaning is published | Not published by the vendor |
0x00000bcb |
Win32 3019, ERROR_PRINTER_DRIVER_DOWNLOAD_NEEDED: the driver was not found on the system and needs to be downloaded | Microsoft Learn |
That third row is the one worth pausing on. A great deal of advice for 0x0000011b states confidently what the number means and hands you a registry value to make it go away. Microsoft publishes neither. What follows is what Microsoft does publish about the print RPC path, which is the layer the failure sits in.
The print RPC settings Microsoft publishes
Windows 11 version 22H2 and later use RPC over TCP by default for print-related client-server communication. RPC over named pipes is still available but is disabled by default. All four values live under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers\RPC and are REG_DWORD.
| Value | Effect |
|---|---|
RpcTcpPort |
Pins print RPC over TCP to a specific port, 1 to 65535, instead of the ephemeral range |
RpcUseNamedPipeProtocol |
1 makes the client use RPC over named pipes rather than TCP |
RpcProtocols |
0x7 makes the server listen on both TCP and named pipes |
ForceKerberosForRpc |
1 requires Kerberos for print RPC. Appropriate where every machine is domain-joined and Kerberos-capable |
Microsoft’s recommendation is to allow RPC over TCP rather than to fall back to named pipes: open the RPC endpoint mapper port 135 and the ephemeral range 49152 to 65535, or pin a single port with RpcTcpPort and open that. Named pipes needs additional configuration to work at all, including guest access in SMB2 and SMB3, which is a security default you should not be turning off to make a printer work.
Export the branch before adding any of these values, and change one machine before you change a policy. A wrong value here can leave clients unable to reach any shared queue, and the symptom is indistinguishable from the fault you started with.
Deciding between the shared queue and a direct connection
| Shared queue on a print server | Standard TCP/IP port to the device | |
|---|---|---|
| Driver updates | Managed centrally on the server | Managed on each client |
| Defaults and paper settings | Set once on the server | Set on each client |
| Accounting and auditing | Available on the server | Not available |
| Exposure to print RPC issues | Yes, this is the path that breaks | No, the client talks to the device |
| Works when the server is down | No | Yes |
Direct connections are a legitimate answer, not a hack, and they take the whole failing path out of the picture. What you give up is central control. For two printers and ten people that is a good trade. For a floor of shared devices with departmental accounting it is not, and the right move is to get both ends onto the same update level and keep them there.
When printing fails from every application, not just Office
- Print a Windows test page from the printer properties. If that fails, stop looking at Office entirely.
- Check the spooler is running on the client with
sc query spooler, and on the server too. - Run
Get-Printerand confirm the queue is present with the driver you expect. - Look under Applications and Services Logs, Microsoft, Windows, PrintService for the driver named around the time of the failure.
- If the spooler itself is stopping or crashing, that is a different fault with its own codes and its own fix.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x00000709 |
Win32 1801, ERROR_INVALID_PRINTER_NAME: the printer name is invalid. Commonly a stale or auto-managed default | Microsoft Learn |
0x0000007c |
Win32 124, ERROR_INVALID_LEVEL: the system call level is not correct. In print terms, the two sides disagree about the shape of the information requested | Microsoft Learn |
0x0000011b |
Decimal 283 does not appear in Microsoft’s published Win32 error code list and no meaning is published for it. Seen when connecting to a queue shared from another machine; diagnose the print RPC path and the update levels at both ends | not published by the vendor |
0x00000bcb |
Win32 3019, ERROR_PRINTER_DRIVER_DOWNLOAD_NEEDED: the specified printer driver was not found on the system and needs to be downloaded | Microsoft Learn |
Confirm the fix worked
- Print a Windows test page from the printer’s properties.
- Print from Word and from Outlook, since the two use the print path differently.
- Reboot and confirm the default printer is still the one you set.
- Run
Get-Printerand confirm the queue appears with the expected driver and port. - If you added any print RPC value, confirm you recorded it somewhere a future rebuild will find.
Questions people ask about this
Do I need to buy anything to fix this?
No. This costs nothing. It is a configuration and update problem in the Windows print path, and no Office or Windows licence changes anything about it.
What does 0x0000011b actually mean?
Microsoft does not say. Decimal 283 is not in the published Win32 error code list. Anyone telling you precisely what it means is telling you what would make their article work. What is documented is the print RPC transport change in Windows 11 22H2 and the settings that control it, which is where to look.
Should I add the registry value everyone recommends for this?
Not on the strength of a forum post. Microsoft publishes no value that relaxes print authentication, and the values it does publish for print RPC are in the reference section above. If a change is going to weaken a security default, you want to be able to point at who documented it.
Why does printing work from Notepad but not from Word?
Usually it does not, and the difference is which printer each application selected. If Notepad genuinely prints and Word does not, check that Word is not still holding a stale default from before the queue changed, and restart it.
The error came back after the next round of updates.
That points at the update-level mismatch again. Keep the print server in the same patching cycle as its clients, and update the server first.
