Printer Error 0X80093025: OSS Comparator Code Not Linked Fix
This error shows up when you add a printer on Windows 10/11 and the driver fails to link an ASN module. Here's how to fix it in a few steps.
When Does This Error Appear?
You're trying to add a printer on Windows 10 or 11. Maybe it's a networked HP LaserJet, a Brother, or a Canon. You click "Add Printer" in Settings, it searches, then pops up with error 0X80093025. The full message says something like "OSS_COMPARATOR_CODE_NOT_LINKED". It stops the driver from installing. This happens most often with older printers that use custom drivers, especially on newer Windows builds after a feature update.
What Causes It?
The short answer: Windows can't verify the driver's digital signature correctly. The error comes from the Microsoft ASN (Abstract Syntax Notation) parser that checks driver code. When it compares the signing certificate's hash, it finds a mismatch. The driver itself may be fine, but Microsoft's security check fails because the driver wasn't signed with the latest SHA-2 standard, or the signing chain is broken.
This isn't a hardware problem. Your printer is fine. The cable works. The network port responds. But Windows says "nope, unsafe" and blocks the install.
Fix: Step-by-Step
Step 1: Download the Latest Driver
Don't use the driver that Windows auto-fetches. Go to the printer manufacturer's website. Look for the model and download the full driver package, not the basic one. For example, for HP use the HP Smart app or Universal Print Driver. For Brother, get the full driver & software suite. Save it to your Desktop.
What you should see: A file ending in .exe or .msi, around 50-200 MB.
Step 2: Run the Driver Installer as Admin
Right-click the downloaded file. Choose Run as administrator. Click Yes if Windows asks permission. Let it install. Usually this replaces the broken driver.
What you should see: The installer starts, asks you to agree to terms, then copies files. You might see "installing driver" with a progress bar.
Step 3: Delete the Old Driver Cache (If Still Fails)
If the error comes back, the old cached driver is causing trouble. Open Device Manager (right-click Start > Device Manager). Find your printer under Print queues. Right-click it and choose Remove device. Check the box that says "Delete the driver software for this device" if it shows up. Click OK.
What you should see: The printer disappears from the list.
Step 4: Clear the Driver Store
This step forces Windows to forget the bad driver. Open Command Prompt as admin (search "cmd", right-click, Run as administrator). Type:
pnputil /enum-drivers | findstr /i "printer_name"Replace printer_name with your printer's model name. It shows a list of driver packages. Look for the Published Name, like oem0.inf. Then delete it with:
pnputil /delete-driver oem0.infIf you see errors, that's normal — just skip to the next step.
What you should see: "Driver package deleted successfully" or a message that it's in use.
Step 5: Install the Driver Again
Run the installer from Step 1 again. This time it should work. Follow the on-screen prompts. When it asks for connection type, choose Network or USB depending on your setup.
What you should see: The printer shows up in Devices & Printers after completion. No error.
If It Still Fails
Some older drivers are not signed correctly for Windows 10 version 2004 or later. In that case, you have two options:
- Option 1: Boot into Safe Mode and install the driver. This bypasses some signature checks. Restart your PC, hold Shift, click Restart, then Troubleshoot > Advanced options > Startup Settings > Restart > press 4 for Safe Mode. Install the driver there.
- Option 2: Use a different printer driver. For example, the Microsoft IPP Class Driver works with many network printers. In Settings > Bluetooth & devices > Printers & scanners > Add device, Windows might find a generic driver that works. It won't have all features, but basic printing works.
- Option 3: Update Windows. Go to Settings > Windows Update > Check for updates. Sometimes Microsoft pushes a fix for driver signing. Install all pending updates, restart, and try again.
If none of this works, the printer itself might be too old. Consider replacing it with a newer model that supports modern Windows. I've seen this with printers from 2010 or earlier — they just weren't built for SHA-2 signing.
Was this solution helpful?