What's new 
One of our managed Macs is not getting a scheduled macOS patch enforcement through Hexnode. The failed actions are for macOS patches 26.5.2 and 26.6.1, and the action history shows an activation error similar to: Activation com.hexnode.ddm.activation.status has errors DDM is activated on the Mac, the Bootstrap Token is escrowed, and the device has plenty of free disk space. There is only one deadline enforcement automation for the affected patch. The user ended up installing the patch manually, but I’m trying to understand why the DDM enforcement did not trigger properly and whether the automation needs to run continuously.
7 Views
Replies (1)
Marked SolutionPending Review
Hexnode Expert
20 hours ago
Sep 23, 2026
Marked SolutionPending Review
This error usually indicates that the failure is occurring in Apple’s Declarative Device Management framework while macOS is processing the software update declaration.
Since the key prerequisites are already in place — Declarative Device Management is activated, the Bootstrap Token is escrowed, and the Mac has sufficient free disk space — the next likely cause is a stalled native macOS software update process.
On the affected Mac, try restarting the software update daemon with: sudo killall softwareupdated
This clears stuck background software update tasks managed by macOS. After running the command, allow the deadline enforcement automation to run again or trigger it on its next scheduled cycle. If the update was already installed manually, use the next applicable patch to confirm whether enforcement resumes normally.
Save