Skip to content

Est. 2011·Microsoft Partner 7033487·Delivery under 3 min·Support 7 days a week

Your vault is empty.

Free Fix Runtime Error 0

Malwarebytes Runtime Error 0 and error 502 during install or upgrade

10 min read Updated October 5, 2026 Antivirus & Endpoint Security

Fix it now

None of these three numbers has a published meaning: Malwarebytes’ error reference does not list Runtime Error 0 or 502, and Microsoft states that Windows Installer codes above 2000 are internal errors without authored strings. What Malwarebytes does publish is a list of install prerequisites, and most of these failures are one of them.

Only for an MSI deployment. For the ordinary installer, work through the steps instead

msiexec /i "<package>.msi" /l*v "%TEMP%\mb-install.log"
  1. Delete the installer you have and download a fresh copy from Malwarebytes’ own site, directly to this device rather than to a network drive.
  2. Confirm the device has a working internet connection, and allow ark.mwbsys.com on port 443 through the firewall.
  3. Temporarily disable any third-party antivirus, and any VPN or proxy, for the length of the install.
  4. Right-click the installer and choose Run as administrator.
  5. When it asks to restart, restart immediately, and let the installer launch itself afterwards rather than starting the app by hand.
  6. On an upgrade, keep the default installation path of C:\Program Files\Malwarebytes.
  7. If it fails again, run the Malwarebytes Support Tool and use Repair; only if that fails use Advanced, then Clean, and install again.

Windows 8.1 and earlier are not supported by current builds. If that is what you are installing on, no amount of installer troubleshooting will help.

If setup completes and the app reaches its dashboard, you are done. If not, the next section covers what setup is doing and where it gets blocked.

Why it happens

Setup unpacks its payload to a temporary location, writes program files, registers a system service and creates the data folders the service later writes to. Each of those needs administrative rights and an unobstructed file system, and a failure in any of them ends the installation. Runtime Error 0 and 502 are what you get when one fails without the installer being able to say which.

It is worth knowing what is not documented here, because it stops you chasing meanings. Malwarebytes publishes an error reference for Windows, and it lists MB-prefixed codes – MB403100 through MB403105 and MB404102 for licensing, MB404104 for the licence server, MB405100 and MB405108 for sign-in – along with named installation conditions such as the installer being run from a network drive, insufficient disk space, missing permissions, missing Windows updates and an unsupported CPU. Runtime Error 0, 502 and 2869 are not in it.

2869 in particular gets a confident explanation almost everywhere, usually that it means an MSI ran without elevation. Microsoft’s Windows Installer reference says something narrower and more honest: error codes numbered greater than 2000 are internal errors that do not have authored strings, and they can occur where the installation package has been incorrectly authored. That is all that is published. Elevation is worth checking anyway – it is cheap – but not because the number says so.

The most common practical cause is unglamorous. A previous Malwarebytes installation was removed incompletely or an upgrade was interrupted, and the remains block the new install: a service still registered and flagged for deletion, files locked by a running process, or a data folder the installer can no longer write into. Setup hits the obstruction and reports a generic failure because that is all it has.

A prerequisite Malwarebytes publishes is not met

You have this one if You have not yet checked the connection, the firewall rule, the other antivirus, or the Windows version.

  1. Confirm the device has an active internet connection.
  2. Allow ark.mwbsys.com on port 443 through the firewall.
  3. Temporarily disable third-party antivirus, and any VPN or proxy, for the duration.
  4. Confirm the Windows version is supported; devices on Windows 8.1 or earlier need upgrading first.

These are Malwarebytes’ own documented pre-install checks. Working through them takes five minutes and clears most of these failures.

Setup is running without full administrative rights

You have this one if The failure comes early, or the installer rolls back rather than completing, and you double-clicked it.

  1. Sign in with an account that is a local administrator.
  2. Right-click the installer and choose Run as administrator explicitly, rather than relying on an elevation prompt appearing.
  3. For an MSI deployment, invoke it from an elevated context, or in the system context under a management tool.
  4. Where policy restricts installs, ask for an exception for this package rather than fighting the installer.

Remains of a previous installation are in the way

You have this one if You uninstalled or upgraded Malwarebytes recently and the failure repeats at the same point every attempt.

  1. Run the Malwarebytes Support Tool and choose Repair first; it removes and reinstalls the app while saving configuration and activation key.
  2. If Repair fails, use Advanced, then Clean, which deletes all app files and configurations.
  3. Restart when prompted. A service flagged for deletion only disappears at shutdown.
  4. Install again from a freshly downloaded installer.

The restart was not taken when the installer asked

You have this one if Setup asked for a restart, you deferred it, and everything since has failed.

  1. Restart the computer now.
  2. Let the installer launch automatically after the restart; do not start the application manually.
  3. If nothing launches, run the installer again as administrator from the same local copy.

Malwarebytes documents both halves of this: restart immediately when prompted, and let the install continue by itself afterwards.

The temp folder or Windows servicing is unhealthy

You have this one if Other software also fails to install, or setup complains about writing to a temporary location.

  1. Check free space on the system drive. Installers need working room, not just the space the product occupies.
  2. Clear the user temp folder: Windows+R, %temp%, delete what will delete.
  3. Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, and restart.
  4. For an MSI deployment, capture a verbose log so the failing action is named rather than guessed at.

Full reference

Malwarebytes’ documented pre-install checks

Check Why it matters
An active internet connection on the device Setup needs to reach Malwarebytes during installation
ark.mwbsys.com allowed on port 443 Named specifically in the firewall guidance
Third-party antivirus temporarily disabled Another product can block the components being registered
VPN or proxy temporarily disabled Both can break the connection setup needs
Windows version supported Windows 8.1 and earlier need upgrading first
Installer downloaded to the local device Not run from a network drive
Default path kept on an upgrade C:\Program Files\Malwarebytes
Restart taken immediately when asked The install continues by itself afterwards

The codes Malwarebytes does publish

Worth scanning, because if what you actually have is one of these then this is the wrong article and the remedy is different.

Code What it points at
MB404104 Unable to contact the licence server; check internet and network settings
MB403102 The licence key has expired
MB403103 The key does not match the product
MB403104 The device limit has been exceeded
MB403105 The licence was refunded
MB404102 No subscription found
MB405100 Maximum sign-in attempts reached
MB405108 Sign-in credentials to verify

There is a pattern there: every published Malwarebytes code in this area is about licensing or connectivity, and none is about setup mechanics. That is a reasonable prior when you meet an unpublished install number.

Logging a packaged install

Where the deployment is an MSI, a verbose log turns a generic runtime error into a named failing action. Read the log backwards from the rollback and search for “Return value 3”, which marks the action that ended the installation.

msiexec /i "<package>.msi" /l*v "%TEMP%\mb-install.log"

Repair before Clean

  1. Download the Support Tool from Malwarebytes’ own downloads site; it needs the Microsoft .NET 4.8 Framework.
  2. Choose Repair, which removes and reinstalls the app while saving configurations and the activation key.
  3. Let it restart the machine and finish the reinstallation on its own.
  4. Only if that fails, open Advanced and choose Clean, which deletes all app files and configurations.
  5. Install again from a freshly downloaded installer, then sign in or re-enter your key.

Deployment cases worth separating

  • A managed rollout failing on every machine points at the invocation – context, elevation, package – not at the machines.
  • A managed rollout failing on some machines points at what is on those machines: another security product, or a previous installation.
  • A single home machine failing repeatedly at the same point is almost always leftovers from a previous install.
  • A single machine failing at a different point each time points at the download, the disk or the temp folder.
  • A machine that has never had Malwarebytes and fails immediately is worth checking against the supported Windows versions and CPU.

What not to do

  • Do not leave third-party antivirus disabled after the install finishes. Turn it back on and confirm it reports itself running.
  • Do not install to a non-default path on an upgrade in the hope of avoiding the leftovers; Malwarebytes documents keeping the default.
  • Do not run the installer from a network share or a mapped drive.
  • Do not repeatedly retry a download that failed once. Fetch a fresh copy instead – a truncated installer produces exactly these symptoms.
  • Do not treat 2869 as proof of an elevation problem. Check elevation because it is cheap, not because the number tells you to.

Every code this article covers

Code What it points at Source
Runtime Error 0 Seen when Malwarebytes setup aborts without naming the step that failed. It is not listed in Malwarebytes’ published error reference for Windows not published by the vendor
502 Another generic setup failure from the same family, also absent from Malwarebytes’ published error reference not published by the vendor
2869 A Windows Installer internal error. Microsoft states that codes above 2000 are internal errors without authored strings, which can occur where the package has been incorrectly authored; no elevation-specific meaning is published not published by the vendor

Confirm the fix worked

  1. Setup completes and offers to open the application rather than rolling back.
  2. The app opens to its dashboard and shows a protection status rather than a service connection error.
  3. The Malwarebytes service shows as running in services.msc.
  4. Any third-party antivirus you disabled for the install is switched back on and reports itself running.
  5. Restart the machine and confirm the app still opens cleanly.

Questions people ask about this

What does Runtime Error 0 mean?

Nothing that Malwarebytes publishes. Its error reference for Windows lists MB-prefixed licensing and connectivity codes plus named installation conditions, and this is not among them. Work the documented prerequisites rather than the number.

Is 2869 an elevation problem?

Possibly, but not because the code says so. Microsoft publishes only that installer errors above 2000 are internal errors without authored strings, which can occur where the package has been incorrectly authored. Run the installer elevated because it is a sensible check, then look at the verbose log.

Does fixing this cost money?

Not a penny. This is a broken installation rather than a licensing problem, and every step uses the vendor’s free tools or facilities already in Windows. If you were on the free product before, you will be on the free product afterwards.

Is the Support Tool safe to run?

Yes, taken from Malwarebytes’ own downloads site. It needs the Microsoft .NET 4.8 Framework. Use Repair first, because it saves your configurations and activation key; Clean deletes all app files and configurations.

The installer asked for a restart and I put it off. Does that matter?

Yes. Malwarebytes documents restarting immediately when prompted and letting the installer relaunch by itself afterwards. Deferring the restart and then starting the app by hand is a documented way to end up here.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error Bitdefender threat scanner cannot be initialized: the scan engine never loads Free Fix Windows Defender update error 0x80070643: security intelligence will not install Free Fix Malwarebytes unable to connect to the service: the app opens but does nothing License Error Trend Micro says your subscription has expired and protection has stopped
← Back to Knowledge Base