Fix OSS_PDV_DLL_NOT_LINKED (0X80093027) Printer Error

Quick answer: Run regsvr32 ossrsvp.dll and regsvr32 ossvps.dll in an admin command prompt, then restart the Print Spooler service.

What's going on?

I've seen this error pop up mostly on Windows 10 build 1909 through 22H2, and occasionally on Windows 11. The 0X80093027 error code translates to OSS_PDV_DLL_NOT_LINKED — Windows is trying to load an ASN.1 decoder DLL for your printer driver, but it can't find or link to it. This usually happens after a Windows update replaces or removes the ossrsvp.dll or ossvps.dll files, or after a printer driver update goes sideways.

I've personally tripped over this when upgrading from Windows 10 21H2 to 22H2 — the update nuked the registry entries for those DLLs. The fix is straightforward, but you need to run the right commands in the right order.

Fix steps

1. Open an elevated Command Prompt. Click Start, type cmd, right-click Command Prompt, and select Run as administrator.
2. Re-register the two OSS ASN.1 DLLs. Type these commands, pressing Enter after each:

   regsvr32 ossrsvp.dll
   regsvr32 ossvps.dll

   Wait for a success message for each.
3. Restart the Print Spooler service. In the same command prompt, run:

   net stop spooler && net start spooler

4. Test your printer. Try printing a test page. From Settings > Bluetooth & devices > Printers & scanners, select your printer, click Print a test page.

If the main fix doesn't work

Sometimes the DLLs are missing entirely, not just unregistered. Here's what to try next:

Reinstall the printer driver

1. Open Device Manager, expand Print queues, right-click your printer, and select Delete device.
2. From the manufacturer's website, download the latest driver for your exact printer model and Windows version.
3. Install it, then try printing again.

Manually extract and register the DLLs

If the DLLs aren't in C:\Windows\System32, copy them from another working PC with the same Windows version. Place them in C:\Windows\System32, then run the regsvr32 commands again.

Check for corrupt system files

Run sfc /scannow in an admin command prompt. This can fix underlying system file corruption that might have damaged the OSS DLLs.

Prevention tip

Before installing major Windows updates, create a restore point. This error is almost always triggered by updates, and having a restore point lets you roll back in two minutes. If you're managing multiple machines, automate the DLL registration with a startup script — saves you the headache later.