7 July 2026
A shared printer connected through an Active Directory domain stopped working after a workstation was upgraded from Windows 10 to Windows 11.
The printer displayed the following error:
Your printer has experienced an unexpected configuration problem: 0x80040154
In this case, the problem was caused by the RPC connection settings used by Windows 11. The solution was to configure RPC connection settings and allow the protocol expected by the domain print server.
For similar workstation, operating-system or peripheral connection problems, Computer Support can help identify whether the issue originates from the local device, its configuration or another part of the IT environment.
Shared Printer Symptoms After the Windows 11 Upgrade
The printer had previously worked through a Windows domain-joined server. After the workstation was upgraded from Windows 10 to Windows 11, the shared printer would no longer connect.
Several troubleshooting steps were completed before the RPC connection settings were identified as the cause. These included:
- Resetting the Print Spooler folder
- Removing all printer drivers and printers from the workstation
- Running the following command: DISM /Online /Cleanup-Image /RestoreHealth
These steps did not resolve error 0x80040154.
When standard printer troubleshooting does not resolve the problem, IT Helpdesk Services can help investigate Windows services, drivers, permissions, workstation settings and connection errors.
Why the Domain Shared Printer Stopped Working
Windows 11 restricts certain print traffic by disabling legacy RPC over Named Pipes by default. Windows 10 does not apply the same restriction by default, so print traffic using this protocol may continue to work before the upgrade.
Installing the printer through direct IP mapping may still work because this method bypasses the domain print spooler architecture.
However, a printer connected through a domain share relies on the domain print server and may fail because of RPC protocol, name resolution, or security-handshake requirements.
In environments where shared printers depend on a domain server, Server and Network Support can help assess print-server communication, permissions, name resolution and network connectivity.
To restore the connection, Windows 11 must be configured to use the RPC protocol expected by the domain print server.
How to Configure RPC Connection Settings
You can configure RPC connection settings on the local computer or apply the setting through domain Group Policy.
Follow these steps:
- Press Windows key + R.
- Type: gpedit.msc
- Press Enter.
- Navigate to: Computer Configuration > Administrative Templates > Printers
- Locate and double-click Configure RPC connection settings.
- Set the policy to Enabled.
- In the options menu, select RPC over named pipes.
- Click Apply, followed by OK.
- Open: services.msc
- Restart the Print Spooler service.
After the service restarts, reconnect to the domain-shared printer and confirm that it is working correctly.
Changes to local or domain Group Policy should be completed by an administrator who understands the existing network and print-server configuration.
Restoring Shared Printer Access in Windows 11
When a domain-shared printer stops connecting after a Windows 11 upgrade, removing drivers or resetting the Print Spooler may not resolve the issue.
In this case, the printer connection was restored by enabling Configure RPC connection settings and selecting RPC over named pipes. This allowed the Windows 11 workstation to use the protocol configuration expected by the domain print server.
For businesses managing upgrades across multiple devices, Managed IT Services can provide ongoing support for workstations, shared printers, servers and other connected systems.