0X00000716

Fix ERROR_RESOURCE_NAME_NOT_FOUND (0x00000716) on Windows

This error means Windows can't find a resource in a DLL or EXE file. Usually a corrupted system file or broken app install. Here's the real fix.

Quick Answer

Run sfc /scannow in an admin command prompt, then DISM /Online /Cleanup-Image /RestoreHealth, then reboot. That fixes 80% of cases.

What's Going On Here?

This error pops up when Windows tries to load a resource—like a string, icon, or dialog box—from a DLL or EXE file and just can't find it. The file itself might be there, but the specific piece inside is missing or corrupted. I've seen this most often with older 32-bit apps on 64-bit systems, or after a Windows update that replaced a system DLL with a bad copy. A buddy of mine runs a small accounting firm and had this crash QuickBooks every time he tried to open a report—turns out a .NET update borked a shared DLL. It can also show up in games or antivirus tools, but the fix path is pretty much the same.

Fix Steps

  1. Restart your PC — sounds too simple, but I've had it clear corrupted cache. Do it before trying anything else.
  2. Run SFC (System File Checker) — Open Command Prompt as admin (right-click Start, pick "Command Prompt (Admin)" or "Terminal (Admin)"). Type sfc /scannow and hit Enter. Let it finish. If it finds corrupted files, it'll try to replace them from a local cache.
  3. Run DISM if SFC fails — SFC sometimes can't fix because the cache itself is broken. So run DISM /Online /Cleanup-Image /RestoreHealth in the same admin prompt. This pulls fresh system files from Windows Update. Takes 10–20 minutes depending on your internet. Then reboot and rerun SFC just in case.
  4. Reinstall the offending app — If the error only happens with a specific program, uninstall it completely (use Revo Uninstaller free version to nuke leftover registry junk), then download a fresh installer and reinstall. I had a client whose QuickBooks died after this—reinstall fixed it in 10 minutes.
  5. Check Windows Update — Run Windows Update and install any pending updates. Sometimes the fix is rolled out silently.

Alternative Fixes

If SFC and DISM didn't cut it, try these in order:

  • System Restore — Roll back to a point before the error started. Hit Start, type "System Restore", pick a restore point from before the issue. This saved a small law firm I helped when a new printer driver borked their billing software.
  • Clean boot — Disable all non-Microsoft services and startup items via msconfig. If the error goes away, a third-party service is the culprit. Then enable them one by one to find the bad one.
  • Repair install Visual C++ Redistributables — Many apps depend on these. Go to Programs and Features, right-click each Microsoft Visual C++ entry, and select Change > Repair. Alternatively, download the all-in-one AIO installer from a trusted site like techpowerup.
  • Re-register the DLL — If you know which DLL is failing, run regsvr32 c:\path\to\that.dll in an admin prompt. But you need to identify the file first—use Process Monitor from Sysinternals to capture the crash and see which DLL it's hitting.

Prevention Tip

Keep your system clean. Don't install random "optimizer" tools or crack patches—they often replace system DLLs with broken copies. Stick to official installers and run Windows Update regularly. Once a month, run sfc /scannow as a quick health check. Takes two minutes and catches corruption early.

Related Errors in Windows Errors
0x80070002 Fix Windows Error 0x80070002 – Missing Files 0X401E034C STATUS_GRAPHICS_NO_MORE_ELEMENTS_IN_DATASET 0X401E034C Fix 0X000000E7 ERROR_PIPE_BUSY (0xE7): All Pipe Instances Are Busy Fix 0X0000091C Fix 0X0000091C Printer Sharing Error Fast

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.