Fix ERROR_REPARSE_OBJECT (0X000002F3) on Printer Install
Stuck printer install? ERROR_REPARSE_OBJECT means Windows sees a leftover symbolic link from a previous failed driver. Delete the registry key or use Device Manager to clear it.
You try to install a printer — maybe an HP LaserJet or a Brother — and Windows throws ERROR_REPARSE_OBJECT (0X000002F3). It's annoying because the printer is fine, but Windows can't finish the job. Let me show you what's really going on and how to fix it in 5 minutes.
Quick Fix: Delete the Stale Reparse Point
The error means Windows found a leftover symbolic link (reparse point) from a previous printer driver that didn't uninstall properly. The easiest way is to remove it from the registry. Here's how:
- Press Win + R, type
regedit, hit Enter. - Go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers - Look for a key with the printer name you're trying to install. If you see a key with weird data — like
ReparseTagorSymbolicLinkValue— that's the culprit. - Right-click that key and delete it. Yes, delete the whole thing.
- Close regedit, restart the Print Spooler service (
net stop spoolerthennet start spoolerin an admin command prompt), and try the install again.
That's it. The install should go through now.
Alternative: Clean the Driver via Device Manager
If you're not comfortable with the registry, use Device Manager:
- Open Device Manager (right-click Start > Device Manager).
- Click View > Show hidden devices.
- Expand Printers and Print queues.
- Look for any ghosted (grayed out) printer entries. Right-click each one and choose Uninstall device — check the box Delete the driver software for this device.
- Also check Software devices — sometimes the reparse point hides there.
- Restart the print spooler and reinstall.
Why Step 1 Works
Here's the core of it: ERROR_REPARSE_OBJECT is Windows' way of saying "I found a symbolic link that points to nothing." When you earlier installed a printer driver, Windows created a reparse point — basically a shortcut in the registry that tells the system where the driver files live. If you then uninstalled the driver badly (like force-deleting files or using a third-party cleaner), that shortcut stays but the target disappears.
When you try to install a new printer using the same port name or driver name, Windows sees the old link, tries to follow it, gets a dead end, and throws 0X000002F3. Deleting that registry key or the ghost device removes the broken link. The new install then creates a fresh, valid one.
This error is specific to Windows 10 and 11 — older systems like Windows 7 rarely had it because they used a different driver model. But on modern Windows, leftover reparse points are a common pain.
Less Common Variations
Sometimes the error shows up with other hardware like scanners or USB devices, not just printers. If you see 0X000002F3 while installing a USB-to-serial adapter or a webcam, the same fix applies: the reparse point is in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{your device class GUID}. Find the GUID for your device type (printers are {4d36e979-e325-11ce-bfc1-08002be10318}). Delete the subkey with the stale reparse data.
Another variation: the error appears when you try to use the Windows Print Migration tool to move printers between PCs. Same cause — broken reparse points in the exported registry file. Fix: open the .reg file in Notepad, search for ReparseTag, remove that entire section, then import the cleaned file.
Prevention
Don't force-delete printer drivers. Always use the official uninstaller or go through Settings > Bluetooth & devices > Printers & scanners, select the printer, and click Remove device. Then open Device Manager, show hidden devices, and uninstall any leftover entries as shown above.
Also, never run a registry cleaner that claims to remove "orphaned printer entries." Those tools often delete only part of the data, leaving the reparse point intact and broken. Windows handles its own housekeeping — let it.
If you install printers often (like an IT guy), keep a restore point before each install. Legit takes 30 seconds and saves you from this exact headache.
Was this solution helpful?