How to Fix CLR Error 80004005: The Program Will Now Terminate

By ErrorFix · Updated October 14, 2026 · 8 min read

What error 0x80004005 means

CLR error 80004005 appears as a small popup that says the program "will now terminate." The CLR — Common Language Runtime — is the engine that .NET Framework programs run on, similar to how Java programs need the Java runtime. When you double-click a .NET app, the CLR loads first and boots the program inside it. If that startup sequence fails, the CLR gives up and kills the app before its window ever appears.

This is not one of Windows' generic failure codes — it specifically means the crash happened inside the .NET runtime, not in Windows itself. That narrows the fix list considerably: you are looking at the framework installation, the program's own files, a driver the framework talks to at launch (graphics drivers are the usual suspect), or a security setting that blocks the startup code. Work through the steps below in order; the majority of people fix it by step 3.

Common causes

• Corrupted .NET Framework installation: missing or damaged framework libraries crash the CLR before the program can load — the single most common cause.
• Broken program files: a bad install, an interrupted update, or a deleted DLL leaves the app unable to boot inside the runtime.
• Outdated or corrupt graphics driver: many .NET apps initialize graphics at startup, and a broken driver takes the whole process down with it.
• Missing permissions: the program needs access to registry keys or folders it cannot reach under a standard user token.
• Data Execution Prevention conflict: DEP can mistake some .NET startup code for malicious behavior and terminate the app.

How to fix CLR error 80004005 — step by step

Work through these fixes in order. Most people clear this error by step 3.

1. Run the program as administrator Right-click the program's shortcut or its .exe file and choose "Run as administrator," then click Yes on the prompt. If the app opens normally, the crash was a permissions problem — the program could not reach files or registry entries it needs. For a permanent fix, right-click the shortcut, choose Properties, go to the Compatibility tab, and check "Run this program as an administrator."
2. Reinstall or repair the Microsoft .NET Framework If the program uses a modern .NET Framework version, open Settings, go to Apps, then Installed apps, find the Microsoft .NET Framework entries, and uninstall them. Then download the latest .NET Framework installer from Microsoft's official website, run it, and restart your PC. If the version came with Windows (3.5 or 4.8), repair it instead: open the Control Panel, go to Programs, then "Turn Windows features on or off," uncheck the .NET entries, restart, then check them again to reinstall.
3. Reinstall the crashing program Open Settings, go to Apps, then Installed apps, and uninstall the program. If a folder for it remains under Program Files, delete it manually. Then download a fresh installer from the developer's official website and install it again. This replaces corrupted DLLs, broken config files, and incomplete updates — all common CLR crash triggers. Do not use an old installer you have saved locally, since it may be the corrupted source itself.
4. Update your graphics drivers Press the Windows key + X and open Device Manager. Expand "Display adapters," right-click your graphics card, and choose "Update driver," then "Search automatically for drivers." If Windows says the best driver is already installed, visit the GPU maker's site — NVIDIA, AMD, or Intel — download the newest driver for your card, install it, and restart. Because many .NET apps initialize graphics during startup, a broken driver crashes the CLR before the program window ever appears.
5. Repair Windows system files with SFC and DISM Right-click Start and choose Terminal (Admin). Run sfc /scannow and let it finish — it scans protected system files and replaces damaged ones. If it reports it could not fix everything, run DISM.exe /Online /Cleanup-image /Restorehealth to repair the underlying component store, then run sfc /scannow once more. Restart your PC afterward and try launching the program again.
6. Add the program as a Data Execution Prevention exception Search the Start menu for "advanced system settings" and open "View advanced system settings." Go to the Advanced tab and click "Settings" under Performance. Open the "Data Execution Prevention" tab, select "Turn on DEP for all programs and services except those I select," click "Add," browse to the program's .exe file, add it, and click OK. Restart the program. This fixes the cases where DEP blocks the .NET startup code and forces the "will now terminate" crash.

Did this fix it? Quick checklist

• The program launches without the "The program will now terminate" popup
• .NET Framework shows correctly installed under Windows Features
• The graphics driver in Device Manager is the newest version available
• The app also opens when launched as administrator

If the error persists after all six steps, check whether the program has a newer version that no longer targets the old .NET Framework — very old .NET apps can break on fully updated Windows 11 systems, and the developer may have released a fixed build. Also try launching the program from a different Windows user account: if it works there, your user profile's .NET configuration is damaged, and creating a fresh profile (or repairing your account) is faster than chasing the exact corrupted file.