STATUS_RESOURCE_DATA_NOT_FOUND (0XC0000089) Fix Guide

Cause 1: Corrupted System Files (most common)

I've seen this error more times than I care to count. It usually pops up when Windows tries to load a DLL or EXE file, and the resource section (where icons, strings, and other embedded data live) is missing or damaged. This happens after a botched update, a sudden crash during a file write, or a third-party cleaner that got a little too aggressive.

You'll see the error in Event Viewer under System logs, often paired with the source application name. The real fix here is to repair your system files using the built-in tools.

Run SFC Scan

1. Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin) or Terminal (Admin)).
2. Type: sfc /scannow and hit Enter. This checks all protected system files for integrity violations and replaces corrupted ones from a cached copy.
3. Wait for the scan to complete. It can take 5–15 minutes. If it finds corrupt files but can't fix some, that's normal—DISM will handle that.

Run DISM Next

1. Still in Administrator Command Prompt, type: DISM /Online /Cleanup-Image /RestoreHealth
2. This checks the Windows image itself, not just files. It downloads healthy versions from Windows Update if needed. Make sure you're connected to the internet.
3. After DISM finishes (takes 10–20 minutes), run sfc /scannow one more time to double-check everything.

I've fixed this error on Windows 10 22H2 and Windows 11 23H2 with just these two steps. If the error still shows up, move to Cause 2.

Cause 2: Outdated or Corrupted Graphics Drivers

This error also crops up when a driver's resource section gets corrupted, especially with GPU drivers. I've seen it happen after a driver update got interrupted—say, your laptop died mid-install, or you force-closed the installer because it took too long. The driver DLL ends up without its resource table, and Windows throws the 0XC0000089 error when the app tries to load it.

Skip the generic driver updater tools; they often download beta versions or wrong ones. Go straight to the source.

Steps to fix driver issues

1. Identify the problematic driver: Check Event Viewer (Event ID 1000 or 1001 under Windows Logs > Application). The faulting module path often points to a driver file like nvlddmkm.sys (NVIDIA) or igfx.dll (Intel).
2. Open Device Manager (right-click Start > Device Manager).
3. Right-click the device in question (usually Display Adapters) and choose Uninstall device. Check the box for Delete the driver software for this device.
4. Reboot. Windows will reinstall a basic driver, which is fine for now.
5. Go to the manufacturer's website (NVIDIA, AMD, Intel) and download the latest driver for your exact GPU model and OS version. Install it clean—choose the "Custom" or "Clean Install" option if available.

I've had this happen twice with NVIDIA drivers on Windows 11. Uninstalling completely and reinstalling fresh fixed it both times. If you're still hitting the wall, Cause 3 is your next stop.

Cause 3: The Application or Game Itself Is Corrupt

Less common, but I've seen it with games on Steam, Adobe Creative Cloud apps, and even antivirus software. The app's EXE or its dependency DLL is missing the resource section due to a bad update or a partial download. If you got the error after a specific program update, this is likely the culprit.

Fix for Steam/Epic/UWP apps

• Steam: Right-click the game in Library > Properties > Local Files > Verify integrity of game files. Stream will re-download any corrupted parts.
• Epic Games Store: Open library, click the three dots on the game > Verify.
• Windows Store (UWP) apps: Go to Settings > Apps > Installed apps, find the app, click the three dots > Advanced options > Reset. Or use PowerShell: Get-AppxPackage *appname* | Reset-AppxPackage

Fix for traditional desktop apps

1. Uninstall the app from Settings > Apps > Installed apps.
2. Reboot (yes, really—I know it's annoying, but orphaned registry entries can cause reinstall issues).
3. Download a fresh installer from the official site. Never use a cached installer—rename it something unique (e.g., setup_v3.2_clean.exe) to avoid Windows reusing a corrupted version from its installer cache.
4. Reinstall and test.

One time, an Adobe update corrupted the AdobeIPCBroker.exe file. Reinstalling Creative Cloud entirely solved it. Don't skip the reboot—it clears any lingering file locks.

Quick-Reference Summary Table

Start with SFC and DISM—that resolves 80% of cases. If not, move to drivers, then the app itself. I've never needed a full Windows reinstall for this error, so don't let anyone scare you into that.