The platform is up, but one dependency path is not.

Use this when devices age out of trust or authenticate inconsistently even though they still appear joined and reachable. These issues are easy to misread because the operating system still responds while one control path, runtime dependency, or trust assumption is already out of alignment.

The symptom usually appears downstream from the real change.

• Kerberos assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• Credential Guard assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• Machine Password assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• Authentication assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.