0x0000001b: BSOD vs printer error and the right fix
These are different issues: one is a Windows blue-screen stop code, while the other is usually a shared-printer connection error, so address the one that matches what you see. If the screen is blue and Windows crashes, use the blue-screen branch. If the message says Operation failed with error 0x0000011b while connecting to a network printer, use the shared-printer branch.
Start with the symptom in front of you: if Windows crashes or restarts unexpectedly, stay on the stop-code path. If the problem appears only when adding or using a shared printer, use printer troubleshooting instead. If you need a wider workflow, see our Windows printing troubleshooting guide, Registry Editor steps in Windows, or BSOD troubleshooting on Windows 10 and 11.
What does 0x0000001b mean on Windows?
0x0000001B is a Windows bug check value named PFN_SHARE_COUNT. Officially, the bug check value is 0x0000001B, it indicates that a memory management page frame number (PFN) database element has a corrupted share count, and Microsoft also notes that this bug check code is no longer used within the Windows operating system. (Microsoft Learn)
How people mix up 0x0000001B and 0x0000011b
The mix-up usually starts with one missing zero. A stop code is written as 0x0000001B. The printer error is usually shown as 0x0000011b. One appears during a crash or startup problem. The other appears when adding or using a shared printer.
The fast way to tell which one you have
- Blue screen, reboot loop, startup crash: treat it as the stop-code branch.
- Printer install or print job fails: treat it as the printer branch.
- Message includes “Operation failed with error
0x0000011b”: use shared-printer troubleshooting. - No printer involved at all: do not start with printer registry edits.
Likely causes, ranked by what I see most often
Most searches for this code are actually about the printer-side error with the extra zero missing. Use the symptom to decide which branch to follow first.
Ranked causes
- You may actually have printer error
0x0000011binstead of stop code0x0000001B. Confirm the exact number shown on screen before making changes. - A shared-printer connection may be failing on the host, print server, or client connection path. Check whether the printer is shared from another Windows PC or from a print server, and test whether other clients can still connect.
- The printer connection saved on the client may be stale or damaged. Removing the printer and adding it again, including by Local Port if needed, is a standard Windows repair step.
- You may have a real blue-screen fault. In that case, use standard crash troubleshooting such as Safe Mode, reversing recent driver changes, and built-in system checks.
Which fix path fits your setup?
The least risky fix depends on the symptom. If Windows crashes, stay on the blue-screen path. If printing fails, check whether the issue affects one client, one shared host, or all clients using the same printer.
One-page decision table
| Symptom pattern | Environment | Most likely branch | Safest first workaround | Why this is the low-risk move |
|---|---|---|---|---|
| Blue screen at boot or during startup | Any Windows 10 or Windows 11 PC | Stop-code branch | Safe Mode, driver rollback, then sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth | Avoids changing print settings for a crash that may have nothing to do with printing |
Operation failed with error 0x0000011b when connecting to a shared printer | Home or small-business workgroup, one shared PC | Shared-printer branch | Check the shared host, restart Print Spooler, then remove and reconnect the printer | Starts with standard Windows checks before deeper changes |
| Several PCs fail after a change on the shared host | Workgroup, few client PCs, one host PC | Host-side print break | Fix the shared host first, then test one client | Client-only changes usually do not help if the source share is the problem |
| Many users fail from the same shared printer | Domain with print server | Server-side enforcement or connection issue | Test with one affected client, then repair the server-side print path or redeploy the printer connection | Keeps changes targeted instead of editing every workstation |
| One client still fails but others print | Domain or workgroup | Client connection path or stale install | Remove and re-add printer by Local Port using \\host\printer | Targets the broken client path without changing the host for everyone |
| Legacy clients such as Windows 7 in the mix | Mixed environment | Compatibility problem around shared printing | Use direct TCP/IP printing or another supported connection method where possible | Reduces repeated shared-printer connection failures |
Why am I seeing error 0x0000011b when printing?
If your message is 0x0000011b, you are dealing with a printer connection problem rather than the stop code above. Start by checking whether the printer is shared from another Windows PC or through a print server, because the next steps depend on where the connection fails. (ninjaone.com; wintips.org)
If that fits, start with the host or print server registry path
- On the PC that shares the printer, sign in with an administrator account.
- Press Windows + R, type regedit, and open Registry Editor. If you want screenshots for this part, use our guide to opening Registry Editor in Windows.
- Go to
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print. - In the right pane, look for a value named RpcAuthnLevelPrivacyEnabled. If it does not exist, right-click the right pane and choose New > DWORD (32-bit) Value.
- Name the value RpcAuthnLevelPrivacyEnabled.
- Double-click it and set the value data to 0 or 1 as required for your environment, then click OK.
- Open Services, find Print Spooler, and choose Restart. You can also open an elevated Command Prompt and run
net stop spoolerfollowed bynet start spooler. - On the client PC, remove the failed printer connection and add it again.
What the 0 and 1 settings do
RpcAuthnLevelPrivacyEnabled is the registry value commonly checked for this type of shared-printer problem under the Print branch shown above. Before changing it, back up the registry or create a restore point. If you are not comfortable editing this path manually, review our Windows Registry backup and restore guide first.
When this is acceptable and when it is a bad fit
This is a reasonable step when the printer is shared from a trusted PC and you can control both the host and the client. It is a weaker fit for a larger managed environment, where it is usually better to confirm the server-side print configuration and test an alternative client connection method first.
Should I uninstall KB5005565 or KB5005573?
Uninstalling a recent update may restore printing in some setups, but it is usually better to try standard connection and spooler checks first. If the problem began right after an update and other printer fixes do not help, rollback can be a short-term recovery step while you test a longer-term printer setup. (dirteam.com)
When rollback makes sense
Rollback makes the most sense when one shared host changed and clients stopped printing immediately afterward. In a managed environment, test on one affected machine first and document the result before removing updates more broadly.
