Error 0x80000003 "A breakpoint has been reached": how to fix it

Published Sources checked By helps.wiki editorial team

0x80000003 is the Windows exception STATUS_BREAKPOINT, shown as "A breakpoint has been reached". It is a crash of the program that displayed it, not a Windows Installer (MSI) code. Start with a fresh download of the installer, then work through system file repair, a malware scan and a clean boot.

Applies to:Windows 10Windows 11
On this page

What it means

The code 0x80000003 is a core Windows exception code named STATUS_BREAKPOINT. Microsoft's protocol documentation describes it as "{EXCEPTION} Breakpoint. A breakpoint has been reached."

It is a crash of the program that showed the message, not a Windows Installer (MSI) error code. When it appears during setup, the installer itself is the program that stopped. Microsoft defines the code but has no troubleshooting page for it, so the steps below are general ones, ordered from the safest to the most involved. They come from a secondary source and are not guaranteed to fix every case.

Symptoms and causes

You are likely dealing with this problem if:

  • A dialog titled "Exception Breakpoint" saying "A breakpoint has been reached. (0x80000003) occurred in the application at location 0x..."
  • A third-party installer shows "External exception 80000003"
  • The installer or application closes right after the message
  • Event Viewer lists an Application Error with exception code 0x80000003

The usual causes, most common first:

A bug in the installer or application
This is the cause with a documented example: one vendor's installer stopped working after a Windows 10 update, and the vendor fixed it by releasing a new installer (January 2016 vendor blog). It may not apply to current systems.
A recent Windows update that older software does not handle well
Plausible, but not confirmed by Microsoft. The vendor case above is the one documented example.
A conflict with other software
Antivirus, overlays or startup programs may interfere. This is a plausible cause rather than an established one.
Corrupted system files
Damaged Windows files can make programs misbehave. Also plausible rather than proven.
Faulty RAM or GPU overclocking
Mostly reported with games. Treat it as a possible cause if other programs crash too.
Malware
Possible, so a scan is a reasonable step.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Download a fresh installer and run it as administrator

Easy

If the installer has a bug, the vendor may already have released a corrected one. A partly downloaded file can also crash.

  1. Go to the software vendor's official website and download the newest installer. Delete the old copy.
  2. Wait until the download finishes completely.
  3. Right-click the installer and choose Run as administrator.

2.Restart and install pending Windows updates

Easy

A restart clears stuck processes, and updates or driver updates may fix a compatibility problem.

  1. Restart the PC and run the installer again.
  2. Open Settings > Windows Update, click Check for updates, and install everything offered, including optional driver updates under Advanced options > Optional updates.
  3. Restart and try the installer once more.

3.Repair Windows system files

Moderate

These built-in tools replace damaged system files, which can remove one possible cause.

  1. Open Terminal (Admin) or a Command Prompt as administrator. Run the System File Checker and wait for it to finish.
    Command Promptrun as administrator
    sfc /scannow
  2. Then run DISM to repair the Windows image.
    Command Promptrun as administrator
    DISM /Online /Cleanup-Image /RestoreHealth
  3. Restart and retry the installer.

4.Run a full Microsoft Defender scan

Easy

Malware is a possible cause, and the scan is harmless to run.

  1. Open Windows Security > Virus & threat protection > Scan options.
  2. Select Full scan and click Scan now. Remove anything it finds, restart, and retry.

5.Try a clean boot to rule out conflicts

ModerateChanges settings

If the installer works with only Microsoft services running, another program was interfering.

Before you start: Note which items you disable so you can undo the changes afterwards. Remember to restore normal startup when you finish.

  1. Press WinR, type msconfig and press Enter.
  2. On the Services tab, tick Hide all Microsoft services, then click Disable all.
  3. On the General tab choose Selective startup. Open Task Manager > Startup apps and disable the startup items.
  4. Restart and run the installer.
  5. Afterwards, go back to System Configuration, choose Normal startup, re-enable the items you turned off, and restart.

6.Check the RAM and stop any GPU overclock

Moderate

Unstable memory or an overclock can crash programs in odd ways. It is mostly reported with games, so do this if other software also crashes.

  1. Press WinR, type mdsched.exe and press Enter. Choose to restart and check for problems.
  2. If you overclock the graphics card, reset it to default settings and retry.

7.Try a new administrator account or System Restore

AdvancedChanges settings

A new account shows whether the problem is tied to your user profile. System Restore can undo a recent change that started the crashes.

Before you start: System Restore changes system files and installed programs made after the restore point. Check which restore point you pick and save your work first.

  1. Create a new administrator account in Settings > Accounts, sign in to it, and run the installer there.
  2. If that fails too and the problem began after a specific change, search for Create a restore point, open System Restore and choose a point from before it started.

Check that it worked

  • The installer runs through to the end without the "Exception Breakpoint" dialog.
  • The program starts normally after installation.
  • No new Application Error with code 0x80000003 appears in Event Viewer.

If it still fails

  • Contact the software vendor. Send them the Event Viewer entry (Windows Logs > Application, source Application Error) and the installer log if it creates one.
  • If the same error appears in several unrelated programs, suspect the system: repeat the RAM check and consider a repair of Windows.
  • For other installer failures with different codes, see Installer error 1603 and Installer error 2503.

Questions

Does this mean my PC is infected or broken?

Not necessarily. The code only says a breakpoint was reached in the program that crashed. The malware scan and system checks are there to rule out other causes.

Sources

  1. NTSTATUS Values (MS-ERREF)Official · Microsoft Learn
  2. Liquid Technologies blog, January 2016 archiveOfficial · Liquid Technologies
  3. How to Fix the "A Breakpoint Has Been Reached" Error in Windows · MakeTechEasier

Browse