Quick fix: Edge sync conflict resolution sometimes picks the timestamp-older profile when devices write simultaneously. Force the canonical version: sign out of Edge on all but one device, make the changes on that device, then sign back in on others — they pull the canonical state.

You added a bookmark on your work PC. Switched to your home PC and made some unrelated tabs/extensions changes. Came back to work PC the next day — your bookmark is gone. Edge sync resolved the conflict in favor of the home PC’s state, even though it was older. Sync’s conflict resolution doesn’t always pick the latest.

Symptom: Edge sync reverts changes to an older profile state when multiple devices write at once.
Affects: Microsoft Edge with sync enabled across multiple devices.
Fix time: 10 minutes.

How Edge sync resolves conflicts

When two devices push different changes to the same sync category, Edge’s server uses a last-write-wins policy per-record, not per-category. A bookmark added on device A and an extension removed on device B may both win — or in pathological cases, an earlier device’s state overwrites the later device. The arbitration runs server-side and isn’t exposed.

Method 1: Sign out on all but the canonical device

Identify the device with the correct state.
On every other device, sign out of Edge (profile icon → Sign out).
On the canonical device, ensure your desired state is saved.
Wait 5 minutes for the server to settle.
Sign back in on the other devices one at a time. They pull the canonical state.

Method 2: Reset sync from the canonical device

On the canonical device, open edge://sync-internals/.
Click Reset at the bottom. Confirm.
Edge clears local sync state and re-pulls from server.
If your local state doesn’t match what you want, the server overrides — reapply changes locally and let them sync up.

Method 3: Export and re-import critical data

For bookmarks specifically, you can export to HTML: edge://favorites → three-dot menu → Export favorites.
Make changes carefully on one device.
If sync conflicts again, re-import the HTML from the canonical export.

Verification

Bookmarks, extensions, settings all match the canonical state.
Making a change on one device propagates to others without overriding unrelated changes.

If none of these work

If sync conflicts keep happening with two devices, consider disabling sync for the categories that conflict most often (Open tabs, Settings). Keep sync for stable categories (Passwords, Bookmarks for read-only access).

Bottom line: Sync conflicts can resolve in the wrong direction. The clean fix is to designate one canonical device and push changes from there. For chronic conflicts, sign out on extras and only re-sign-in after canonical is settled.