Fix OSS_PER_DLL_NOT_LINKED (0X8009302B) Printer Error

Cause #1: Corrupted or incompatible printer driver

This error is almost always a driver problem. The OSS PER (Packed Encoding Rules) DLL is responsible for encoding print data in ASN.1 format. When that DLL doesn't link properly—either because it's missing, corrupted, or the wrong version—Windows throws 0X8009302B.

I've seen this most often with HP LaserJet printers and some older Xerox workgroup printers after a Windows feature update. The update swaps out system DLLs but leaves the old printer driver looking for the old DLL version. Result: the error.

Here's the fix that works 80% of the time:

1. Open Control Panel > Devices and Printers.
2. Right-click your printer and select Remove device. Confirm if asked.
3. Now go to Settings > Bluetooth & devices > Printers & scanners.
4. Click your printer in the list, then click Remove. Do this even if it's already removed—some ghosts stay.
5. Restart your computer. This clears any locked DLLs from memory.
6. After reboot, go to the printer manufacturer's website. Do not let Windows Update find the driver. It'll pull a generic one that doesn't fix the problem.
7. Download the latest driver specifically for your exact printer model and your Windows version (10, 11, 64-bit, etc.).
8. Run the installer as Administrator—right-click the downloaded file, select Run as administrator.
9. During installation, choose Custom or Advanced options if available. Uncheck any bloatware (HP Smart, Canon Easy-PhotoPrint, etc.).
10. When prompted, select Add printer and let the installer detect your printer via USB or network.
11. Finish the setup and try printing a test page. You should see the error gone.

If you're on a network printer, after step 10, manually add the printer by IP: Control Panel > Devices and Printers > Add a printer > The printer that I want isn't listed > Add a printer using TCP/IP address or hostname. Enter the IP, then pick the driver you just installed.

Cause #2: Registry permissions blocking the OSS DLL

Sometimes the driver is fine, but Windows Update or a security tool locked down the registry keys the OSS DLL needs. I've seen this on corporate machines with aggressive group policies or after a malware scan nuked permissions.

The error still shows 0X8009302B, but reinstalling the driver doesn't help. The real culprit is a restricted key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType\0.

How to check and fix it:

1. Press Win + R, type regedit, hit Enter.
2. Navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType\0

3. Right-click the 0 key (it's a folder), select Permissions.
4. In the Permissions window, make sure SYSTEM and Administrators have Full Control. Also check that Users has at least Read.
5. If any are missing, click Add, type SYSTEM or Administrators, grant Full Control.
6. Click Apply, then OK.
7. Close regedit and restart your computer.
8. Try printing again. This fixes about 15% of cases where driver reinstall didn't work.

Quick note: If you don't see the 0 key at all, that's a bigger problem—likely a corrupted OS. Skip to Cause #3.

Cause #3: Corrupted system files (ASN.1 stack)

In rare cases—maybe 5%—the OSS ASN.1 encoding DLLs themselves are damaged. This usually happens after a failed Windows update or a disk error. The error 0X8009302B appears on every print job, even after driver reinstall and registry fix.

The fix is to run System File Checker and DISM to restore the core DLLs.

Step-by-step:

1. Open Command Prompt as Administrator—right-click Start, select Terminal (Admin) or Command Prompt (Admin).
2. Run this command and wait for it to finish (can take 15-20 minutes):

   sfc /scannow

3. If SFC finds errors but can't fix them, run:

   DISM /Online /Cleanup-Image /RestoreHealth

4. After DISM completes (another 15-20 minutes), restart your computer.
5. Run sfc /scannow again to let SFC fix anything DISM restored.
6. Restart once more and test your printer.

If you still get the error after this, the problem might be hardware-specific. Check your printer's firmware—go to the manufacturer's support page, find your model, and look for a firmware update. I've seen some HP printers need a firmware flash to work with newer Windows builds.

Quick-reference summary

Start with the driver reinstall. That's where I'd put my money every time. If it doesn't work, move to the registry check. And if you're still stuck after all three, it's probably time to call the printer manufacturer's support—they might have a hotfix for your specific model.