How to fix error code 0xe06d7363 on Windows?

0xe06d7363 is the code Windows reports when a program written in C++ throws an error that its own code never catches. It is a crash of that program, not a Windows fault, and the code alone names no cause. Find out which program crashed first, then update, repair or reinstall it.

Facts checked on 16 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What error code 0xe06d7363 means

Microsoft's debugger documentation lists 0xE06D7363 under the name STATUS_CPP_EH_EXCEPTION: a C++ exception handling exception. When a program built with Visual C++ hits a problem, its code "throws" an exception and expects another part of the same program to catch it. If nothing catches it, Windows ends the program and shows this code. Windows cannot see what the C++ error was, so the window calls it an unknown software exception.

The message as the reader above saw it (the program name sits in the title bar)

Application Error
The exception unknown software exception (0xe06d7363) occurred in the application.

• E0 at the start marks a code made by a program, not one of Windows' own status codes.
• 6D 73 63 are the ASCII letters msc. Every C++ exception from a Visual C++ program carries the same code, whatever went wrong.
• The title bar of the window names the program file that crashed. That name is what you work with.
• The address after "at location" points into Windows' own code, where the exception was raised. It changes between runs and does not help you.

Why the 0xe06d7363 error happens: causes ranked

We have no counts of how often each cause occurs. The order below follows what the code means: an error inside one program is the normal case, damaged parts shared by many programs are less common, and damaged Windows files are rare.

The reader's case above, several apps crashing on a black loading screen, fits the third and fourth rows: something the apps share is broken or gets in the way. Still find the program names first, because two different apps can also crash for two different reasons.

How to fix error code 0xe06d7363

Fix 1 tells you which program crashed. Fixes 2 and 3 repair that program and the Visual C++ files it needs, and solve most cases. Fixes 4 and 5 find a program that interferes. Fixes 6 to 9 are for crashes in many programs. You do not need to do all of them.

Fix 1. Find which program crashed with 0xe06d7363

5 minutesNo riskEveryone, unless the title bar of the error window already named a program you know.

0xe06d7363 is the same for every C++ crash, so the code cannot point to a fix. The faulting application named in the crash record can.

1. If the error window is still open, note the file name in its title bar before you select OK.
2. Press Win + R, type eventvwr and select OK.
3. Expand Windows Logs and select Application.
4. Find an Error from the source Application Error with event ID 1000 at the time of the crash.
5. On the General tab, check that it shows Exception code: 0xe06d7363, then note Faulting application name and Faulting module name.
6. Select Copy in the event window and paste the text into Notepad. You may need it for Fix 2 or for the program's support.

A faster view is Reliability Monitor: press Win + R, type perfmon /rel and select OK. Red crosses mark crashes by day. Select one and choose View technical details to see the same program name and exception code.

PowerShell: the last five crashes with code 0xe06d7363 (no administrator rights needed)

Get-WinEvent -FilterHashtable @{ LogName='Application'; ProviderName='Application Error'; Id=1000 } -MaxEvents 100 |
  Where-Object Message -match 'e06d7363' | Select-Object -First 5 | Format-List TimeCreated, Message

Fix 2. Update, repair or reinstall the program that crashed

15 to 30 minutesLow riskThe title bar or event 1000 names one program, and other programs work.

The exception was thrown inside that program's own code. A newer version may fix the bug, and a repair or clean install brings back a missing or mismatched file that made its code fail.

1. Look for an update in the program's Help or About menu, its launcher, or on its maker's website.
2. If there is no update, press Win + I and open Apps > Installed apps (Windows 10: Apps > Apps & features).
3. Select the three dots next to the program (Windows 10: select the program). If Modify or Advanced options with Repair is offered, use it first.
4. If the crash stays, select Uninstall and restart the PC.
5. Install the newest version from the maker's own website or store and start it again.

Other ways to remove a program, such as Control Panel: Uninstall a program or app in Windows A Microsoft Store app has Repair and Reset instead: How to repair or reset an app in Windows A game from Steam, Epic or another launcher can check its own files without a reinstall: How to verify game files in Steam, Epic Games, Xbox app, EA app, Battle.net and GOG Galaxy

Fix 3. Repair the Microsoft Visual C++ Redistributable packages

15 minutesLow riskSeveral C++ programs or games crash with 0xe06d7363, as in the reader's question, or event 1000 names a Visual C++ file such as VCRUNTIME140.dll.

Programs built with Visual C++ throw and catch their exceptions through the Visual C++ runtime files that many programs share. A damaged or outdated runtime can break that for all of them at once.

1. Open Programs and Features. Type control panel in the search box on the taskbar and select Control Panel. Select Programs > Programs and Features.
2. Find the installed versions. Look for the entries that start with Microsoft Visual C++. Each one shows a year and an architecture, x64 or x86. Several entries side by side are normal: older versions stay installed next to newer ones.

   

3. Repair each Visual C++ entry. Right-click an entry and select Change, then select Repair in the window that opens. Do the same for every Microsoft Visual C++ entry.

   

4. Install the latest supported version. Download the latest Visual C++ v14 Redistributable from Microsoft: Visual C++ Redistributable latest supported downloads and run it. On a 64-bit PC install both X64 and X86, because 32-bit programs need the x86 package. On an ARM64 PC install ARM64. This one version serves programs built with Visual Studio 2017 to 2026.

These steps were written for Windows 11 25H2 and 26H2, Windows 10 22H2. The full page with the other versions and what each result means: How to repair Microsoft Visual C++ Redistributable and .NET Framework

• Repair every Microsoft Visual C++ entry, x64 and x86. A 64-bit PC often runs 32-bit programs that need the x86 package.
• Do not uninstall the older years. Programs built for 2010 or 2013 need those exact packages, and the newer one does not replace them.
• Restart the PC after the repair, then start the program that crashed.

Fix 4. Test the program in Safe Mode

10 minutesNo riskThe crash comes at sign-in, names a program you never open, or Fixes 2 and 3 did not help.

Safe Mode starts Windows with basic drivers and no third-party startup programs. If the program runs there without 0xe06d7363, something that loads in a normal start is the cause, not the program's own files.

1. Restart from Settings…. Open Settings > System > Recovery. Next to Advanced startup, select Restart now and confirm. On Windows 10 the path is Settings > Update & Security > Recovery.
2. …or hold Shift and select Restart. Instead of Settings you can select Start > Power, hold Shift and select Restart. This also works from the power button on the sign-in screen.
3. Select Troubleshoot. On the blue Choose an option screen, select Troubleshoot.
4. Open Startup Settings. Select Advanced options > Startup Settings.
5. Restart. On the Startup Settings page, select Restart. The PC restarts and shows a numbered list.
6. Choose Safe Mode. Press 4 or F4 for Enable Safe Mode. Press 5 or F5 for Enable Safe Mode with Networking if you need the internet, for example to download a scanner or a driver.
7. Leave Safe Mode. When you are done, restart the PC normally. Windows starts in normal mode again.
8. If it keeps starting in Safe Mode. Press Windows key + R, type msconfig and press Enter. On the Boot tab, clear Safe boot, select OK and restart.

These steps were written for Windows 11 24H2 and later; Windows 10 22H2. The full page with the other versions and what each result means: Start Windows or a Mac in Safe Mode

• Start the program that crashed while you are in Safe Mode. Some programs, many games among them, need full graphics drivers and do not run there at all. That result tells you nothing.
• It works in Safe Mode: a driver or startup program is involved. Go to Fix 5 to find which one.
• It crashes in Safe Mode too: the cause is in the program or Windows files. Go back to Fix 2 or on to Fix 8.

Fix 5. Find an interfering program with a clean boot

20 to 40 minutesLow riskThe program works in Safe Mode, or crashes keep coming with no clear pattern.

Overlays, screen recorders, monitoring tools and some security programs load into other programs and can make their code fail. A clean boot turns them off while Windows keeps its normal drivers, so you can find the one behind 0xe06d7363.

1. Do a clean boot as described in How to perform a clean boot in Windows: tick Hide all Microsoft services, turn off the rest, and turn off the startup apps.
2. Restart and open the program that crashed. If 0xe06d7363 no longer appears, one of the turned-off items is the cause.
3. Turn half of the services back on, restart and test again.
4. Keep halving the group that brings the crash back until one service or startup app is left.
5. Update or remove that program, then return System Configuration to Normal startup.

Fix 6. Undo a recent change with System Restore

20 to 30 minutesRead the warningThe crashes began on a known day, after a driver, Windows update or program install, and a restore point from before that day exists.

If a recent change replaced a shared file or driver that the crashing programs use, returning Windows to a restore point from before the change puts the old files back.

1. Open System Restore. Press Windows+R, type the command below and press Enter. You can also open Control Panel > Recovery > Open System Restore. If a first page opens, select Next.

   rstrui.exe

2. Choose a restore point. Select a restore point from a time before the problem started. The Description often names the event, such as a driver or app install. If the one you need is missing, select Show more restore points (shown only when there are more).
3. See what will change. Select Scan for affected programs. The upper list shows programs and drivers that will be removed; the lower list shows those that might come back and may need to be reinstalled. Select Close.
4. Start the restore. Select Next, check the summary and select Finish. Windows restarts and applies the restore point. Do not turn the PC off.
5. Check the result. After sign-in Windows reports whether the restore succeeded. Check whether the problem is gone.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Undo recent changes with System Restore

Fix 7. Scan for malware with Microsoft Defender

15 minutes to 2 hoursNo riskThe title bar or event 1000 names a program file you do not know, or the PC shows other odd behaviour.

0xe06d7363 is a crash code, not a sign of malware. Malware can still damage program files or settings so that a program crashes, and an unknown file name is worth one check.

1. Look at where the file from the title bar lives: in Task Manager, right-click it on the Details tab and select Open file location, if it is running.
2. If you cannot place the file, run a full scan or a Microsoft Defender Offline scan with the steps in How to scan for malware with Microsoft Defender
3. Let Defender remove or quarantine what it finds and restart the PC.
4. Reinstall the program that crashed (Fix 2), because removed malware does not bring back the files it damaged.

Fix 8. Repair Windows system files with DISM and SFC

20 to 40 minutesNo riskSeveral programs crash and Fixes 3 to 5 did not help, or Windows' own tools fail too.

C++ programs raise their exceptions through Windows' own system files. If those files are damaged, many programs can fail at once. DISM repairs the Windows image and SFC then replaces bad system files from it.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

Fix 9. Check the drive for errors with chkdsk

10 minutes to several hoursLow riskSFC could not repair some files, or programs on one drive crash with damaged files again after a reinstall.

Errors in the file system can damage program and runtime files again after you repair them. chkdsk finds and fixes those errors, so the repaired files stay whole.

1. Open Command Prompt as administrator. Type cmd in the search box on the taskbar, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
2. Scan the drive without changing anything. Type the command below and press Enter. Replace C: with another drive letter to check that drive. This scan only reports; it does not fix anything.

   chkdsk C:

3. If errors were found, run the repair. Run chkdsk with /f to fix file system errors. On the Windows drive (C:) chkdsk cannot lock the drive while Windows is running, so it offers to check it at the next restart.

   chkdsk C: /f

4. Schedule the check and restart. Type Y and press Enter, then restart the PC. chkdsk runs before Windows starts. Do not turn the PC off while it runs.
5. Read the result after the restart. The report of a check made at startup is not shown on the desktop. Open PowerShell and run the command below to see it, or open Event Viewer (eventvwr.msc) > Windows Logs > Application and filter by the sources Chkdsk and Wininit.

   Get-WinEvent -FilterHashtable @{LogName='Application'} | Where-Object { $_.ProviderName -match 'wininit' } | Select-Object -First 1 | Format-List TimeCreated, Message

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Check a disk for errors (chkdsk)

If 0xe06d7363 keeps coming back: what to send and to whom

When the same program crashes with 0xe06d7363 after a clean install and a Visual C++ repair, the bug is in that program, and only its maker can fix it. The code itself helps them little, because all C++ crashes share it. They need the crash records.

• The full text of event 1000, copied in Fix 1: program version, faulting module, exception code and fault offset.
• The Windows Error Reporting files for the crash, found in C:\ProgramData\Microsoft\Windows\WER\ReportArchive in a folder that starts with the program's name.
• What you did when it crashed: starting the program, a loading screen, a menu, closing it.
• Your Windows version: press Win + R and type winver.
• What you already tried: update, reinstall, Visual C++ repair, clean boot.

How to keep error 0xe06d7363 from coming back

• Keep your programs updated. Most 0xe06d7363 crashes are bugs that the program's maker fixes in a later version.
• Keep the Visual C++ packages. Do not remove old Microsoft Visual C++ entries to tidy up the list of installed apps.
• Install programs from their makers only. Repacks and copied program folders often lack files, which makes their code fail.
• Keep Windows updated. Windows 10 left support on 14 October 2025, so a Windows 10 PC without extended updates gets no more fixes.
• Keep restore points on for the system drive, so a bad change can be undone with Fix 6.

One old event 1000 with 0xe06d7363 for a program you never use needs no action. Start looking when the same program crashes again, or when a program you need does not open.

Frequently asked questions

What is error code 0xe06d7363?

It is the code Windows records when a program written in C++ ends on an exception that its own code did not catch. Microsoft lists it as STATUS_CPP_EH_EXCEPTION, a C++ exception handling exception, and the Visual C++ compiler uses it for every C++ exception. The code tells you that a C++ program crashed, not why. The program's name is in the title bar of the error window and in Event Viewer event 1000, and that program is what you fix.

What does "the exception unknown software exception (0xe06d7363) occurred in the application" mean?

It means the program named in the window's title bar threw a C++ exception that nothing in its code handled, so Windows ended it. Windows calls it unknown because it cannot read what the C++ error was. The address after "at location" points into Windows' own code and changes between runs, so it does not help. Note the program name, check event 1000 (Fix 1) and update or reinstall that program (Fix 2).

Why do several apps crash with 0xe06d7363 on a black loading screen?

When more than one program fails with the same code at the same stage, the likely cause is something they share. For C++ programs that is the Microsoft Visual C++ Redistributable, so repair every Visual C++ entry first (Fix 3). An overlay, screen recorder or other tool that loads into programs at start can cause the same pattern, which Safe Mode and a clean boot reveal (Fixes 4 and 5). Check the names in event 1000 too, in case two different programs fail for different reasons.

What is External exception E06D7363?

It is the same C++ exception, reported in the words of the program that crashed rather than by Windows. Some programs catch exceptions from Windows or from add-ons they load and show them as an external exception with the code, without the 0x. The cause is the same: C++ code inside the program or one of its add-ons threw an error nobody handled. Update or reinstall that program (Fix 2), including any plug-ins it uses, and repair Visual C++ (Fix 3).

What does [WinError -529697949] Windows Error 0xe06d7363 mean?

-529697949 is 0xe06d7363 written as a signed decimal number, so the two are the same code. Python shows errors this way: when a C++ library called from a Python script throws an exception that is not handled, Python reports it as WinError -529697949. The error is in that library or in what the script passed to it. Update the package that wraps the library and its Visual C++ runtime (Fix 3), and check the script's arguments with the package's documentation.

How do I fix the NVIDIA app error 0xe06d7363?

The code means the same there: a part of the NVIDIA app crashed on an unhandled C++ exception. Check event 1000 to see which NVIDIA file failed (Fix 1). Then install the newest NVIDIA app from NVIDIA's website over the old one, or remove it and install it again (Fix 2), and repair Visual C++ (Fix 3). If the NVIDIA installer stops with code 0xE6000000 instead, see NVIDIA installer error 0xE6000000.

Does 0xe06d7363 mean the same on Windows 7?

Yes. The code comes from the Visual C++ compiler, not from one Windows version, so it means the same on Windows 7, 10 and 11, and Event Viewer shows it in the same place. Fixes 1 to 3 work on Windows 7, with Programs and Features in Control Panel instead of the Settings app. Windows 7 lost support on 14 January 2020, and new versions of many programs and of Visual C++ no longer install on it, which can leave a crash unfixable there.

Is 0xe06d7363 caused by KERNELBASE.dll?

No. Event 1000 often names KERNELBASE.dll as the faulting module because that Windows file raises the exception on behalf of the program. It shows up next to almost every 0xe06d7363 crash and is almost never damaged. Do not download a copy of it from a DLL site, which can bring in a wrong or unsafe file. Look at the faulting application name instead and fix that program (Fix 2).

Can malware cause the 0xe06d7363 error?

It can, but not often. The code only says that a C++ program crashed, and a bug or a missing file is far more likely. Malware can still damage program files or settings so that a program crashes. If the title bar names a file you do not know, or the PC shows other odd behaviour, scan with Microsoft Defender (Fix 7). After a threat is removed, reinstall the affected program, because the damaged files do not come back on their own.

Did a Windows 10 update cause the 0xe06d7363 error?

Not as a known issue. Microsoft has not listed 0xe06d7363 as a problem of any Windows update, and the code comes from programs, not from Windows. An update can still change a driver or shared file that one program depends on. If crashes started on the day of an update, check for a new version of the program first (Fix 2), then use System Restore to a point before that day (Fix 6).