ERROR_CONTROL_ID_NOT_FOUND Fix: 0X0000058D

Quick Answer

Restart the app. If that fails, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an admin Command Prompt, then update the problematic program or reinstall it.

What This Error Actually Means

I know seeing 0X0000058D pop up feels like a punch to the gut — especially when you're in the middle of something important. This error code, ERROR_CONTROL_ID_NOT_FOUND, is Windows's way of saying it tried to reference a control (like a button, text box, or dropdown) inside a dialog box or resource file, but that ID doesn't exist. It's not a hardware failure or a virus — it's a resource mismatch.

Typically, this happens when an app expects a specific version of a DLL or resource file, but the file is outdated, corrupted, or from another program. I've seen it most often with older Windows applications (think Office 2010, Visual Studio 2015, or custom line-of-business software) after an OS update or a third-party tool replaced a system file. It's also common with game launchers like Steam or Origin when their UI resources get borked by a partial update.

Let's fix it. Start with the quickest checks, then work down to the heavier stuff.

Fix Steps

1. Restart the application — sounds basic, but I've seen this error vanish after a simple reboot of the program. Close it fully (check Task Manager for background processes), then relaunch. If it works, you're done. If not, move on.
2. Run System File Checker — open Command Prompt as Administrator (type cmd in Start, right-click, choose Run as administrator). Then type sfc /scannow and let it run. It'll check for corrupted system files and replace them. Takes 10-15 minutes. If it finds issues, it fixes them automatically.
3. Run DISM to repair the system image — if SFC doesn't help, the underlying image might be damaged. In the same admin Command Prompt, run DISM /Online /Cleanup-Image /RestoreHealth. This downloads clean files from Windows Update. It can take 20 minutes. Don't close the window.
4. Update the problematic program — go to the app's update checker or download the latest version from the official site. Old versions of software often reference resource IDs that don't exist in newer Windows releases. I've seen this with Adobe Creative Suite 5 and older AutoCAD versions.
5. Reinstall the application — uninstall it via Settings > Apps > Apps & Features. Reboot, then install the latest version from scratch. Make sure you grab the correct architecture (32-bit vs 64-bit). If it's a business app, contact your IT team for the exact version.
6. Check for conflicting third-party software — if the error appears in a dialog box, note which program triggered it. I've seen antivirus tools (especially McAfee and Avast) inject their own UI elements and mess up resource IDs. Temporarily disable the antivirus, test the app, then re-enable it. If that fixes it, add the app to the antivirus's exclusions.

Alternative Fixes If the Main Steps Fail

If none of the above worked, try these:

• Run the app in compatibility mode — right-click its executable, go to Properties > Compatibility tab, and run the troubleshooter. Or manually set it to an older Windows version that you know worked (e.g., Windows 7 or 8).
• Use Process Monitor to trace the missing resource — download Process Monitor from Microsoft Sysinternals. Filter by the app name. Look for NAME NOT FOUND entries with paths that include .rc or .res files. That'll tell you exactly which file is missing or wrong. Replace that file from a known-good source or reinstall the app.
• Check Event Viewer — open Event Viewer, go to Windows Logs > Application, and look for Error events with ID 0x58D. The details there often include the app's binary path and the control ID. Google that control ID with the app name — someone else has likely solved it.
• Perform a clean boot — type msconfig into Start, go to Services tab, check "Hide all Microsoft services", then click "Disable all". Reboot. If the error disappears, re-enable services one by one until you find the culprit.

Prevention Tip

The best way to avoid ERROR_CONTROL_ID_NOT_FOUND is to keep Windows and all your software updated. Third-party resource editors (like Resource Hacker) can corrupt files if used incorrectly — don't manually edit .exe or .dll resources unless you're absolutely certain of what you're doing. Also, always download apps from official sources to avoid mismatched resource files from repack or cracked versions.

One more thing: If you're using custom visual themes or shell replacements (like WindowBlinds), disable them temporarily. They can replace system resources and cause control IDs to vanish. This tripped me up the first time I saw it on a Windows 10 machine with a custom theme.