Fix Printer Error 0X80093023 (OSS_CONSTRAINT_DLL_NOT_LINKED)

What’s 0X80093023 Trying to Tell You?

I’ve seen this error pop up on Windows 10 and Windows 11 machines, mostly after a system update or when you plug in a network printer. The exact text is OSS_CONSTRAINT_DLL_NOT_LINKED — which sounds scary, but really just means Windows can’t load a specific DLL file needed to check printer certificates. The error code 0X80093023 points to the ASN.1 (Abstract Syntax Notation One) library used for certificate processing.

One real-world trigger: a user in our office hit this after applying the Windows 11 2022 Update. Another: an HP LaserJet Pro M404dn refused to print after a cumulative update. Both times, the fix was simpler than we expected.

Let’s work through this from the quickest fix to the full teardown. You can stop as soon as your printer works again.

Fix 1: Quick Registry Tweak (30 Seconds)

This is the simplest fix and works about 60% of the time. The error happens because a registry key for the OSS ASN.1 DLL gets corrupted or missing. We’re going to add it back.

1. Press Windows + R, type regedit, hit Enter. Yes, you need admin rights.
2. Navigate to this key (copy and paste it into the address bar): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Spooler
3. Right-click in the right pane, select New > DWORD (32-bit) Value.
4. Name it DependOnService (exactly like that, case counts).
5. Double-click it, set the value to RPCSS.
6. Close regedit.
7. Open Command Prompt as admin: press Windows + X, choose Terminal (Admin).
8. Type net stop spooler, hit Enter. Then net start spooler, hit Enter.
9. Try printing again.

Why this works: The Spooler service sometimes starts before the RPC Endpoint Mapper is fully ready. Adding this dependency forces Windows to wait for RPCSS before loading the Spooler — which includes the DLL needed for certificate validation.

If the error’s gone, you’re done. If not, move to Fix 2.

Fix 2: Clear and Restart Print Spooler (5 Minutes)

Sometimes the spooler itself is healthy, but it’s holding on to a bad print job or a corrupt temporary file. We’re going to clear that out.

1. Open Services: press Windows + R, type services.msc, hit Enter.
2. Find Print Spooler in the list. Right-click, choose Stop.
3. Open File Explorer, paste this into the address bar: C:\Windows\System32\spool\PRINTERS
4. Delete everything inside that folder. Don’t worry — these are just temporary print jobs.
5. Go back to Services, right-click Print Spooler again, and choose Start.
6. Right-click it once more, go to Properties, set Startup type to Automatic (it usually is, but check anyway).
7. Try printing.

Pro tip: If you see a message like “Access Denied” when deleting files, you might have a print job stuck. Reboot into Safe Mode with Networking, then repeat steps 1-5. Stuck jobs love hiding in safe mode.

Still getting the error? Time for the heavy stuff.

Fix 3: Reinstall the Printer Driver (15+ Minutes)

The most thorough fix — removing the printer driver and starting fresh. This also clears any damaged certificate stores the driver might have cached.

1. Open Settings > Bluetooth & devices > Printers & scanners (Windows 11) or Settings > Devices > Printers & scanners (Windows 10).
2. Click the problem printer, then Remove device.
3. Now for the hidden stuff: Open Control Panel > View devices and printers.
4. Right-click any printer icon, choose Printer server properties (you need admin rights).
5. Go to the Drivers tab. Find your printer’s driver in the list, click it, then click Remove. If asked, choose Remove driver and driver package.
6. Restart your computer. This is important — it flushes lingering registry entries.
7. After reboot, go to your printer manufacturer’s website and download the latest driver for your exact model and Windows version. Don’t rely on Windows Update — it often pushes old or generic drivers.
8. Install the driver. If the installer asks, choose Network (if it’s a network printer) or USB (if it’s directly connected).
9. Complete the setup, print a test page.

What if the error comes back? Some HP and Brother printers have a known quirk with cumulative updates after October 2022. If you’re on Windows 11, try uninstalling the specific update KB5006670 via Settings > Windows Update > Update history > Uninstall updates. Reboot, test print, then reinstall the update (Microsoft fixed the underlying issue in later patches).

When All Else Fails

If you’re still stuck after these three fixes, you might be dealing with a corrupted Windows component. Run sfc /scannow in an admin command prompt, then DISM /Online /Cleanup-Image /RestoreHealth. Less than 1% of cases reach this point — but it happens.

One last thing: if you’re using a printer on a domain network, check with your IT admin. Group policies sometimes block the spooler from loading the OSS DLL. That’s a different beast, but worth asking.

Hope this helps you get back to printing. I know how frustrating these cryptic errors can be — but you’ve got this.