Fix it now
Malwarebytes is a background service plus a window that reports on it. This message means the window opened and could not reach the service. Errors 1060 and 1072 alongside it are Windows explaining why: 1060 is the service not existing as an installed service, 1072 is it being marked for deletion and waiting on a restart.
sc query MBAMService
sc qc MBAMService
- Open services.msc, find the Malwarebytes entry in the list, and read its exact service name from Properties. Use that name in the commands rather than assuming one.
- If it is stopped, set Startup type to Automatic, click Apply, then Start.
- If Windows says the service does not exist, that is error 1060 and the installation is incomplete.
- If Windows says the service is marked for deletion, that is error 1072 and only a restart clears it. Restart before anything else.
- If it still will not connect, run the Malwarebytes Support Tool and use Repair, which removes and reinstalls the app while saving your configuration and activation key.
- Only if Repair fails should you use Advanced, then Clean, which deletes all app files and configurations, then reinstall.
The Support Tool needs the Microsoft .NET 4.8 Framework and is published on Malwarebytes’ own downloads site. Take it from there rather than from a search result.
If the dashboard opens and shows a protection status, you are done. If not, the next section explains what the two halves are doing and which of them is broken.
Why it happens
The service runs with system privileges. It owns the drivers, the definition store, the quarantine and the record of what your subscription entitles you to. The window you double-click is an ordinary unprivileged application that connects to that service locally and asks it questions. When the connection fails the window has nothing at all to display, so it shows one message regardless of the underlying cause – which is why a disabled service, a half-finished upgrade and a missing installation all look identical from the front.
Malwarebytes does not publish this message in its error reference. What it publishes there is a set of MB-prefixed codes for licensing and connectivity – MB404104 for being unable to contact the licence server, MB403102 for an expired key, MB403104 for exceeding the device limit, and so on – plus a list of installation conditions. So the message on your screen is not a documented code with a documented remedy, and the useful evidence is the Windows error alongside it rather than the wording in the window.
Those Windows errors are precise. 1060, ERROR_SERVICE_DOES_NOT_EXIST, means the specified service does not exist as an installed service: setup never completed, an uninstall took it away, or a cleanup tool removed the registration and left the program files behind. 1072, ERROR_SERVICE_MARKED_FOR_DELETE, means the service has been marked for deletion. That flag is the normal mid-upgrade state and it clears at shutdown, so it becomes a fault only when something is stopping the restart from finishing the job.
The service is set to Disabled
You have this one if The Malwarebytes entry appears in services.msc with Startup type Disabled, and the app fails instantly every time rather than intermittently.
- Open services.msc, right-click the Malwarebytes entry and choose Properties.
- Set Startup type to Automatic, click Apply, then click Start.
- If Start returns access denied, you are not running as an administrator. Sign in with an administrator account and repeat.
- Reopen the Malwarebytes window; it should connect without a reboot.
System tuning utilities and debloat scripts disable security services routinely. If you ran one recently, check what else it switched off while you are in there.
An upgrade left the service marked for deletion
You have this one if Error 1072, or the service properties are greyed out and Windows refuses to start or reinstall it.
- Close the Malwarebytes window and its tray icon.
- Restart the computer. This is not optional: the deletion flag is cleared during shutdown.
- After the restart, open the app again. If it connects, the upgrade completed itself.
- If the service is now missing entirely, you have moved from 1072 to 1060 and the installation needs repairing.
The service is not installed at all
You have this one if Error 1060, or sc query reports that the specified service does not exist, while the program folder and shortcuts are still present.
- Run the Malwarebytes Support Tool and choose Repair, which removes and reinstalls the app while saving your configuration and activation key.
- Let it restart the computer when it asks.
- If Repair does not restore the service, use Advanced, then Clean, then install again from a freshly downloaded installer.
- Sign in or re-enter your key afterwards and confirm the dashboard reports a protection status.
Repair before Clean. Clean deletes all app files and configurations, and there is no reason to lose them if Repair will do the job.
The service starts and dies within seconds
You have this one if services.msc shows it stopped again on refresh, and the Windows System log records it terminating unexpectedly.
- Open Event Viewer, go to Windows Logs then System, and filter for Service Control Manager entries around the time of the failure.
- Check any other security product’s quarantine and block list for Malwarebytes executables.
- Add an exclusion in the other product for the Malwarebytes program folder, then restart.
- If the two products cannot coexist, decide which keeps real-time duty and remove the other with its vendor’s removal tool.
Full reference
The Windows service errors, precisely
| Code | Symbolic name | Microsoft’s published text |
|---|---|---|
1060 |
ERROR_SERVICE_DOES_NOT_EXIST | The specified service does not exist as an installed service |
1072 |
ERROR_SERVICE_MARKED_FOR_DELETE | The specified service has been marked for deletion |
1053 |
ERROR_SERVICE_REQUEST_TIMEOUT | The service did not respond to the start or control request in a timely fashion |
1067 |
ERROR_PROCESS_ABORTED | The process terminated unexpectedly |
1075 |
ERROR_SERVICE_DEPENDENCY_DELETED | The dependency service does not exist or has been marked for deletion |
The last three are worth knowing because they turn up in the System log rather than in a dialog, and they narrow things usefully. 1053 is a service that started and hung; 1067 is one that started and crashed; 1075 points at something the service needs having been removed rather than at the service itself.
The two Support Tool options, and which to use
| Option | Where it is | What Malwarebytes says it does |
|---|---|---|
| Repair | The main screen of the Support Tool | Removes and reinstalls the app while saving your configurations and activation key |
| Clean | Advanced, then Clean | Deletes all app files and configurations |
- Download the Support Tool from Malwarebytes’ own downloads site.
- Install it. It requires the Microsoft .NET 4.8 Framework and will tell you if that is missing.
- Select the security app to repair and describe the issue when it asks.
- Let the repair run; it takes several minutes and restarts the computer.
- Let the reinstallation complete after the restart rather than launching anything by hand.
Reach for Clean only when Repair has failed. Repair keeps the activation key, which removes the most annoying part of a reinstall.
Commands worth having while you diagnose
| Command | What it gives you |
|---|---|
sc query <servicename> |
The current state, and a clear “does not exist” if the registration has gone |
sc qc <servicename> |
How the service is configured, including the binary it runs and its start type |
net start <servicename> |
A plain-language reason for a failure where sc returns only a number |
Read the service name off the entry in services.msc rather than trusting a name from an article, including this one. It has changed between major versions and a command aimed at a name that does not exist reports the service missing when it is perfectly healthy.
When another security product is involved
- Check the other product’s quarantine before assuming a Malwarebytes fault; a quarantined executable produces exactly this.
- Add an exclusion for the Malwarebytes program folder in the other product rather than disabling it wholesale.
- Two real-time engines competing for the same file operations is a decision, not an accident. Decide which one is in charge.
- If you are removing one of them, use its vendor’s removal tool, not Settings.
- Check Windows Security, Settings, Manage providers afterwards to see what Windows now believes is running.
What this is not
It is not a licensing problem. Malwarebytes publishes separate MB-prefixed codes for licence and account failures, and none of them presents as the service being unreachable. It is not a detection either – nothing has been found. And it is not a reason to reinstall Windows, which is a step people reach for surprisingly early when a security product will not start.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
Unable to connect to the Service |
The interface could not open a connection to the Malwarebytes background service. Malwarebytes does not list this message in its published error reference for Windows, so diagnose from the Windows service error alongside it | not published by the vendor |
1060 |
ERROR_SERVICE_DOES_NOT_EXIST: the specified service does not exist as an installed service | Microsoft Learn |
1072 |
ERROR_SERVICE_MARKED_FOR_DELETE: the specified service has been marked for deletion, and the flag is only cleared at shutdown | Microsoft Learn |
Confirm the fix worked
- The Malwarebytes window opens to its dashboard and shows a protection status rather than the connection message.
sc query <servicename>returns a state of RUNNING.- Restart the machine and open the app again; it connects without you starting anything by hand.
- A threat scan completes and writes a result to the scan report list.
- No new Service Control Manager errors for that service appear in the System log after the restart.
Questions people ask about this
Does this mean my licence has been lost?
No. Entitlement is held by the service and by the account or key behind it, not by the window that failed to open. Once the service runs again, your subscription is reported exactly as before. Write your key down before any clean reinstall so you are not hunting for it afterwards.
Do I have to buy Premium to fix this?
No, and it is worth being blunt: this repair costs nothing. The failure is in the background service, which is the same in either edition, and Malwarebytes publishes distinct MB-prefixed codes for licensing problems. Anyone telling you a purchase clears a 1060 or 1072 is wrong.
Should I use Repair or Clean?
Repair first. Malwarebytes documents it as removing and reinstalling the app while saving your configurations and activation key. Clean deletes all app files and configurations, so it is the fallback rather than the opening move.
Am I unprotected while I work through this?
If Malwarebytes was your only real-time scanner, yes, until the service runs again. Open Windows Security and confirm Microsoft Defender reports itself as on; Windows normally re-enables it when no other scanner is active.
Why does a restart fix error 1072?
Because a service marked for deletion is only actually removed during shutdown. Until then Windows will neither start it nor let anything reinstall it under the same name, which is why every other step fails until you reboot.
