Fix ERROR_OBJECT_NOT_FOUND 0x000010D8 on Windows 10/11

What triggers 0x000010D8

This error shows up when Windows asks for a specific object ID and the system can't match it to anything real. I've seen it most often after a failed software install or a registry cleaner that got too aggressive. You'll get a popup saying "The object identifier does not represent a valid object" — usually paired with error code 0x000010D8 (decimal 4312).

It can also hit during driver updates, especially for graphics or network adapters. One real-world case: a user installed a printer driver from a sketchy website, and this error appeared every time they opened Device Manager. The fix was simpler than they thought.

Here's the flow. Start at step 1. If it's fixed, stop. If not, move to step 2.

Step 1: Simple fix — reboot and check for leftover processes (30 seconds)

Before you dig into anything complicated, do a full restart. Not a shutdown. A restart. Windows 10 and 11 use Fast Startup by default, which means a shutdown doesn't clear the kernel session. A restart does.

1. Click Start, then the Power icon.
2. Hold Shift on your keyboard and click "Restart." Keep holding Shift until you see the blue screen with options.
3. Let it reboot normally after that.

After the restart, open Task Manager (Ctrl+Shift+Esc). Look under the Processes tab for anything that's "Suspended" or "Not responding." If you see something related to the program that threw the error, right-click it and choose "End task." That's often enough to clear a hung object reference.

If the error is gone, you're done. If it comes back, move to step 2.

Step 2: Moderate fix — clean the registry reference (5 minutes)

This error often lives in the registry. A broken key or orphaned entry points to an object that no longer exists. You'll need to find and remove it.

Backup first. I can't stress this enough. A wrong registry edit can brick your install.

1. Press Win+R, type regedit, and hit Enter.
2. In Registry Editor, go to File > Export. Save a full backup to your Desktop as "backup.reg."
3. Now press Ctrl+F to open Find. Type the error code as 0x000010D8 and click Find Next.
4. Registry Editor will search every key, value, and data. Wait — it might take a minute on a large registry.
5. If it finds a key or value containing that string, right-click the entry and choose Delete. Be absolutely sure it's the right one. The full path will show in the status bar at the bottom.
6. Press F3 to find the next one. Delete all matches.
7. Close Registry Editor and restart your PC.

After the restart, check if the error is gone. If it still shows up, the problem isn't registry-based — it's probably disk corruption. Move to step 3.

Step 3: Advanced fix — check disk and system files (15+ minutes)

When the object ID lives in a corrupted file or on a disk with bad sectors, neither reboot nor registry editing will fix it. You need to repair the file system and check for corruption.

Run CHKDSK first

CHKDSK finds physical disk errors that can cause object identifiers to go missing. Run it on your system drive (usually C:).

1. Open Command Prompt as Administrator. Press Win+X, then choose "Windows Terminal (Admin)" or "Command Prompt (Admin)."
2. Type this command and press Enter:

   chkdsk C: /f /r

3. It'll say the drive is in use and ask if you want to schedule it for the next restart. Type Y and press Enter.
4. Restart your PC. CHKDSK will run before Windows loads — it'll take 30 minutes to a few hours depending on drive size and damage. Let it finish. Don't interrupt it.

After CHKDSK finishes and you're back in Windows, see if the error is gone. If not, move to SFC.

Then run SFC and DISM

System File Checker (SFC) replaces corrupted Windows files. DISM fixes the system image that SFC relies on. Run them in this order.

1. Open Command Prompt as Administrator again.
2. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This checks the Windows component store and fixes what it can. It'll show a progress bar — expect 10-20 minutes. It might look stuck at 20% for a while. That's normal.
3. Once DISM finishes, type sfc /scannow and press Enter. SFC will scan all protected system files and replace any corrupted ones from the local cache. This takes 15-30 minutes.
4. After SFC finishes, restart your PC.

That sequence (CHKDSK → DISM → SFC) covers every base. I've seen it fix this error on half a dozen machines. If it still doesn't work, you might be dealing with a failing hard drive — run a SMART test using CrystalDiskInfo or the manufacturer's diagnostic tool.

Final note

If none of these steps work, the error could come from a specific application that's looking for a custom object. Check the Event Viewer (Event ID 10 under Windows Logs > System often tags the source). Uninstall the app that appears in the log entry, then reinstall it. That's rarely needed, but I've seen it with old Visual C++ redistributables and certain VPN clients.