Every terminal is crashing in Windows 10

Frequent crashes of the command prompt or Windows Terminal in Windows 10 usually stem from corrupted system files, conflicting third-party shell extensions, or misconfigured environment variables. By running system integrity checks and isolating the terminal application from external interference, you can restore stability to your command-line interface without needing to reinstall the operating system.

Identifying the Scope of the Crash

Before applying fixes, it is crucial to determine which terminal application is failing. Windows 10 includes two primary command-line interfaces: the legacy cmd.exe (Command Prompt) and the modern Windows Terminal. If only one of these crashes while the other functions correctly, the issue is likely isolated to that specific application's configuration or dependencies. If both fail simultaneously, the problem is more systemic, potentially involving core Windows components or user profile corruption. Start by opening the Start menu and searching for "Command Prompt." Right-click the result and select "Run as administrator." If this instance opens successfully, the issue may be related to permissions or specific user-level settings rather than a global system failure. Next, try launching Windows Terminal via the same method. Comparing the behavior between these two tools helps narrow down whether the fault lies with the legacy console host or the newer, cross-platform terminal emulator.

Repairing Corrupted System Files

One of the most common causes for terminal instability is corruption within the Windows System File Checker database. When essential DLLs or executable files are damaged, the operating system cannot load the terminal properly, resulting in immediate closures or error dialogs. To address this, you must run the System File Checker tool with elevated privileges. Open an administrative Command Prompt by right-clicking the Start button and selecting "Windows PowerShell (Admin)" or "Command Prompt (Admin)." Type the following command and press Enter:

sfc /scannow

This process scans all protected system files and replaces corrupted versions with correct Microsoft versions. The scan may take several minutes to complete. If the tool reports that it found corrupt files and successfully repaired them, restart your computer and test the terminal again. If SFC fails to fix the issue, proceed to the Deployment Image Servicing and Management tool, which repairs the underlying Windows image. Run this command in the same administrative window:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run sfc /scannow once more to ensure any remaining file issues are resolved. This two-step repair process addresses deep-seated system corruption that often manifests as application crashes. For users experiencing broader system instability, ensuring your OS is fully patched is also recommended; see our guide on updating Windows to resolve compatibility issues.

Disabling Third-Party Shell Extensions

If system files are intact, the culprit is often a third-party application injecting shell extensions into the explorer context. Tools like cloud storage syncers, antivirus programs, or file compression utilities can add right-click menu items or hooks that interfere with how the terminal initializes. These extensions may crash during the loading phase, causing the entire terminal session to terminate unexpectedly. To diagnose this, perform a clean boot to disable non-essential services and startup applications. Press Win + R, type msconfig, and press Enter. In the System Configuration window, go to the "Services" tab, check "Hide Microsoft services," and then click "Disable all." Next, navigate to the "Startup" tab and open Task Manager to disable all startup items. Restart your computer and attempt to launch the terminal. If the terminal works correctly after a clean boot, re-enable services and startups in small batches to identify the offending software. Pay special attention to applications that modify the file system or interact with command-line interfaces. Removing or updating the problematic application should resolve the crashing issue permanently.

Resetting Environment Variables and Profiles

Misconfigured environment variables can also cause terminals to crash upon startup. If a variable points to a non-existent path or contains invalid characters, the shell may fail to initialize. Additionally, user profile corruption can lead to similar symptoms. You can reset environment variables by accessing Advanced System Settings through the Control Panel. Navigate to Environment Variables and review the PATH variable. Ensure there are no trailing semicolons or references to deleted directories. If you suspect profile corruption, creating a new local user account can help isolate the issue. Create a new standard user account, log in, and test the terminal. If it works, the original user profile is likely damaged, and migrating data to the new account may be necessary. For advanced users who need to modify system settings directly, understanding how to edit the registry safely can prevent accidental damage during troubleshooting.

Reinstalling Windows Terminal

For users specifically encountering issues with Windows Terminal rather than the legacy CMD, resetting the app via PowerShell is an effective solution. Open PowerShell as an administrator and run the following command to remove the current installation:

Get-AppxPackage *Microsoft.WindowsTerminal* | Remove-AppxPackage

After removal, restart the Microsoft Store and search for "Windows Terminal" to reinstall the latest version. This ensures you have a clean configuration file and the most recent bug fixes. Note that this action does not delete your custom profiles or settings if they were stored in the default location, but it resets the app state.

Frequently Asked Questions

Why does my terminal crash only when I run specific commands?

This usually indicates a conflict with a specific executable or a missing dependency required by that command. Check if the command relies on external tools that might be uninstalled or moved. Running the command in a different user profile can help confirm if the issue is environment-specific.

Can antivirus software cause terminal crashes?

Yes, real-time scanning can sometimes interfere with the execution of scripts or binaries launched from the terminal. Temporarily disabling your antivirus or adding the terminal executable to its exclusion list can verify if this is the cause. Ensure you re-enable protection immediately after testing.

What should I do if sfc /scannow finds nothing to fix?

If SFC reports no integrity violations, the issue likely lies outside of core system files. Focus on third-party software conflicts, driver issues, or user profile corruption. Proceed with the clean boot diagnostic steps to isolate external interference.

Is it safe to delete the AppData folder for Windows Terminal?

Deleting the local AppData folder for Windows Terminal will reset the application to its default state, removing custom themes and configurations. This is a safe troubleshooting step if the app is corrupted, but you will need to reconfigure your preferences afterward.

How do I check if my graphics drivers are causing terminal issues?

While rare, outdated GPU drivers can cause rendering failures in Windows Terminal due to its use of DirectComposition. Update your graphics drivers through Device Manager or the manufacturer's utility. If the issue persists, try switching the rendering backend in Windows Terminal settings from DirectComposition to GDI.