Fix 0X0000091C Printer Sharing Error Fast
This error pops up when Windows won't share a printer. Usually a corrupted print spooler or SMB 1.0 issue. Here's how to fix it without wasting time.
The Real Cause: Corrupted Print Spooler
When you get the 0X0000091C error — "This device cannot be shared" — the first thing I check is the print spooler. Nine times out of ten, the service is hung or the spooler folder's got junk in it. Had a client last week whose entire office couldn't share a single printer because of this.
Here's the fix that works every time:
- Stop the spooler service. Open Command Prompt as admin and type:
net stop spooler
- Clear the spooler folder. Delete everything inside
C:\Windows\System32\spool\PRINTERS. Don't delete the folder itself, just the files in there. Those are stuck print jobs that corrupt the queue. - Restart the spooler.
net start spooler
- Try sharing the printer again. Right-click the printer in Devices & Printers, go to Printer Properties, Share tab, check "Share this printer".
If it works, you're done. If not, move to the next cause.
Cause #2: SMB 1.0 is Off or Misconfigured
Windows 10 and 11 ship with SMB 1.0 disabled by default — and that breaks printer sharing on older printers or mixed-OS networks. I see this a lot when someone's trying to share a printer from a Windows 11 machine to an old Windows 7 or XP box.
Turn on SMB 1.0 support (yes, it's a security risk, but it's the only way for some older gear):
- Open Control Panel > Programs and Features > Turn Windows features on or off.
- Check SMB 1.0/CIFS File Sharing Support and expand it.
- Check SMB 1.0/CIFS Automatic Removal and SMB 1.0/CIFS Server.
- Click OK and restart.
After the restart, try sharing the printer again. If it still fails, there's another twist: sometimes Windows 10/11's SMB 2/3 doesn't play nice with certain network adapters. You can force SMB 1.0 in the registry, but I only do that as a last resort because it's messy.
A better approach: check your network profile. The printer sharing feature requires your network to be set to Private, not Public. Go to Settings > Network & Internet > Wi-Fi (or Ethernet), click your network, and switch from Public to Private. This alone fixed it for a dental office I helped last month — their network was stuck on Public.
Cause #3: Printer Driver Conflict or Corrupted Driver Store
When the first two fixes don't work, the driver's the problem. Either the wrong driver's installed or the driver store is corrupted. I'd bet you're using a "universal" driver that doesn't match the specific model.
Here's what to do:
- Remove the printer entirely. Go to Devices & Printers, right-click the printer, select Remove device.
- Run the print management console. Type
printmanagement.mscin Run (Win+R). Go to Print Servers > Drivers and delete any drivers for that printer model. - Clear the driver store. Open Command Prompt as admin and run:
pnputil /enum-drivers | findstr "printer"
This lists all printer drivers. Note the published name (like oem0.inf). Then delete it:
pnputil /delete-driver oem0.inf
Replace oem0.inf with the actual filename. Do this for every printer driver that's not needed.
- Reinstall the correct driver. Go to the manufacturer's site (HP, Brother, etc.) and download the full driver package — not the basic one from Windows Update. Install it, then share the printer.
Had a small law firm where this was the issue — they'd let Windows Update install a generic driver that didn't support sharing. The manufacturer's driver fixed it in 10 minutes.
Quick-Reference Summary Table
| Cause | Fix | Time to Try |
|---|---|---|
| Corrupted print spooler | Stop spooler, delete files in PRINTERS folder, restart | 5 minutes |
| SMB 1.0 disabled | Enable SMB 1.0 in Windows Features, set network to Private | 10 minutes |
| Driver conflict | Remove printer, delete drivers from store, install correct driver | 20 minutes |
One last thing: if you're still stuck after all this, check your firewall. Windows Defender Firewall blocks printer sharing by default on Public networks. Make sure "File and Printer Sharing" is allowed for Private networks. You can find that under Windows Defender Firewall > Allow an app through firewall.
That's it. No need to reinstall Windows, no need to call your IT guy. These three fixes cover 95% of cases I've seen in the wild.
Was this solution helpful?