sodcalculator

10 Tech How-To

Fix Runtime Error 429 on Windows 10 and Earlier

Guide 10-51491 · Updated · Step by step

Runtime error 429 is a Windows error that typically appears when a program tries to use an ActiveX component or a COM object that is not properly registered or available. This guide walks you through the most effective fixes, from re-registering the component to repairing the underlying system files, and works on Windows 10, 8, 7, and Vista.

What You’ll Need

  • Administrator access to the computer (you’ll need to run some commands as admin).
  • The name of the program that triggers the error (if you know it, it helps narrow down the fix).
  • An internet connection (for downloading updates or tools if needed).

Step-by-Step

  1. Restart your computer. This clears temporary glitches that might cause the error. If the error persists, continue.
  2. Re-register the Windows Script Host components. The error often involves scripting files like .vbs or .dll. Open Command Prompt as administrator (press Windows key, type “cmd”, right-click “Command Prompt”, and select “Run as administrator”). Then type the following commands one by one, pressing Enter after each:
    regsvr32 vbscript.dll
    regsvr32 jscript.dll
    regsvr32 scrrun.dll
    You should see a success message for each. Restart your computer and test.
  3. Re-register the component that the program uses. If you know which ActiveX or COM component is failing (the error message might mention a .dll or .ocx file), locate it in the System32 or SysWOW64 folder (usually C:\Windows\System32 or C:\Windows\SysWOW64). Then run:
    regsvr32 "C:\Windows\System32\filename.dll"
    Replace the path and filename with the actual file. If the file is 32-bit on a 64-bit system, use the SysWOW64 folder.
  4. Run System File Checker (SFC). Corrupted system files can cause this error. Open Command Prompt as administrator and type:
    sfc /scannow
    Wait for the scan to complete (it may take 15-30 minutes). If it finds and fixes issues, restart and test.
  5. Run DISM (Deployment Imaging Service and Management Tool). If SFC doesn’t fix it, run DISM to repair the Windows image. In the same admin Command Prompt, type:
    DISM /Online /Cleanup-Image /RestoreHealth
    This may take longer. After it finishes, restart and test.
  6. Update the problematic program. If the error occurs in a specific application, check the developer’s website for updates or patches. Older programs often have compatibility issues with newer Windows versions.
  7. Run the program in compatibility mode. Right-click the program’s .exe file, select “Properties”, go to the “Compatibility” tab, check “Run this program in compatibility mode for:”, and select an older Windows version (e.g., Windows 7). Apply and test.
  8. Check for malware. Malware can corrupt registry entries that cause runtime errors. Run a full system scan with Windows Defender or a reputable antivirus program.
  9. Perform a clean boot. This starts Windows with a minimal set of drivers and startup programs. Type “msconfig” in the Start menu, go to the “Services” tab, check “Hide all Microsoft services”, then click “Disable all”. Go to the “Startup” tab and click “Open Task Manager”, disable all startup items. Restart. If the error is gone, re-enable services/startup items one by one to find the culprit.
  10. Reinstall the program. If none of the above works, uninstall the program that causes the error, restart, and reinstall it. This ensures all its components are correctly registered.

Common Mistakes

  • Not running commands as administrator. regsvr32 and sfc require admin rights. If you don’t run them as admin, you’ll get “Access denied” or “You must be an administrator” errors.
  • Using the wrong file path. On 64-bit Windows, 32-bit components are in SysWOW64, not System32. Registering the wrong version can cause more issues.
  • Skipping the restart. Many fixes require a restart to take effect. Don’t skip it, or the error may persist.
  • Ignoring the specific component. Re-registering all DLLs blindly is not recommended. Focus on the ones mentioned in the error message.

Tips

  • Create a system restore point before making changes. This lets you revert if something goes wrong.
  • Write down the exact error message. The full text often includes the component name, which is key to fixing it.
  • If you’re using a 64-bit system, try both the 32-bit and 64-bit versions of the component. Sometimes a program needs the 32-bit version even if Windows is 64-bit.
  • Keep Windows updated. Many runtime errors are fixed by Windows updates.

Troubleshooting

If you’ve followed the steps and the error persists, try these additional checks:

  • Check the Event Viewer. Press Windows key + R, type “eventvwr”, and look under Windows Logs > Application for errors around the time the error occurs. The details may point to the specific module.
  • Try a different user account. Create a new admin account and run the program there. If it works, the issue is with your user profile.
  • Use Process Monitor. Microsoft’s Process Monitor can show which registry keys or files the program is trying to access when the error occurs. This is advanced but can reveal the exact missing component.
  • Consider the program’s age. Very old programs (from Windows 95/98 era) may not work at all on modern Windows. In that case, consider using a virtual machine with an older Windows version.
  • Check for conflicting software. Antivirus or security software can sometimes block ActiveX components. Temporarily disable them (if safe) to test.

Frequently Asked Questions

What causes Runtime Error 429?

It’s usually caused by a missing or unregistered ActiveX component, a corrupted system file, or a program that expects an older version of a component.

Is Runtime Error 429 dangerous?

No, it’s not dangerous by itself. It just means a program can’t run properly. However, if it’s caused by malware, that could be a concern.

Will reinstalling Windows fix it?

Yes, a clean install of Windows will almost certainly fix the error, but it’s a last resort. Try the steps above first.

Can I fix this without admin rights?

No, most fixes require admin access. If you don’t have admin rights, contact your system administrator.

Does this error affect all programs?

No, it usually affects only the specific program that uses the unregistered component. Other programs should work fine.

How long does the SFC scan take?

It can take 15-30 minutes, depending on your system speed and hard drive. Don’t interrupt it.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →