Share via

AADDS500 - Synchronization stopped May 30, 2026 - all diagnostics OK

Stefan Jaeckel 20 Reputation points
2026-06-08T12:59:52.67+00:00

Our Entra Domain Services managed domain (quadriga.eu, Germany West Central) has not synchronized since May 30, 2026. We have investigated all accessible components:

  • All configDiagnostics: OK
  • No NSG changes around May 30
  • No UDR/Route Table on aadds-subnet
  • Service Principal "Domain Controller Services" (2565bd9d-da50-47d4-8b85-4c97f669dc36): enabled
  • Service Principal "Azure AD Domain Services Sync" (04534565-147f-44e5-9d28-23447516d6c1): enabled
  • syncScope: All, filteredSync: Disabled, provisioningState: Succeeded
  • serviceStatus: Running
  • OnPremisesSyncEnabled: False (no Entra Connect since 2023, all users cloud-only)
  • No other active health alerts

We do not have a support plan. Can anyone help identify the cause?

Windows for business | Windows Server | Directory services | Active Directory
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Quinnie Quoc 11,485 Reputation points Independent Advisor
    2026-06-08T13:42:46.1166667+00:00

    Dear Stefan Jaeckel,

    The behavior you describe in Windows 11 25H2, where opening a new window causes previously opened ones to minimize automatically, is typically linked to the “Aero Shake” or “Focus Assist” features that were modified in recent builds. Even if your multitasking and snap settings look correct, Windows may have re‑enabled Aero Shake after the upgrade. To confirm, open Settings → System → Multitasking and disable “Title bar window shake.” Additionally, check Settings → System → Focus Assist to ensure no automatic rules are forcing background windows to minimize when a new one is opened.

    If those settings are already disabled, the next step is to verify the registry key HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\DisallowShaking. Setting this to 1 will completely disable Aero Shake behavior. After applying the change, restart Explorer or log off and back on. This issue appearing suddenly after the upgrade suggests that the cumulative update reset one of these values, so correcting the setting should restore normal window behavior.

    If my answer is useful for you, please hit Accept the answer to support me.

    Thank you,

    QQ.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.