Edge not syncing "Setting up sync"

Question

Edge not syncing "Setting up sync"

Jeremiah de Kroon 50

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.

Martin Wallenböck 25 Reputation points

2026-10-21T20:40:57.7366667+00:00
Same issue here – reproducible, affects multiple accounts, devices and Edge channels.

Since ~2 weeks, Edge sync for my personal Microsoft account (MSA) is stuck at “Setting up sync” after every browser restart. Business (Entra) profiles on the same machines sync fine. Edge on Android works.

Reproduction:

Sign out of the Edge profile, sign in again → sync works (Transport State: Active, all types Running, MSA key download Success, HTTP 200).

Close Edge completely and reopen → stuck again at “Setting up sync”.

edge://sync-internals after restart:

Transport State: Initializing

Auth Error: OK / Last Token Request Result: OK (tokens are fine)

MSA Account Key Status: Download Key Result: Fail, HTTP Response Code: n/a, Net Error Code: n/a → no request is sent to the server at all

Set Key Result: Fail

Sync Engine: BlockReason: NotStarted; DataType Manager: Stopped

Cryptographer Ready To Encrypt: true, Has Keystore Key: true

Next Key Request Time: 24h after the last successful download

Already ruled out:

Policies (none affecting sync), clear-on-close settings (all off), cookie exceptions (none)

Extensions, Windows Credential Manager cleanup

Server-side sync reset (completed successfully, full re-upload, fresh keystore key) → still fails after restart

Edge Dev and Canary: same behavior

A different MSA account on a different device: same behavior

Version: Edge Stable 155.0.4283.62, Windows 11.

This looks like a client-side regression in the MSA key handling on startup, very similar to the sync bug in April 2026 (related to the Workspaces v2 migration), which Microsoft fixed then. Feedback with sync-internals dumps has been sent multiple times via Alt+Shift+I.

Workaround: sign out/in after every browser start.

Please escalate to the Edge sync team.Same issue here – reproducible, affects multiple accounts, devices and Edge channels.

Since ~2 weeks, Edge sync for my personal Microsoft account (MSA) is stuck at “Setting up sync” after every browser restart. Business (Entra) profiles on the same machines sync fine. Edge on Android works.

Reproduction:

Sign out of the Edge profile, sign in again → sync works (Transport State: Active, all types Running, MSA key download Success, HTTP 200).

Close Edge completely and reopen → stuck again at “Setting up sync”.

edge://sync-internals after restart:

Transport State: Initializing

Auth Error: OK / Last Token Request Result: OK (tokens are fine)

MSA Account Key Status: Download Key Result: Fail, HTTP Response Code: n/a, Net Error Code: n/a → no request is sent to the server at all

Set Key Result: Fail

Sync Engine: BlockReason: NotStarted; DataType Manager: Stopped

Cryptographer Ready To Encrypt: true, Has Keystore Key: true

Next Key Request Time: 24h after the last successful download

Already ruled out:

Policies (none affecting sync), clear-on-close settings (all off), cookie exceptions (none)

Extensions, Windows Credential Manager cleanup

Server-side sync reset (completed successfully, full re-upload, fresh keystore key) → still fails after restart

Edge Dev and Canary: same behavior

A different MSA account on a different device: same behavior

Version: Edge Stable 155.0.4283.62, Windows 11.

This looks like a client-side regression in the MSA key handling on startup, very similar to the sync bug in April 2026 (related to the Workspaces v2 migration), which Microsoft fixed then. Feedback with sync-internals dumps has been sent multiple times via Alt+Shift+I.

Workaround: sign out/in after every browser start.

Please escalate to the Edge sync team.
Carsten Svendsen 0 Reputation points

2026-10-24T07:17:12.9633333+00:00

I have the same problem. Syncing hasn't worked for at least a week now. I just signed out and back in as the comment above suggested and it did sync my favorites so that's nice. But after every browser start? Ridicoulous. Must be fixed yesterday!!!!
Martin Wallenböck 25 Reputation points

2026-10-25T07:42:58.2733333+00:00

it looks like that thousands of microsoft employees never use Microsoft products. otherwise its not believable that such major issue is so long not fixed.
Alexander Vadovič 0 Reputation points

2026-10-25T15:36:54.2633333+00:00

Same issue here, even affecting Fedora
R U 0 Reputation points

2026-10-26T17:53:38.77+00:00

Same issue here. Edge not syncing after restart althogh sign out and in again from edge profile activates sync.

In my particular case, the problem first occured when I forced Edge to not using my outlook.com accountname to sign in to my edge profile (and my onedrive), but my normal private accountname I use for Windows Login on my computer and online (which is the primary accountname in my Microsoft Account).

Anyone else who experiences the Edge syncing problem in relation with outlook.com accountnames?
Magnus Stensson 35 Reputation points

2026-10-27T11:01:05.2766667+00:00

Yes, this has happened the last couple of weeks for me. Syncing between a couple of android devices and 2 laptops. Its been working fine for years, but now it stops. Each device gets randomly stuck on setting up sync. Removing profiles, deleting data, resyncing to servers, and every other tip available online only resolves the first resync on the device, then next time I look its back to setting up sync. Has M-soft changed something with cloud sync recently?
Daniel Burkhard 0 Reputation points

2026-10-28T15:56:04.4233333+00:00

I'm having the same problem on several Windows 11 systems
MK 0 Reputation points

2026-10-28T16:56:57.8966667+00:00

我也遇到了同样的问题
在几台windows11上的edge都无法完成同步

同样的全部显示为正在设置同步
Rune Venes 0 Reputation points

2026-10-28T18:16:46.2866667+00:00

Same problem here.
Oli Cooke 10 Reputation points

2026-10-28T20:26:01.2266667+00:00

Same problem
Oli Cooke 10 Reputation points

2026-10-28T20:26:18.5633333+00:00

Same problem
Yo Yoshi 0 Reputation points

2026-10-28T22:48:02.2933333+00:00

Same problem
Aaron Boeker 0 Reputation points

2026-10-28T23:03:03.51+00:00

Same problem here.
Martin Wallenböck 25 Reputation points

2026-10-29T08:11:00.7666667+00:00
Update (Oct 29, 2026): still not fixed, no response from Microsoft yetThe issue persists unchanged for 3 weeks now on Edge Stable 155.0.4283.62. Additional findings:

Dev and Canary are affected as well, so a newer client version alone does not seem to fix it.

Server-side sync reset does not help. After a completed reset with full re-upload and a fresh keystore key, sync still breaks on the next browser restart.

Different MSA accounts on different devices show the same behavior. Work/Entra accounts and Edge on Android are not affected.

After restart, edge://sync-internals shows MSA Download Key Result: Fail with HTTP Response Code n/a. No key request is sent to the server at all, and the sync engine stays at BlockReason NotStarted until a sign-out/sign-in forces a new key fetch.

Reports from other users (deskmodder.de) say that downgrading to Edge 154 restores sync, which points to a regression introduced in 155.

Dr. Windows reports that after the sign-out/in workaround, the servers sometimes return an older bookmark state. Affected users should check their favorites for old or duplicate entries.

There appear to be ongoing changes to Edge sign-in and sync infrastructure, which may be related:

Dr. Windows reports that Microsoft seems to be working on the Edge sync infrastructure again and sees indications of a server-side problem.

Microsoft is adding sign-in with Apple and Google accounts to Edge on Windows (mentioned in the Stable release notes).

According to deskmodder.de, the Direct WAM sign-in implementation on Windows is being retired with Edge 157 in favor of OneAuth (which still uses WAM internally).

These changes may coincide with the start of this regression, so the MSA key handling may have been affected by them.

This is the same pattern as the Edge 147 MSA sync bug in April 2026.

Microsoft, please acknowledge this issue and share a status or ETA. Many personal-account users are affected across Windows and macOS, and signing out/in after every browser start is not a workable solution.
Petrus 5 Reputation points

2026-10-29T12:20:06.53+00:00

same problem here
Richard Bottiglieri 10 Reputation points

2026-10-29T14:42:04.7266667+00:00

Same problem here. Ever since Edge 155, I believe. Still broken in Edge 156.0.4314.50.
Randy 💢 0 Reputation points

2026-10-30T16:00:53.8033333+00:00

It appears to be working again on Canary's build 159.0.4372.0.
Y Z 0 Reputation points

2026-11-01T15:22:34.0933333+00:00

The issue still persists.
I2 Zerro 0 Reputation points

2026-11-02T09:36:57.01+00:00
Additional reproduction of the restart-dependent personal-MSA sync failure, tested on November 1, 2026.

Environment: Windows 11 Pro 25H2 (build 26200.9711), Edge Stable 156.0.4314.58, and isolated Beta 157.0.4341.30 profiles. These are historical test versions, not a fresh inventory.

Interactive sign-in temporarily restores sync and data types show Running. Closing and reopening Edge without signing out returns sync to Initializing/Not Running.

Failing-state observations:

Signed In, Consented for Sync; refresh token present; no persistent auth error.

MainSyncToken OK / Has Token=true. In later failing captures, KeyDataToken was also OK / Has Token=true.

Server Connection: not attempted.

MSA Download Key Result: Fail; Set Key Result: Fail; HTTP Response Code and Net Error Code: n/a.

DataType Manager: Stopped; Cryptographer Ready To Encrypt: true; no pending keys or passphrase requirement shown.

No Edge policies were configured at the initial capture. Re-sync, cloud sync reset, browsing-data cleanup, and isolated Stable/Beta profiles did not provide a lasting fix. In an isolated key-reinitialization test, two account keys were retrieved/installed, but the engine still did not start.

Consumer support documented the unresolved issue but could not escalate internally. No second MSA was available for my comparison tests. The original diagnostic archive was subsequently deleted; fresh traces can be collected through an appropriate secure channel.

Does the Edge Sync team recognize this startup/key-initialization pattern? What focused before/after-restart diagnostics would help distinguish a client regression from account provisioning or a backend issue?

Prepared with AI assistance from my recorded troubleshooting observations; no account-specific identifiers or raw logs are included.
Richard Bottiglieri 10 Reputation points

2026-11-02T14:48:51.0833333+00:00

This is currently fixed in the Dev channel (Edge major version 158). Still broken in Stable and Beta channels. It's highly unlikely that we'll get a fix before Edge 158 hits the Stable channel, which is honestly pathetic.
Eduardo 0 Reputation points

2026-11-02T20:28:28.48+00:00

More than 15 days have passed, and Microsoft still hasn’t fixed the synchronization issue. Edge is a very good browser, but this is unacceptable. In the end, I’ll have to go back to using Chrome, which I don’t particularly like, but it never let me down when it came to synchronization, including syncing across devices, which always happened instantly.
Raf 0 Reputation points

2026-11-03T02:30:41.2966667+00:00

Same problem. Microsoft - hotfix please.

Your answer

Carsten Svendsen 0 Reputation points

2026-10-24T07:17:12.9633333+00:00

I have the same problem. Syncing hasn't worked for at least a week now. I just signed out and back in as the comment above suggested and it did sync my favorites so that's nice. But after every browser start? Ridicoulous. Must be fixed yesterday!!!!
Martin Wallenböck 25 Reputation points

2026-10-25T07:42:58.2733333+00:00

it looks like that thousands of microsoft employees never use Microsoft products. otherwise its not believable that such major issue is so long not fixed.
Alexander Vadovič 0 Reputation points

2026-10-25T15:36:54.2633333+00:00

Same issue here, even affecting Fedora
R U 0 Reputation points

2026-10-26T17:53:38.77+00:00

Same issue here. Edge not syncing after restart althogh sign out and in again from edge profile activates sync.

In my particular case, the problem first occured when I forced Edge to not using my outlook.com accountname to sign in to my edge profile (and my onedrive), but my normal private accountname I use for Windows Login on my computer and online (which is the primary accountname in my Microsoft Account).

Anyone else who experiences the Edge syncing problem in relation with outlook.com accountnames?
Magnus Stensson 35 Reputation points

2026-10-27T11:01:05.2766667+00:00

Yes, this has happened the last couple of weeks for me. Syncing between a couple of android devices and 2 laptops. Its been working fine for years, but now it stops. Each device gets randomly stuck on setting up sync. Removing profiles, deleting data, resyncing to servers, and every other tip available online only resolves the first resync on the device, then next time I look its back to setting up sync. Has M-soft changed something with cloud sync recently?
Daniel Burkhard 0 Reputation points

2026-10-28T15:56:04.4233333+00:00

I'm having the same problem on several Windows 11 systems
MK 0 Reputation points

2026-10-28T16:56:57.8966667+00:00

我也遇到了同样的问题
在几台windows11上的edge都无法完成同步

同样的全部显示为正在设置同步
Rune Venes 0 Reputation points

2026-10-28T18:16:46.2866667+00:00

Same problem here.
Oli Cooke 10 Reputation points

2026-10-28T20:26:01.2266667+00:00

Same problem
Oli Cooke 10 Reputation points

2026-10-28T20:26:18.5633333+00:00

Same problem
Yo Yoshi 0 Reputation points

2026-10-28T22:48:02.2933333+00:00

Same problem
Aaron Boeker 0 Reputation points

2026-10-28T23:03:03.51+00:00

Same problem here.
Petrus 5 Reputation points

2026-10-29T12:20:06.53+00:00

same problem here
Richard Bottiglieri 10 Reputation points

2026-10-29T14:42:04.7266667+00:00

Same problem here. Ever since Edge 155, I believe. Still broken in Edge 156.0.4314.50.
Randy 💢 0 Reputation points

2026-10-30T16:00:53.8033333+00:00

It appears to be working again on Canary's build 159.0.4372.0.
Y Z 0 Reputation points

2026-11-01T15:22:34.0933333+00:00

The issue still persists.
I2 Zerro 0 Reputation points

2026-11-02T09:36:57.01+00:00

Additional reproduction of the restart-dependent personal-MSA sync failure, tested on November 1, 2026.

Environment: Windows 11 Pro 25H2 (build 26200.9711), Edge Stable 156.0.4314.58, and isolated Beta 157.0.4341.30 profiles. These are historical test versions, not a fresh inventory.

Interactive sign-in temporarily restores sync and data types show Running. Closing and reopening Edge without signing out returns sync to Initializing/Not Running.

Failing-state observations:

Signed In, Consented for Sync; refresh token present; no persistent auth error.

MainSyncToken OK / Has Token=true. In later failing captures, KeyDataToken was also OK / Has Token=true.

Server Connection: not attempted.

MSA Download Key Result: Fail; Set Key Result: Fail; HTTP Response Code and Net Error Code: n/a.

DataType Manager: Stopped; Cryptographer Ready To Encrypt: true; no pending keys or passphrase requirement shown.

No Edge policies were configured at the initial capture. Re-sync, cloud sync reset, browsing-data cleanup, and isolated Stable/Beta profiles did not provide a lasting fix. In an isolated key-reinitialization test, two account keys were retrieved/installed, but the engine still did not start.

Consumer support documented the unresolved issue but could not escalate internally. No second MSA was available for my comparison tests. The original diagnostic archive was subsequently deleted; fresh traces can be collected through an appropriate secure channel.

Does the Edge Sync team recognize this startup/key-initialization pattern? What focused before/after-restart diagnostics would help distinguish a client regression from account provisioning or a backend issue?

Prepared with AI assistance from my recorded troubleshooting observations; no account-specific identifiers or raw logs are included.
Richard Bottiglieri 10 Reputation points

2026-11-02T14:48:51.0833333+00:00

This is currently fixed in the Dev channel (Edge major version 158). Still broken in Stable and Beta channels. It's highly unlikely that we'll get a fix before Edge 158 hits the Stable channel, which is honestly pathetic.
Eduardo 0 Reputation points

2026-11-02T20:28:28.48+00:00

More than 15 days have passed, and Microsoft still hasn’t fixed the synchronization issue. Edge is a very good browser, but this is unacceptable. In the end, I’ll have to go back to using Chrome, which I don’t particularly like, but it never let me down when it came to synchronization, including syncing across devices, which always happened instantly.
Raf 0 Reputation points

2026-11-03T02:30:41.2966667+00:00

Same problem. Microsoft - hotfix please.