Skip to content

Endpoint security

Investigate a noncompliant Windows device

Find the failed compliance requirement, resolve stale device state and verify that legitimate access returns after an approved fix.

By BugSnaps · Updated

Add BugSnaps as a preferred source on Google(opens in a new tab)

Want more of our security guides? Select BugSnaps and confirm your choice on Google.

Direct answer

Identify the exact failed requirement and evaluation time, verify the device's effective state, correct the underlying issue through the owning team and recheck compliance and access.

Read the failed requirement

Confirm the device record, user, policy, status and last evaluation. A missing check-in or unassigned policy is different from a measured setting that fails. Ask the device owner about recent updates, enrollment changes and pending restarts.

Check the actual device

Use approved management and local tools to compare the relevant effective state with the policy. Microsoft documents troubleshooting for Conditional Access and compliance integration; a device may need a successful management sync before its new state is reported.

Reference: Microsoft: Troubleshoot Intune Conditional Access.

Fix and test the outcome

Coordinate the specific fix with its owner rather than disabling the whole compliance policy. Allow the required sync or restart, verify the device result, then repeat the authorized access test. Record devices that remain offline and time-limited exceptions with an approver.

Example: a pending restart

A device may report a noncompliant operating-system requirement while an approved update is waiting for restart. Confirm the installed build and restart indication with its owner, schedule the restart and allow policy reevaluation. If access remains blocked, inspect the specific remaining requirement rather than assuming the restart fixed every issue.

Assessment limits

Compliance policies are organization-specific and can report stale or unavailable data. Restoring access does not prove every other control is effective.

Frequently asked questions

Does noncompliant always mean a device is compromised?

No. It means a policy requirement or evaluation condition was not met; investigate the specific reason.

Why can compliance remain stale after a fix?

The device may need a sync, restart or reevaluation, or a different condition may still fail.

Should the entire policy be disabled to restore access?

Investigate the failed condition and use the approved exception process if a temporary workaround is needed.

Primary sources and further reading

These guides combine published security guidance with practical assessment planning. Adapt checks to the owner's policy, environment, and authorized scope.

This guide was prepared with AI assistance using the linked sources and illustrative examples. Check current vendor guidance and your environment before making changes.

Review your Windows endpoint.

EndpointRadar provides a point-in-time view of an authorized Windows machine. Review the report alongside its collection limits and your organization's policy.

Explore EndpointRadar