
Error 0x0000011b comes from Windows requiring a higher authentication level for shared printer connections (the IRemoteWinspool RPC interface). The requirement arrived for CVE-2021-1678 in January 2021 and became the default with the September 14, 2021 updates. The right fix is to update the computer sharing the printer and every client, allow the RPC over TCP connection, and deploy drivers with administrator rights; setting RpcAuthnLevelPrivacyEnabled to 0 switches the protection off.
Symptoms
- When adding a printer shared by another computer on the network you see: “Windows cannot connect to the printer. Operation failed with error 0x0000011b.”
- A shared printer that worked before stops working after updates are installed on the computer sharing it.
- Computers that add the same printer directly by IP address (Standard TCP/IP port) are not affected.
- The problem mostly appears in small office networks where a Windows 10/11 computer shares the printer like a print server.
Root cause: the authentication level for printer RPC was raised
When connecting to a shared printer, Windows uses the Print Spooler RPC interface called IRemoteWinspool. To close CVE-2021-1678, Microsoft raised the authentication level required on this interface. The change came in two phases: the January 12, 2021 update made it available as an opt-in, and updates from September 14, 2021 onwards enforce it by default when the registry value is not defined.
The value that controls the change is RpcAuthnLevelPrivacyEnabled (REG_DWORD) under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print. 1 enables enforcement mode; 0 is the setting Microsoft marks as “not recommended” and that leaves devices unprotected. According to Microsoft’s KB4599464, if a client without the January 2021 update connects to a server in enforcement mode, the printing experience will be broken. In the field, 0x0000011b is the most common face of that mismatch.
In the same period the Point and Print rules were tightened for PrintNightmare (CVE-2021-34527) and CVE-2021-34481: in updates from August 10, 2021 onwards, RestrictDriverInstallationToAdministrators defaults to 1, meaning that installing the driver for a shared printer requires administrator rights. This second change often appears together with 0x0000011b and complicates the picture.
Working out which side the problem is on
Before moving to the fix, it saves time to work out whether the problem lies with the computer sharing the printer, with the client or with the network. If every client in the office is affected at the same time, the sharing computer has usually received a new update. If only one or two computers show the error, their update level and local policies are the first suspects.
- One client fails while the others connect: check that client’s update history and whether its operating system version is still supported.
- No client can connect and the port 135 test fails: the firewall or the network profile (Public/Private) may be blocking the sharing computer.
- The connection is made but an administrator password is requested: this is not 0x0000011b but the Point and Print driver restriction.
- The registry contains RPC or Point and Print values added by hand in the past: document when and why they were added; most of them are no longer needed.
Step-by-step fix
- Read the current settings on the computer sharing the printer and on the client (commands below). If RpcAuthnLevelPrivacyEnabled is missing or set to 1, enforcement mode is on; that is the expected and secure state.
- Install the latest cumulative update on the computer sharing the printer and on every client that connects to it. KB4599464 expects all clients and servers to be updated first, and enforcement to be enabled only after that. An outdated or unsupported client that can no longer receive updates is the most likely source of the problem.
- Windows 11, version 22H2 and later use RPC over TCP for shared printer communication by default and listen only over TCP. Make sure the firewall on the computer sharing the printer allows the RPC Endpoint Mapper port (135) and the dynamic ports (49152–65535) from the local network.
- If a Group Policy or an old “fix” forces the client to use RPC over Named Pipes (RpcUseNamedPipeProtocol = 1 under HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Printers\RPC), remove it and return to the default TCP behavior. Microsoft does not recommend the named pipe configuration.
- Pre-install the driver with administrator rights: connect once with an administrator account, add the driver to the Windows image, or deploy package-aware drivers from a server approved in the “Package Point and Print – Approved servers” policy. Leave RestrictDriverInstallationToAdministrators at 1.
- Rebuild the connection: delete the old printer entry on the client, restart the Print Spooler service and add the printer again from the \\computername\printername path.
- If an old client cannot be updated, connect that computer to the printer directly by IP address (Standard TCP/IP port) instead of the share, or replace the client.
rem Current RPC authentication setting (read only)
reg query "HKLM\SYSTEM\CurrentControlSet\Control\Print" /v RpcAuthnLevelPrivacyEnabled
rem Print RPC policy and Point and Print settings
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Printers\RPC"
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Printers\PointAndPrint"
rem Most recently installed updates (PowerShell)
powershell -Command "Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5"
rem Reachability of port 135 on the sharing computer (PowerShell)
powershell -Command "Test-NetConnection -ComputerName PRINTSERVER -Port 135"The most widely suggested “fix” online is to set RpcAuthnLevelPrivacyEnabled to 0 on the computer sharing the printer. It hides the error but switches off the protection added for CVE-2021-1678; Microsoft marks this value as “not recommended” and states that devices are left unprotected. Microsoft mentions the setting only for exceptional scenarios where RPC over TCP cannot be used at all and named pipes are mandatory. Complete the steps above before going down this road; if you have no choice, document the risk and plan a permanent fix.
Permanent prevention
- Instead of sharing the printer from a desktop computer, use an up-to-date print server or add printers to clients directly by IP address.
- Monitor that every computer receives the monthly cumulative updates; isolate or replace unsupported operating systems.
- Deploy printer drivers centrally through Group Policy or the image; do not rely on users installing drivers themselves.
- Try the monthly updates for the computer sharing the printer with a test client before rolling them out to the whole office, and if a problem appears, update the clients rather than changing the registry.
- In Point and Print Restrictions, make sure the warning and elevation prompt is shown (NoWarningNoElevationOnInstall and UpdatePromptSettings should be 0 or undefined).
When should you call a specialist?
When a network mixes different Windows versions, old drivers and registry “patches” applied in the past, finding which setting produces the error and fixing it without weakening security takes expertise. For printing problems like these, which we encounter in the field at businesses in Denizli, Workas reviews the update status and the RPC and Point and Print policies and puts printer deployment on a permanent footing as part of its system maintenance and support service. For emergencies we respond with priority during working hours.
Frequently Asked Questions
Is it safe to set RpcAuthnLevelPrivacyEnabled to 0?
No. Microsoft does not recommend it; it disables the CVE-2021-1678 protection and leaves the computer sharing the printer unprotected.
Will uninstalling the update fix it?
The connection may come back in the short term, but the device stays exposed to the vulnerabilities that security update closed. The correct path is to update the clients as well.
Why does adding the printer by IP address work?
With a printer added directly by IP, the client does not connect over RPC to the sharing computer’s print spooler, so it is not affected by this authentication requirement.
Why can standard users not add the printer?
In updates from August 10, 2021 onwards, installing drivers via Point and Print requires administrator rights by default. Pre-install the driver as an administrator or deploy it centrally.
Sources
- Microsoft Support: Managing deployment of Printer RPC binding changes for CVE-2021-1678 (KB4599464)
- Microsoft Support: KB5005010 – Restricting installation of new printer drivers after applying the July 6, 2021 updates
- Microsoft Support: KB5005652 – Manage new Point and Print default driver installation behavior (CVE-2021-34481)
- Microsoft Learn: Windows 11 RPC connection updates for print


