Fix: Network Printer Sharing Error 0x0000011b (Windows 10 to Windows 7)

By /

Summary This document outlines the registry-level intervention required to resolve the 0x0000011b network printing error. This issue typically occurs when legacy operating systems (Windows 7) attempt to connect to a shared printer hosted on a fully patched Windows 10 machine.

Environment

  • Print Server (Host): Windows 10 (Post-2021 Security Updates)
  • Client: Windows 7
  • Network Topology: Workgroup / Local Area Network (LAN)

Problem Legacy Windows 7 clients fail to establish a connection to a shared printer hosted on a Windows 10 machine. The printer is properly shared on the network, and file sharing is functional, but the specific attempt to map the printer (\\Host-IP\Printer-Name) gets instantly rejected by the host.

Symptoms

  • The shared printer is visible in the network directory.
  • Double-clicking to connect triggers a connection dialogue that fails immediately.
  • No print jobs can be spooled from the client to the host.

Error Message

Windows cannot connect to the printer.
Operation failed with error 0x0000011b.

Root Cause This is a protocol compatibility issue stemming from Microsoft’s security patches released to mitigate the “PrintNightmare” vulnerabilities (CVE-2021-1678). Windows 10 updates introduced a strict enforcement of RPC (Remote Procedure Call) authentication and encryption levels for the Print Spooler service. Since Windows 7 does not support this specific modern RPC authentication enforcement natively, the Windows 10 host actively terminates the handshake, resulting in the 0x0000011b error code.

Solution To resolve this issue and restore compatibility with legacy clients, the RPC authentication level privacy enforcement must be explicitly disabled on the Windows 10 Host machine. You can achieve this using either the automated Command Prompt method (recommended for speed) or the graphical Registry Editor method.

Option A: Automated Method (Command Prompt)

  1. Open the Start menu, type cmd, right-click on Command Prompt, and select Run as administrator.
  2. Execute the following commands to inject the registry key and restart the Print Spooler service immediately:
reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print" /v RpcAuthnLevelPrivacyEnabled /t REG_DWORD /d 0 /f
net stop spooler
net start spooler

Option B: Graphical Method (Registry Editor) If you prefer to make the changes manually, follow these steps on the Windows 10 Host machine:

  1. Press Win + R on your keyboard to open the Run dialog.
  2. Type regedit and press Enter to open the Registry Editor (accept the UAC prompt if it appears).
  3. Navigate to the following exact path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print
  4. Right-click on an empty space in the right pane, select New, and then click on DWORD (32-bit) Value.
  5. Name the new value exactly: RpcAuthnLevelPrivacyEnabled
  6. Double-click the newly created RpcAuthnLevelPrivacyEnabled value and ensure its Value data is set to 0 (Zero). Click OK.
  7. Close the Registry Editor.
  8. To apply the changes, either restart the Windows 10 computer entirely, or press Win + R, type services.msc, locate the Print Spooler service, right-click it, and select Restart.

(Explanation of why the solution works: Setting RpcAuthnLevelPrivacyEnabled to 0 instructs the Windows 10 Print Spooler to accept non-encrypted RPC connections from clients, allowing the legacy Windows 7 machine to bypass the strict authentication layer and establish the connection successfully.)

Verification

  1. On the Windows 7 client, navigate to Devices and Printers.
  2. Click Add a printer > Add a network, wireless or Bluetooth printer.
  3. Select the shared Windows 10 printer or type the path manually (e.g., \\192.168.1.10\HP-Printer).
  4. The system should now successfully download the drivers and map the printer without returning the 0x0000011b error.

Lessons Learned

  • While this registry modification restores functionality for legacy environments, disabling RPC authentication technically lowers the security posture of the Windows 10 Print Spooler against lateral movement attacks.
  • For long-term enterprise stability, migrating to standalone Network Printers (connecting the printer directly to the switch and mapping via Standard TCP/IP Port) is highly recommended over host-based sharing, as it entirely bypasses host OS RPC/SMB dependencies.

References

  • Microsoft Security Response Center: PrintNightmare (CVE-2021-1678) RPC Enforcement Mitigations.

Related Articles

  • Currently, there are no related articles in this category. This section will be updated as more internal documentation is published.
Scroll to Top