Edge not syncing "Setting up sync"

Jeremiah de Kroon 0 Reputation points
2026-10-13T19:40:57.7666667+00:00

Hi there, I've had a problem with syncing for quite some time. Earlier this year I had a sync problem that went away, it had to do with authentication and tokens. Today it is back now now with network error. It particularly happens on my MS Surface with Win 11 but does not happen on my Dell XPS with Win 10 or iPhone 13. Last week I fixed the problem by installing the stable version after being on 155.0.4283.24 Beta. A week later running 155.0.4283.45 (Official Build) and the sync problem is back. I have tried repairing edge, re-syncing, Verified DNS resolution works correctly: ISP DNS, Cloudflare (1.1.1.1), Google DNS (8.8.8.8).

Authentication generally succeeds:

  • Current auth error: None
  • Token error with: None
  • Has Token: true

Typical startup sequence:

  • Try to start sync engine
  • Load and connect Nigori controller
  • ConfigureSyncer
  • Configured DataTypeManager: Ok
  • DoStartSyncing

Initial sync requests succeed:

  • Initial GetUpdates
  • Reason: NEW_CLIENT

Server response:

  • "error_code": "SUCCESS"

Over time the logs repeatedly show intermittent failures:

  • ERR_NAME_NOT_RESOLVED
  • ERR_INTERNET_DISCONNECTED
  • ERR_CONNECTION_RESET
  • ERR_ABORTED
  • HTTP error (401)

Current encryption state appears healthy:

  • Has Keystore Key: true
  • Cryptographer Has Pending Keys: false
  • Cryptographer Ready To Encrypt: true
  • Passphrase Type: kKeystorePassphrase

This suggests the issue is no longer related to missing encryption keys.

I am out of ways to fix this and it is unsustainable to delete the profile once a day or reinstall edge regularly.

Microsoft Edge | Profile, sync, and sign in | Windows 11
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-10-13T19:41:16.3533333+00:00

    For "Setting up sync..." on the Surface while auth and encryption look healthy, treat this as a connectivity or policy issue, not a token or key issue.

    Recommended troubleshooting path:

    1. Sign out of the Edge profile, then sign back in This is the first documented step for "Setting up sync..." or "Couldn't connect to the sync server. Retrying...".
    2. Check whether the issue is actually sync or identity In edge://sync-internals, confirm there is no identity error under Credentials. A valid signed-in account is required before treating this as a sync problem.
    3. Verify sync is enabled and the device is participating
      • Open edge://sync-internals/
      • In Summary, confirm sync is enabled.
      • In Sync Node Browser > Device info, check whether the Surface appears in the sync device list.
    4. Check sign-in state Open edge://signin-internals/ and verify the browser sign-in status is healthy on the Surface.
    5. Check for policies blocking sync Open edge://policy/ and look for policies that can prevent sync. If the message is "Sync has been turned off by your administrator", make sure SyncDisabled is not set.
    6. Confirm the Surface can reach the required sync endpoints Since the failures include ERR_NAME_NOT_RESOLVED, ERR_INTERNET_DISCONNECTED, ERR_CONNECTION_RESET, and intermittent 401, verify the device can access these endpoints and that no firewall, proxy, or network filter is interrupting them:
      • https://edge.microsoft.com
      • https://api.aadrm.com for most tenants
      • https://api.aadrm.de for tenants in Germany
      • https://api.aadrm.cn for tenants in China
      • https://*.cloudmessaging.edge.microsoft.com/
      • wss://*.cloudmessaging.edge.microsoft.com/
      If the server endpoint in edge://sync-internals is empty, or the endpoint cannot be reached, that points to network or firewall interference on the Surface.
    7. Make sure Edge is on a supported current build Basic troubleshooting guidance calls for using the latest version of Microsoft Edge that supports sync features, at least 98.0.1108.43. Since the issue returned after moving between Beta and Stable, staying on the latest current Stable build is the safest path.
    8. Run a resync again Go to Settings > Profiles > Sync > Re-sync data to this device. If that still fails, use Still having sync problems? Try another option > Reset sync.
    9. If edge://sync-internals shows a cryptographer error under Type info, switch to the cloud reset path If the error appears as: Error:GenerateCryptoErrorsForTypes@../../components/sync/driver/data_type_manager_impl.cc:42, cryptographer error was encountered then the documented fix is to inspect Microsoft Entra account Key Status and reset Microsoft Edge data in the cloud if required.
    10. If the problem remains Surface-only after the checks above, collect evidence from the failing device and escalate Because sync works on the Dell XPS and iPhone, the strongest documented signal is a device-specific network, firewall, or policy condition on the Surface rather than an account-wide sync failure. If endpoint access and policy checks are clean and reset does not help, the next documented step is to contact Microsoft Edge support.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.