macOS FileVault policy shows devices as non-compliant in HexnodeSolved

Participant
Discussion
1 day ago Jul 27, 2026

I’m trying to enforce FileVault on macOS devices using a Hexnode policy, but the devices keep showing as non-compliant. The policy is assigned to the Macs, but compliance is not updating as expected. Is there a specific FileVault setting that needs to be configured for this?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
20 hours ago Jul 27, 2026
Marked SolutionPending Review

For macOS FileVault compliance, check the FileVault policy configuration and make sure the option “Skip enabling FileVault on user login” is enabled with the value set to “0”.

After updating the setting:

  1. Confirm that the FileVault policy is linked to the affected macOS devices.
  2. Run the “Scan Device” remote action for the devices.
  3. Once the scan completes, check the device compliance status again.

Setting the value to “0” ensures that FileVault enablement is not skipped during user login, allowing the policy state to be evaluated correctly after the device scan.

Marked SolutionPending Review
Participant
18 hours ago Jul 27, 2026
Marked SolutionPending Review

The wording of that setting confused me at first. So even though it says “Skip enabling FileVault on user login,” setting it to 0 means it won’t skip the FileVault prompt, right?

Marked SolutionPending Review
Hexnode Expert
3 hours ago Jul 28, 2026
Marked SolutionPending Review

Correct. A value of “0” means the skip behavior is disabled. After saving the policy change, the important part is to make sure the updated policy is applied to the device and then trigger a device scan so Hexnode refreshes the compliance status.

Save