Here’s a question that sounds simple and isn’t: will your antivirus actually protect you on a Snapdragon laptop? With Malwarebytes the answer is genuinely good news — native ARM support arrived in early 2025, the installer detects your processor automatically, and ARM-based Windows 11 devices are officially supported. But “supported” has fine print: two specific features don’t exist on ARM, old version-4 installs predate ARM support entirely, and the usual antivirus headaches (update failures, protection that won’t start, fights with Windows Security) still apply. It shares troubleshooting DNA with Cocreator problems in Paint : a feature set that looks complete until you discover which pieces are quietly absent on ARM.

The most important thing to understand is the difference between “installs fine” and “protects fully.” An antivirus that launches but whose real-time drivers never load is worse than no antivirus — it gives you confidence you haven’t earned. On ARM, that distinction matters more than on Intel, because kernel-level protection components must be ARM64-native, and older builds simply don’t have them. For the mixed-architecture middle ground — apps that straddle ARM and x64 — ARM64EC apps explained and fixed is worth a read alongside this guide.

This guide gives you the honest compatibility picture first, then fixes the real problems: wrong builds, protection that won’t start, update errors, and AV conflicts. It even parallels Notepad++ issues on ARM64 Windows — another case where the fix starts with verifying you actually have the ARM build, not the emulated one. Let’s make sure your protection is real.

Why this happens

  • Old v4 builds predate ARM support: Version 4’s requirements explicitly excluded ARM — only the current v5 line supports it.
  • Two features are ARM-excluded by design: Exploit protection and rootkit scan aren’t available on ARM; their absence is expected, not a bug.
  • Kernel protection must be ARM64-native: Real-time drivers can’t be emulated, so wrong builds fail silently at the protection layer.
  • Update servers hiccup: Database and component updates fail for ordinary network reasons unrelated to ARM.
  • Two real-time engines collide: Malwarebytes plus another active antivirus causes slowdowns, blocks, and disabled protection.
  • Windows Security confusion: Defender’s automatic step-back sometimes misfires, leaving both — or neither — in charge.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm you’re on the ARM-native build

Everything else is pointless on the wrong build. The current Malwarebytes installer auto-detects ARM, but upgrades and migrations can leave ancient v4 installs behind.

  1. Open Malwarebytes > Settings > About and check your version — you want the current v5 line.
  2. If you see version 4 (or the About screen looks years out of date), you’re on the pre-ARM build.
  3. Download the current installer from Malwarebytes’ official site — it detects ARM automatically.
  4. Install over the old version, or uninstall v4 first for a cleaner result, then reboot.
  5. Reopen Malwarebytes and confirm the version now shows the current v5 release.

Fix 2: Verify real-time protection actually starts

An antivirus dashboard can look healthy while protection is off. Check the protection layer itself, not just the app window.

  1. On the Malwarebytes dashboard, look at the Real-Time Protection toggles — all should be on (Premium/trial).
  2. If a toggle won’t stay on, note which one: web, malware, ransomware, or exploit protection.
  3. Remember: exploit protection is not available on ARM at all — its absence is expected, per Malwarebytes’ own docs.
  4. For other toggles that refuse to start, reboot and try again before assuming deeper trouble.
  5. If protection still won’t enable, skip to Fix 5 (AV conflict) — that’s the most common cause.

Fix 3: Fix database and component update errors

Out-of-date protection is nearly as bad as no protection. Update failures are usually network or service issues, not ARM issues.

  1. In Malwarebytes, go to Settings > General > Check for updates and watch the exact error, if any.
  2. Confirm your internet works and no VPN or firewall is blocking Malwarebytes’ update servers.
  3. Restart the Malwarebytes Service: open Services (services.msc), find it, and restart it.
  4. If updates still fail, reboot the laptop and retry — stuck update states often clear on restart.
  5. As a last resort, reinstall with the current installer (Fix 6), which resets the update components.

Fix 4: Run a proper threat scan

Once protection is verified, confirm scanning works end to end. A scan that completes cleanly proves the engine, drivers, and database are all cooperating.

  1. Update databases first (Fix 3), then go to the Dashboard and run a Threat Scan.
  2. Let it complete fully — don’t judge ARM performance by the first scan, which is always slowest.
  3. If the scan stalls at the same point repeatedly, reboot and try a Quick Scan instead.
  4. Note: rootkit scanning isn’t offered on ARM — don’t go hunting for the option; it’s excluded by design.
  5. Quarantine anything found, reboot, and rescan to confirm the system is clean.

Fix 5: Resolve antivirus conflicts

Two real-time antivirus engines on one machine is the top cause of “protection won’t stay on.” Pick one primary and demote the other.

  1. Check Settings > Apps for any other antivirus with real-time protection (Norton, McAfee, Avast, etc.).
  2. Decide: Malwarebytes as primary, or the other product as primary — not both.
  3. If Malwarebytes is primary, uninstall the other AV completely (not just disable) and reboot.
  4. Verify Windows Security shows Malwarebytes as the active provider and Defender in passive mode.
  5. If you’d rather keep another AV primary, set Malwarebytes Free as an on-demand second-opinion scanner with real-time off. Microsoft’s Windows support hub explains how Defender’s passive mode is supposed to behave.

Fix 6: Clean reinstall with the official removal tool

When builds are tangled or services are corrupted beyond settings-level repair, a full purge and fresh install is fastest.

  1. Download Malwarebytes’ official support/removal tool from their site.
  2. Run it to fully uninstall, choosing the clean-removal option, then reboot.
  3. Download the current installer fresh — it will auto-detect your ARM processor.
  4. Install, activate your license (or start the trial), and update databases immediately.
  5. Re-verify real-time protection toggles (Fix 2) before calling it done.

Closing

Malwarebytes on ARM is a genuine success story — native support, auto-detecting installer, and officially the same level of protection — with exactly two documented exceptions: no exploit protection, no rootkit scan. Verify you’re on the current ARM-native build, confirm real-time protection truly starts, and keep it the only real-time engine on the machine. Do that, and your Snapdragon laptop is as well defended as any Intel machine — no asterisks required beyond the two you’ve now memorized.

Frequently asked questions

Does Malwarebytes support ARM Windows laptops?
Yes — Malwarebytes added native ARM support for Windows in early 2025, and ARM-based Windows 11 devices are officially listed in its system requirements. The installer automatically detects an ARM processor and installs the right build. Windows 11 is recommended; older version 4 installers did not support ARM, so upgrade if you’re on v4.
Are any Malwarebytes features missing on ARM?
Two, according to Malwarebytes’ own help center: exploit protection and rootkit scan aren’t available on ARM-based devices. Everything else — threat scans, real-time protection, web protection, ransomware protection, tamper protection — works the same. Malwarebytes states ARM devices get the same level of protection and aren’t more vulnerable.
Real-time protection won't turn on — what do I do?
First confirm you’re running the current ARM-native build, not an old v4 install carried over from an Intel machine. Then check for conflicts: two antivirus products with real-time protection will fight each other. Fix 2 verifies the build; Fix 5 resolves AV conflicts.
Should I keep Windows Security on alongside Malwarebytes?
Windows Security (Defender) automatically steps back when it detects another antivirus with real-time protection, which is the safe arrangement. Running two real-time engines simultaneously causes slowdowns and false blocks. Use Malwarebytes as your primary real-time protection or as an on-demand second-opinion scanner — not both at once.