SCCM Update Compliance Inconsistency – Required vs Not Required Status

Hello,

We are managing an environment with approximately 14,000 clients via SCCM.

For the March 2026 updates, we are observing an inconsistency:

• Around 4,700 clients show the update as Required
• Approximately 7,000 clients show the same update as Not Required

However, on the clients marked as Not Required, when we manually download the update from the Update Catalog and install it, the update installs successfully without any issues.

This raises a concern regarding the accuracy of the compliance state evaluation.

Our questions are:

1. What could cause a client to report an update as “Not Required” while still being able to install it manually?
2. Could this be related to detection logic, supersedence rules, or scan cycle issues?
3. What steps would you recommend to ensure accurate compliance status across all clients?

We would appreciate your guidance on identifying the root cause and resolving this inconsistency.

Best regards,Hello,

We are managing an environment with approximately 14,000 clients via SCCM.

For the March 2026 updates, we are observing an inconsistency:

• Around 4,700 clients show the update as Required
• Approximately 7,000 clients show the same update as Not Required

However, on the clients marked as Not Required, when we manually download the update from the Update Catalog and install it, the update installs successfully without any issues.

This raises a concern regarding the accuracy of the compliance state evaluation.

Our questions are:

1. What could cause a client to report an update as “Not Required” while still being able to install it manually?
2. Could this be related to detection logic, supersedence rules, or scan cycle issues?
3. What steps would you recommend to ensure accurate compliance status across all clients?

We would appreciate your guidance on identifying the root cause and resolving this inconsistency.