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

1. You may actually have printer error 0x0000011b instead of stop code 0x0000001B. Confirm the exact number shown on screen before making changes.
2. 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.
3. 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.
4. 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

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

1. On the PC that shares the printer, sign in with an administrator account.
2. 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.
3. Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print.
4. 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.
5. Name the value RpcAuthnLevelPrivacyEnabled.
6. Double-click it and set the value data to 0 or 1 as required for your environment, then click OK.
7. Open Services, find Print Spooler, and choose Restart. You can also open an elevated Command Prompt and run net stop spooler followed by net start spooler.
8. 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.

Exact uninstall steps

1. On Windows 11, open Settings > Windows Update > Update history > Uninstall updates.
2. On Windows 10, open Settings > Update & Security > Windows Update > View update history > Uninstall updates.
3. Select KB5005565 or KB5005573 if present on the affected host or print server.
4. Choose Uninstall, restart the host, then restart the Print Spooler.
5. Reconnect one client and print a test page before touching other devices.

How to keep this from turning into a repeat fix

If rollback is used, treat it as temporary. If the printer is shared from a user PC, consider moving to a more stable connection method such as direct TCP/IP printing or a maintained print server deployment where appropriate.

What registry key fixes the 0x0000011b printer error?

The registry value commonly checked is RpcAuthnLevelPrivacyEnabled under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print.

Exact registry steps

1. Press Windows + R, type regedit, and press Enter.
2. Open HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print.
3. Right-click the right pane and choose New > DWORD (32-bit) Value if the value does not exist.
4. Name it RpcAuthnLevelPrivacyEnabled.
5. Double-click it and enter the required value data, then select OK.
6. Restart the Print Spooler with net stop spooler and net start spooler.

Why one-machine fixes often fail

If the printer is shared from another PC or a print server, changing only the client may do nothing. Check whether other clients can connect to the same share. For related cleanup, our how to remove a printer in Windows and restart the Print Spooler service guides can save time.

How do I add the printer by local port instead?

Adding a shared printer as a Local Port is a standard Windows workaround when the normal shared-printer connection path fails.

Exact Local Port steps

1. Open Control Panel > Devices and Printers.
2. Select Add a printer.
3. Choose The printer that I want isn’t listed.
4. Select Add a local printer or network printer with manual settings.
5. Choose Create a new port.
6. Set Type of port to Local Port.
7. For Port Name, enter the UNC share in this format: \\host\printer.
8. Select the correct printer driver when prompted, then finish setup and print a test page.

What to check if prompts or errors appear

If access is denied, verify the share name from the host PC under Control Panel > Devices and Printers > Printer properties > Sharing. If the driver prompt appears, select the exact printer model if available. If you need the basics, our add a network printer in Windows page covers the standard path.

How do I fix a Windows 0x0000001b blue screen?

Because Microsoft says this bug check code is no longer used within Windows, first confirm the exact stop code shown on the blue screen or in crash details. If you still need to troubleshoot a crash, use standard Windows crash-recovery steps rather than printer fixes.

Safe first steps for a startup crash

1. Boot into Safe Mode if normal startup fails.
2. Open Device Manager and roll back or uninstall the most recent storage, chipset, display, or VPN driver if the crash began after a driver change.
3. Open Command Prompt as administrator and run sfc /scannow.
4. Then run DISM /Online /Cleanup-Image /RestoreHealth.
5. Run chkdsk and schedule it if prompted.
6. Run Windows Memory Diagnostic.

Special cases people search for

On startup: stay in Safe Mode first and reverse recent driver or disk changes. PFN_SHARE_COUNT: that label matches Microsoft’s name for bug check 0x0000001B, but Microsoft also says the code is no longer used within Windows. HP: check printer or scanner drivers only if the crash started after installing them. VPN: remove or roll back the VPN adapter driver if the blue screen began after a VPN client update. If the system keeps looping, use our how to boot into Safe Mode in Windows 11 or Safe Mode in Windows 10 guide, then continue with SFC and DISM repair commands for Windows.

Is it safer to keep the printer update and use another workaround?

Yes, in many cases it is safer to keep updates in place and try a different printer connection method first. Standard alternatives include reconnecting the shared printer, using a Local Port with the printer share path, or moving to direct TCP/IP printing where appropriate.

Prevention note

For a few PCs, Local Port installs are often a practical stopgap. For larger sites, a more stable printer deployment method usually prevents the same connection failure from returning after later changes.

Still not working?

If the first fix did not hold, narrow the failure to one client, one host, or the whole print path. That keeps the next step targeted and avoids changing every PC unnecessarily.

If that didn’t work, use this escalation ladder

1. Only one client fails: remove the printer from Settings or Devices and Printers, then re-add it by Local Port using \\host\printer.
2. Every client fails after the host changes: check the host or print server first, confirm the printer is still shared correctly, and restart Print Spooler with net stop spooler and net start spooler.
3. Windows 7 or older clients are involved: move those devices to direct TCP/IP printing or another supported connection method instead of relying on the shared-printer path.
4. Blue screen still returns: use msconfig for a clean boot, then test again; if needed, move to Reset This PC after saving data.

Verification checklist

1. Reboot the host or affected PC.
2. Restart the Print Spooler.
3. Print a test page from one client.
4. Disconnect and reconnect the printer once.
5. Reboot the client and test again.
6. After the next update cycle, print another test page to confirm the fix survived.

Frequently asked questions

Is 0x0000001b the same as 0x0000011b?

No. They are different codes. If the problem appears while connecting to or using a shared printer, follow the printer branch. If Windows crashes or loops at boot, follow the crash branch instead.

Should I uninstall Windows updates for 0x0000011b?

Only as a short-term recovery step. On Windows 10, use Settings > Update & Security > Windows Update > View update history > Uninstall updates; on Windows 11, use Settings > Windows Update > Update history > Uninstall updates. Try standard printer reconnection and host checks first.

How do I add a shared printer by local port instead?

Go to Control Panel > Devices and Printers > Add a printer > The printer that I want isn’t listed > Add a local printer or network printer with manual settings. Create a Local Port and enter the UNC path as \\host\printer, then finish with the proper driver.