Fix 0X80093022 Copier DLL Error in 5 Minutes
This error stops Windows from linking a copier's OSS ASN.1 DLL. The fix is a registry tweak and a driver reinstall. Takes about five minutes.
This Error Is Annoying — But Fixable
If you're staring at OSS_COPIER_DLL_NOT_LINKED (0X80093022) every time you try to print or scan, I get it. It's one of those errors that makes you want to throw the copier out the window. But here's the thing: the problem isn't the copier. It's Windows forgetting how to talk to it. I've seen this on Sharp, Toshiba, and Ricoh models — mostly on Windows 10 and 11 after an update or a driver install that went sideways.
The Fix: One Registry Edit, One Driver Reinstall
You'll need admin rights on your PC. No way around that. If you're on a work computer and don't have admin, call your IT department and read them the next steps.
Step 1: Uninstall the Copier Driver
- Press Windows + R, type
printmanagement.msc, and hit Enter. This opens Print Management. - In the left pane, click Print Servers > Your PC name > Drivers.
- Find your copier driver in the list (e.g., "Sharp MX-xxxx PCL6" or "Toshiba e-STUDIOxxx"). Right-click it and select Remove driver package.
- When it asks if you're sure, click Yes. Wait for the "Removal complete" message.
- After removing the driver package, uninstall the printer too: right-click the printer in Printers (same left pane) and choose Delete.
- Close Print Management.
What you should see: The printer disappears from your Devices and Printers folder. No more old drivers hanging around.
Step 2: Fix the Registry
This is the part that actually solves the DLL linking issue. The error 0X80093022 means Windows can't load the OSS ASN.1 parser (ossrsvp.dll). The registry key that tells Windows where to find it gets corrupted or lost.
- Press Windows + R, type
regedit, and hit Enter. Click Yes if UAC asks. - Go to this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ossrsvp - If that key doesn't exist, you need to create it. Right-click Services > New > Key and name it
ossrsvp. - Inside the
ossrsvpkey, look for a string value named ImagePath. If it's missing or wrong, create or modify it:
Right-click empty space > New > String Value, name itImagePath, then double-click it and set its value to:
%SystemRoot%\System32\ossrsvp.dll - Next, check this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider - If it's missing, create it. Inside, create a DWORD (32-bit) value named DisableServerSidePrinting and set it to
0. - Close Registry Editor.
What you should see: The ossrsvp service now points to the correct DLL. No more "DLL not linked" nonsense.
Step 3: Restart the Print Spooler
- Press Windows + R, type
services.msc, and hit Enter. - Find Print Spooler in the list. Right-click it and select Stop.
- Wait 10 seconds, then right-click it again and choose Start.
- Close Services.
What you should see: The spooler restarts clean. No error messages.
Step 4: Reinstall the Copier Driver
- Download the latest driver from your copier manufacturer's website. Don't use the one on the CD that came with the machine — it's probably old.
- Run the installer. When it asks for connection type, choose Network (unless it's a USB copier, then USB).
- Follow the on-screen prompts. For network copiers, you'll usually enter the printer's IP address.
- Once installed, open Devices and Printers, right-click your copier, and select Print Test Page.
What you should see: A test page prints without error. If you still get 0X80093022, you missed the registry step — go back and double-check the ossrsvp key.
Why This Works
The error 0X80093022 is a Windows side issue. The OSS ASN.1 parser (ossrsvp.dll) is a system component that some copier drivers use for encoding print data. When the registry link breaks — usually after a Windows update or a botched driver install — Windows can't find the DLL. The copier driver then throws the "DLL not linked" error. By fixing the registry and reinstalling the driver fresh, you restore that link. No magic, just plumbing.
Less Common Variations
Variation 1: The DLL Is Missing Entirely
Sometimes ossrsvp.dll goes missing after a Windows feature update. Check in C:\Windows\System32\ for the file. If it's not there, you can restore it from a working PC (copy it from C:\Windows\System32\) or run sfc /scannow in an admin command prompt. SFC will replace missing system files, including this one.
Variation 2: Error Only on Network Printers
If the error only pops up when printing over a network, the problem might be the Client Side Rendering Print Provider registry key we fixed above. Some copier drivers need that key set to 0. If you skip that step, you'll still get the error on network prints.
Variation 3: Multiple Copiers, One PC
I've seen this on PCs with two different copier brands installed. The fix is the same — uninstall all copier drivers, do the registry fix, then reinstall only the one you need. Don't stack drivers.
Prevention: Don't Let It Come Back
- Pause feature updates on Windows 10/11 for at least 30 days. This gives Microsoft time to fix any DLL-breaking bugs. Go to Settings > Update & Security > Windows Update > Pause Updates.
- Always use the latest driver from the copier's website, not the one Windows Update offers. Windows Update drivers are often generic and cause this issue.
- Back up your registry before installing major driver updates. Export
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servicesto a .reg file. Takes 10 seconds, saves you hours. - If you're a sysadmin, push the registry fix via Group Policy to all machines that use the copier. Saves everyone the headache.
That's it. Five minutes, maybe ten if you're slow. The error won't come back unless you break the registry again. You're welcome.
Was this solution helpful?