Is error 0x0000007c related to error 0x0000011b?

Yes, both errors are related to Windows security updates that tightened restrictions on network printer connections and RPC communication.

Does changing the RpcAuthnLevelPrivacyEnabled registry key pose a security risk?

Setting this key to 0 reduces the RPC security level for printing, which bypasses certain security mitigations. Use this workaround only in trusted local network environments.

Why does local printing work if network printing fails?

Local printing communicates directly via USB or local ports, whereas network printing relies on RPC and print spooler network protocols that are restricted by recent security updates.

Will future Windows updates fix this permanently without registry changes?

Microsoft has periodically released updates addressing print deployment issues, but applying administrative registry workarounds remains the standard immediate fix until official patches are fully integrated.

Can I use an IP port instead of a shared printer path to bypass this?

Yes, configuring a Standard TCP/IP port pointing to the host computer IP address and sharing the printer via local methods can sometimes bypass RPC connection restrictions.

WiFi & NetworkWorth attentionAbout 10 min

Windows Printer Error 0x0000007c: Causes and Fixes

Quick answer

Windows printer error 0x0000007c occurs when a client computer cannot connect to a shared network printer due to security updates restricting RPC communication. Fix this error by modifying the RpcAuthnLevelPrivacyEnabled registry key on the affected machine.

Published 10 October 2026

What this means

Error 0x0000007c means your computer cannot reach a shared network printer. Windows security updates changed how your machine talks to the printer host by restricting remote procedure call communication for print spoolers.

The printer itself is not broken. Local printing on the host machine still works fine. The failure sits entirely in the network path between your computer and the host.

This error happens when your computer uses a different architecture or driver version than the host. A network profile set to public will also block the connection.

Common causes

Strict RPC connection settings enforced by Windows updates
Mismatch in RpcAuthnLevelPrivacyEnabled registry settings between client and host
Windows Firewall blocking print spooler communication
Outdated printer drivers on the client machine
Network profile set to Public instead of Private
SMB signing or authentication protocol mismatches

What to check first

1Verify the printer works correctly when connected directly to the host PC
2Confirm both computers are on the same local network
3Check that printer sharing is still enabled on the host machine

Step-by-step fix

1
Configure RpcAuthnLevelPrivacyEnabled Registry Key
On the client or host computer, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print. Create or modify a DWORD value named RpcAuthnLevelPrivacyEnabled and set it to 0.
Incorrectly editing the registry can cause system instability. Back up the registry before proceeding.
2
Check Network Profile Type
Ensure that the network connection profile on both the client and host machines is set to Private rather than Public, as Public profiles block file and printer sharing.
3
Restart the Print Spooler Service
Open Windows Services, locate Print Spooler, right-click, and select Restart on both the host and client computers.
4
Install Matching Print Drivers
Download and install the exact same version of the manufacturer print driver on the client computer that is currently installed on the host computer.
5
Adjust Windows Firewall Settings
Verify that File and Printer Sharing is allowed through the Windows Defender Firewall on both machines.

When to contact a professional

Call your network administrator if your computer is on an Active Directory domain where Group Policy overrides local registry changes. You also need IT help if security policies block you from altering remote procedure call authentication levels. Forcing these changes against network rules will break your connection entirely.

Questions people ask

Is error 0x0000007c related to error 0x0000011b?: Yes, both errors are related to Windows security updates that tightened restrictions on network printer connections and RPC communication.
Does changing the RpcAuthnLevelPrivacyEnabled registry key pose a security risk?: Setting this key to 0 reduces the RPC security level for printing, which bypasses certain security mitigations. Use this workaround only in trusted local network environments.
Why does local printing work if network printing fails?: Local printing communicates directly via USB or local ports, whereas network printing relies on RPC and print spooler network protocols that are restricted by recent security updates.
Will future Windows updates fix this permanently without registry changes?: Microsoft has periodically released updates addressing print deployment issues, but applying administrative registry workarounds remains the standard immediate fix until official patches are fully integrated.
Can I use an IP port instead of a shared printer path to bypass this?: Yes, configuring a Standard TCP/IP port pointing to the host computer IP address and sharing the printer via local methods can sometimes bypass RPC connection restrictions.

Was this guide helpful?

Not the problem you have?

Switch off and unplug a printer before reaching inside it. Steps that can damage hardware or affect a warranty are flagged above. If your machine is still under warranty, or the fault involves the power supply or internal electronics, contact the manufacturer or a qualified technician instead. Full disclaimer.

What this means

Common causes

What to check first

Step-by-step fix

Configure RpcAuthnLevelPrivacyEnabled Registry Key

Check Network Profile Type

Restart the Print Spooler Service

Install Matching Print Drivers

Adjust Windows Firewall Settings

When to contact a professional

Questions people ask

Related guides