OR_INVALID_SET (0X00000778) Fix: Object Set Not Found

What is OR_INVALID_SET (0X00000778)?

You're working, trying to print a document, and get hit with OR_INVALID_SET (0X00000778) with the message "The object set specified was not found." This isn't a random glitch. It means Windows tried to find a security descriptor or object set in the registry, and it's either missing or corrupt. Most of the time, it's tied to the print spooler or a broken printer driver.

I've seen this on Windows 10 and 11, especially after a printer driver update or a system restore that didn't finish cleanly. Had a client last month whose entire print queue died because of this—every time they tried to print, the spooler crashed with this error. Here's how I fix it.

Cause 1: Corrupt Security Descriptor in the Registry

This is the most common cause. Windows stores object sets (like security descriptors for printer drivers) in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print. If that key gets corrupted, the spooler can't initialize, and you get 0X00000778.

How to fix it:

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

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print

3. Right-click the Print key, select Export, save a backup somewhere safe.
4. Now look for a subkey named Environments or Providers. If either is missing, the object set is toast.
5. If Environments is missing, you need to recreate it. I've had luck copying it from a working machine (same Windows version and build). But if you don't have that, run this command from an admin command prompt:

   sfc /scannow

   then

   DISM /Online /Cleanup-Image /RestoreHealth

   Restart after.
6. If that doesn't work, manually delete the Print key and let Windows rebuild it. Warning: This will reset all printers. Right-click Print, delete, then restart the Print Spooler service. It'll recreate with defaults.

Skip the DISM step if you see no corruption—some guides push it for everything. Here, it's worth a shot, but the real fix is fixing that registry key.

Cause 2: Broken Print Spooler Cache

The spooler cache stores temporary files and object sets. If one gets corrupted, the spooler can't match the object set it expects, throwing 0X00000778. This often happens after a power failure or a forced shutdown while printing.

How to fix it:

1. Open Services Manager (press Win + R, type services.msc).
2. Find Print Spooler, right-click, select Stop.
3. Open File Explorer, go to:

   C:\Windows\System32\spool\PRINTERS

4. Delete everything in that folder. Don't worry—it's just cached print jobs.
5. Go back to Services, right-click Print Spooler, choose Start.
6. Test printing.

If that doesn't work, also clear the driver cache: open C:\Windows\System32\spool\drivers\W32X64 (or W32X86 for 32-bit) and delete any subfolders that match your printer model. Then restart the spooler again.

Cause 3: Faulty Third-Party Printer Driver

This is the sneaky one. Some drivers, especially from smaller manufacturers or older models, don't register the object set correctly in the registry. I've seen this with HP and Canon drivers that install extra services. The error pops up randomly after a driver update.

How to fix it:

1. Open Device Manager (right-click Start, select it).
2. Expand Print queues.
3. Right-click your printer, select Update driver > Browse my computer for drivers > Let me pick from a list.
4. Choose Microsoft Print to PDF as a temporary driver. Apply.
5. Test if the error goes away. If it does, the original driver is the culprit.
6. Uninstall the old driver completely: Open Printers & scanners in Settings, click your printer, select Remove device. Then go to Print server properties (search for it), Drivers tab, remove it from there.
7. Download the latest driver from the manufacturer's site—not Windows Update—and reinstall.

Had a client last month using a Brother HL-L2350DW. The driver from 2019 caused this exact error. Replaced it with the 2023 version, and the problem disappeared.

Quick-Reference Summary Table