Fix it now
Two unrelated things produce this and it is worth establishing which you have before touching anything. Either the protection service cannot run, or the installation has no paid subscription behind it – Malwarebytes states plainly that access to Real-Time Protection requires one, so on a free or lapsed install the toggles will never hold.
sc query MBAMService
- Open Malwarebytes and read the subscription state. If there is no active paid subscription, that is your answer and no repair will change it.
- If there is one, open the Real-Time Protection card, then Protection settings at the bottom, and turn the layers on there.
- Open services.msc and confirm the Malwarebytes service is running and set to Automatic.
- Open Windows Security, then Settings, then Manage providers, and see which product Windows currently regards as your active antivirus.
- Restart and check whether the toggles survive a genuine restart rather than a sleep.
- If they do not, run the Malwarebytes Support Tool and choose Repair, which reinstalls the app while keeping your configuration and activation key.
Exploit Protection is not available on ARM devices. On an ARM machine, a layer that will not switch on may simply not be there.
If the layers are on and survive a restart, you are done. If not, the next section separates the licensing case from the service case.
Why it happens
Malwarebytes publishes four real-time layers for Windows: Web Protection, Malware Protection, Ransomware Protection and Exploit Protection, with Exploit Protection unavailable on ARM devices. It also states that access to Real-Time Protection requires a paid subscription. Those two sentences together explain most reports of protection turning itself off after a restart, and neither of them describes a fault.
The interface does not change when a trial ends, which is what makes this so persistent. The toggles stay visible and simply refuse to hold, because switching them on asks the product to do something the installation is not entitled to do. People then spend an evening repairing a service that was never broken. Reading the subscription state in the app first is thirty seconds and saves the evening.
The genuine technical fault is a service that cannot run, and the codes here come from Windows rather than from Malwarebytes. 1056, ERROR_SERVICE_ALREADY_RUNNING, means an instance of the service is already running – usually a stale one left by a shutdown that did not complete. 1057, ERROR_INVALID_SERVICE_ACCOUNT, means the account name is invalid or does not exist, or the password is invalid for the account named, which is what a migration or a tuning script that rewrote the service configuration produces.
1921 is the odd one out. It is widely quoted as the installer being unable to stop a service in order to replace it, and that may well be what it is, but the row is not something we could retrieve from Microsoft’s published error table and Malwarebytes does not list the code in its own error reference. Treat it as an installer failure during an upgrade, work it as one, and do not build a diagnosis on a meaning nobody publishes.
There is no paid subscription behind this installation
You have this one if The app shows no active subscription or an ended trial, and the real-time toggles refuse to hold whatever you do to the service.
- Confirm the state on the subscription page in the app rather than guessing from the dashboard.
- Open Windows Security and confirm Microsoft Defender reports itself as on, so the machine is not left with no real-time cover.
- If you want the Malwarebytes layers back, apply a paid subscription to this installation and restart.
This is not a repairable fault, and it is worth saying so plainly. Removal tools, service resets and reinstalls will not restore a feature the installation is not entitled to.
An upgrade could not replace the service
You have this one if Error 1921 during an update, after which protection no longer survives a restart.
- Restart the machine so any pending file replacement completes.
- Run the Support Tool and choose Repair, which removes and reinstalls the app while saving configuration and activation key.
- If Repair fails, use Advanced then Clean, restart, and install fresh.
- Re-apply your subscription and restart once more before deciding whether it is fixed.
The service is configured to run as the wrong account
You have this one if Error 1057, or the service properties show a named user account under Log On rather than the system account.
- Open services.msc, open the Malwarebytes service Properties and go to the Log On tab.
- Select Local System account, apply, and start the service.
- If the setting is greyed out or reverts, a management policy is setting it; check with whoever administers the machine.
- Reinstall if the configuration cannot be corrected by hand.
Microsoft’s published text for 1057 covers an invalid password as well as an invalid account name, so a service set to run as a real user whose password changed produces it too.
A stale instance is blocking a clean start
You have this one if Error 1056, or the service shows as stopping and never reaches stopped.
- Restart the machine rather than trying to kill the process; that is the fastest reliable way to clear it.
- If it recurs after every shutdown, look at fast startup, which can preserve a stuck service state across what looks like a restart.
- Use Restart rather than Shut down and start again, because a restart bypasses fast startup.
Another product holds the antivirus position
You have this one if Windows Security lists a different product as your antivirus, and Malwarebytes is running alongside rather than in charge.
- Open Windows Security, Settings, Manage providers and read what Windows believes.
- Decide which product is doing real-time work; running two full engines against the same file operations is a choice with a cost.
- If a product you already removed is still listed, run its vendor’s removal tool to clear the registration, then restart.
Full reference
What is in Real-Time Protection
| Layer | Platform | Notes |
|---|---|---|
| Web Protection | Windows and macOS | |
| Malware Protection | Windows and macOS | On macOS it needs full disk access granted |
| Ransomware Protection | Windows only | |
| Exploit Protection | Windows only | Not available on ARM devices |
| App Block | macOS only | Needs full disk access granted |
Malwarebytes states that access to Real-Time Protection requires a paid subscription. Every layer in that table sits behind it.
Turning the layers on where you actually can
- Open the application.
- Select the Real-Time Protection card.
- Click Protection settings at the bottom.
- Toggle on the protection layers you want.
- Restart, and confirm they are still on afterwards – that is the test that matters, not the toggle moving.
The service errors and what they mean
| Code | Symbolic name | Microsoft’s published text |
|---|---|---|
1056 |
ERROR_SERVICE_ALREADY_RUNNING | An instance of the service is already running |
1057 |
ERROR_INVALID_SERVICE_ACCOUNT | The account name is invalid or does not exist, or the password is invalid for the account name specified |
1921 |
Not retrievable from Microsoft’s published table | An installer failure while a service is being replaced; no vendor meaning published |
Fast startup, and why a restart is not a shutdown
Windows fast startup hibernates the kernel session at shutdown and restores it at power-on, which is why a machine that has been shut down and started again can come back with the same stuck service state it had before. A restart does not use fast startup. When you are testing whether protection survives, use Restart rather than Shut down, or you are testing something different from what you think.
Running Malwarebytes alongside another antivirus
- Windows Security, Settings, Manage providers shows what Windows believes is in charge. Start there rather than in either product.
- A registration left behind by a product that is no longer installed is enough to change how the machine behaves.
- Two full real-time engines examining the same file operations costs performance, and the cost is most visible on file-heavy work like builds and backups.
- If the machine feels slow after adding a second product, test by turning one off rather than by adding exclusions blindly.
- Decide deliberately. Running two is a legitimate choice; running two by accident is how people end up with neither working.
When the answer is licensing, what the honest options are
- Keep the installation as an on-demand scanner and rely on Microsoft Defender for real-time cover. This is free and coherent.
- Remove Malwarebytes entirely and rely on Defender. Also free, and simpler.
- Buy a subscription because you specifically want the Malwarebytes layers. Reasonable, if that is the actual reason.
- What is not coherent is leaving a lapsed installation in place, believing it is protecting the machine in real time, and periodically repairing a service that is doing exactly what it should.
When a licence is the actual fix
If the answer turns out to be the first cause, a Malwarebytes Premium subscription is what restores the real-time layers, and Arco can supply one and work out how many devices your household or office actually needs covered. The alternatives deserve saying plainly, though. The free product still works as an on-demand scanner at no cost, and Microsoft Defender is built into Windows, does real-time scanning, and costs nothing. Buy Premium because you want its particular layers – the ransomware and exploit protection in particular – rather than because you think the machine is otherwise defenceless. It is not.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
1921 |
Seen during a Malwarebytes upgrade when a service cannot be replaced. It is not listed in Malwarebytes’ error reference, and Microsoft’s published Windows Installer message table row for it could not be retrieved, so treat it as an installer failure rather than a diagnosis | not published by the vendor |
1057 |
ERROR_INVALID_SERVICE_ACCOUNT: the account name is invalid or does not exist, or the password is invalid for the account name specified | Microsoft Learn |
1056 |
ERROR_SERVICE_ALREADY_RUNNING: an instance of the service is already running | Microsoft Learn |
Confirm the fix worked
- The app shows an active paid subscription, if that is what you expect it to say.
- The Real-Time Protection layers are on under Protection settings.
- They are still on after a full Restart, rather than after a sleep or a fast-startup shutdown.
- The Malwarebytes service reports RUNNING after that restart.
- Windows Security, Manage providers shows a coherent picture, with no product listed as active that you have already removed.
Questions people ask about this
Does the free Malwarebytes have real-time protection?
Malwarebytes states that access to Real-Time Protection requires a paid subscription. That is the single most common reason people find protection off after a restart, and it is not a fault to repair.
Which layers should I have?
Malwarebytes publishes four for Windows: Web Protection, Malware Protection, Ransomware Protection and Exploit Protection. Exploit Protection is not available on ARM devices, so on an ARM machine one of them will be absent by design.
Can I run Malwarebytes alongside another antivirus?
Many people run it beside Microsoft Defender. Whether it is worth doing depends on whether you want two real-time engines competing for the same file operations. Check Windows Security, Manage providers to see what Windows thinks is in charge before deciding.
My trial ended. Do I have to buy something immediately?
No. Leave it as an on-demand scanner or remove it, and confirm Microsoft Defender is on in Windows Security. That is a legitimate, cost-free position. Buy a subscription if you specifically want the Malwarebytes real-time layers back.
Why does the toggle appear at all if the feature is not licensed?
The interface is the same either way, so the controls stay visible and refuse to hold. That is why people spend an evening repairing a service that was never broken.
