Edge sync permanently stuck at 'Setting up sync' (Transport State = Initializing) after every restart - MSA account, macOS and Windows 11

Question

Edge sync permanently stuck at 'Setting up sync' (Transport State = Initializing) after every restart - MSA account, macOS and Windows 11

dalong zhai 0

Environment: Microsoft Edge 156.0.4314.58 (stable) on macOS (Apple Silicon) and Windows 11; personal Microsoft account (MSA); sync server https://edge.microsoft.com/sync/v1/feeds/me/syncEntities, environment no_env-v1. The same account syncs fine in Edge for Android.

Symptom: A brand-new Edge profile syncs normally during the first session (Transport State = Active). After quitting and relaunching Edge, sync is stuck at 'Setting up sync' forever and never recovers. Reproduces 100% of the time.

edge://sync-internals shows:

Transport State: Initializing

Server Connection: not attempted

Sync Engine: Backend Status: Initialized; BlockReason: NotStarted; Syncer: Unset

DataType Manager: State: Stopped

Migration Stage: (empty)

Fetch Result: Uninitialized

MSA Account Key Download Key Result: Fail (Net Error Code = n/a, HTTP Response Code = n/a)

MSA Account Key Set Key Result: Fail

Trusted Vault Version/Epoch: 0

Passphrase Type: PassphraseType::kKeystorePassphrase

Has Keystore Key: true

Cryptographer Ready To Encrypt: true

Keystore Migration Time: 2026-11-04 17:51:23 +08

The sync_diagnostic.log for the current session contains no entries at all - the engine never even runs 'Try to start sync engine' and never issues a request to syncEntities. Local crypto is healthy (Has Keystore Key = true, Cryptographer Ready To Encrypt = true), so this is not a macOS Keychain / OSCrypt failure. Both key download and key set fail with no net error code and no HTTP status code, i.e. the failure happens before a network request is issued.

Already tried, all ineffective:

Clean reinstall; deleting ~/Library/Application Support/Microsoft Edge and the 'Microsoft Edge Safe Storage' Keychain item (3 times) - works for the first session only, breaks after restart.
Deleting the OneAuthAccount Keychain item.
Reset sync data from Microsoft servers (edge://settings/profiles/sync/reset) and Re-sync data to this device.
Signing in with password instead of passkey.
Launching with --disable-features=SyncTrustedVaultPassphrase: passphrase state becomes correct (kKeystorePassphrase, keystore key present, crypto ready) but Transport State still stays at Initializing and no server connection is ever attempted.
Turning off all encrypted data types (passwords, autofill, payments).
Windows 11 repair install / reinstall - same behavior.

Question: Could someone from Microsoft check the sync key records (Trusted Vault / MSA Account Key) for this account server-side? The vault reports epoch 0 and both key download and key set fail client-side. If the account's key material is corrupt, please reset/rebuild it; if this is a known nigori initialization defect in 156.0.4314.58, please confirm and provide a workaround. I can provide the full edge://sync-internals dump on request.

0 个注释

3 个答案

你的答案

Answer 1

Hello Carl-L,

Thank you for the reply and for clarifying this forum's scope. I understand that neither moderators nor external Microsoft employees can access backend systems, so I will not ask you to check the account's key records server-side. Routing this to the right team would help.

The fault reproduces on both desktop platforms, but the keystore state differs, so I am not assuming a single root cause.

macOS (Edge 156.0.4314.58): Trusted Vault reports Version/Epoch: 0 - no key material exists at all. Migration never advances (Migration Stage empty, Fetch Result Uninitialized), and no network request is ever issued, so proxy, VPN and network configuration are not involved.

Windows 11: the keystore is not empty. key_count=10, download_key_result=true with HTTP 200, so keys were downloaded successfully; their expiry is 2026-11-05 01:15:28, i.e. already expired. cv_debug.log shows the last successful server request at 2026-11-04 01:15:29. Three cold starts (11-04 20:17, 11-05 20:13, 11-05 20:24) produced no sync request at all. Each sync_diagnostic.log shows the same sequence: "Try to start sync engine" -> "LoadAndConnectNigoriController" -> "Control Types added:" (empty) -> "Types to download:" (empty) -> "Reset engine".

On Windows 11 I have also excluded policy and network causes: no SyncDisabled, no SyncTypesListDisabled, the SettingSync policy key does not exist; WinHTTP direct, ProxyEnable=0, DNS resolves, four Microsoft endpoints reachable on 443; personal MSA via WAM consumers, personal device, single profile.

Both platforms therefore fail at the same stage - the engine starts, then resets or stalls before any server request - but with different key states (absent versus expired). That is why I describe both.

For reference, Edge for Android on a Samsung device syncs normally; that is my own observation only.

I submitted this once via Edge's built-in Send feedback with diagnostics, without granting contact consent, so no reply is expected. I will resubmit with consent enabled and reference this thread (Q&A 6060857).

Which Feedback Hub category fits best, and is there a public issue tracker for this?

Thank you.

Answer 2

Disclaimer: This is the forum for zh-cn locale, however, I will answer you in English since the thread is in English. If you need support using your local language, please let me know.

Hello, dalong zhai

Welcome to Microsoft Q&A forum.

Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests, or ideas. To report this issue and request check on this, please submit your Feedback to the Feedback Hub app or Edge send feedback button. In the meantime, you can use a fresh Edge profile as a workaround.

Thank you for your understanding.

Answer 3

dalong zhai 0

edge_sync_dump_20261104.txt

0 个注释