Skip to main content
Jensa
Jensa
Level 1.6: Donut
May 13, 2026
Question

Intune app disabled

  • May 13, 2026
  • 1 reply
  • 66 views

Hi!
We are currently having big issues with, what seems to be "MARsPolicyManager" on sour Samsung devices.
In the dumplogs it says that the Intune app (com.microsoft.intune) is disabled (enabled=4)
Pressing "Enable" in Google Play doesnt do anything, and no commands sent from Intune seem to help.
The Intune app is in the battery optimization list in KSP
The most critical symptom is that deployed certificates are not updated in the WiFi profile causing the device to loose conection when the current cert expires.
com.microsoft.intune is set to enabled=4 by auto_disabler. The state is permanent for the lifetime of the install: MARsPolicyManager: cancelDisablePolicy failed. package: com.microsoft.intune

The issue is quite like Disabled apps | Community

Any clues?

Br
//Niklas

1 reply

Kirk
KirkCommunity Manager
Community Manager
May 15, 2026

Hi Niklas,

This is a complex one, so I’ll do my best to help steer you in the right direction.
 

As far as I understand it, this looks like it's sitting on the Samsung Knox side of things rather than Android Enterprise or Intune. From what I can tell, MARsPolicyManager and auto_disabler are Samsung internal, and the fact that cancelDisablePolicy is failing with a permanent state suggests something in Knox's policy layer is blocking the disable from being reversed, which would be beyond what Intune or standard Android APIs can reach. But I'd caveat that with: I'm not a Knox expert, so happy to be corrected!
 

Have you raised this with Samsung Knox support yet? That feels like the right place for this to land. They should have visibility into what's triggering the disable policy on com.microsoft.intune and why it can't be cancelled, especially with the dump logs you already have.
 

In the meantime, a few things that would help build a clearer picture:

  • Which Samsung device model(s) are affected, and what One UI version and security patch level are they running?
  • Is this happening across your whole fleet or only on certain devices?
  • Did anything change around the time it started, like a firmware update, a KSP policy change, or an Intune update?
  • Are you running fully managed (Device Owner) mode or COPE?
  • What does your KSP battery optimisation config look like, and are you applying it under Device-wide policies or Work profile policies?

The more we can narrow down whether this is firmware-specific or config-triggered, the better. And if Samsung support do come back with anything, it'd be great if you could share it here as this is probably affecting others too.

Terms & ConditionsAccessibility statement