microsoft edge
224 TopicsEdge sync fails after restart — MSA key error
Edge sync works after signing in, but gets stuck on “Initializing” after reopening — persists after Windows repair and testing with a new Windows user Hi everyone, Microsoft Support suggested that I post here for further help. My personal Microsoft account syncs successfully when I first sign in to Edge. However, after closing and reopening the browser, sync gets stuck on “Initializing” / “Setting up sync.” Signing in again can temporarily restore it, but the problem returns after restarting Edge. The issue also reproduces under a newly created Windows local user account. Environment Microsoft Edge: 156.0.4314.58 Windows 11 Home China, version 26H2, build 26300.9711, 64-bit Account type: Personal Microsoft account (MSA), not a work or school account The same Microsoft account has been syncing successfully on my phone Steps to reproduce Sign in to Edge with my Microsoft account and enable sync. Sync works successfully. Close and reopen Edge. Sync remains stuck on “Initializing,” and all data types show “Not Running.” Current edge://sync-internals results Transport State: Initializing User Actionable Error: None Disable Reasons: None Sync Feature Enabled: true Setup In Progress: false Sync Consent: true Auth Error: OK since browser startup MainSyncToken: Last Token Request Result: OK Has Token: true Last Token Error: None KeyDataToken: Last Token Request Result: OK Has Token: true Last Token Error: None MSA Account Key Status: Download Key Result: Fail Set Key Result: Fail Net Error Code: n/a HTTP Response Code: n/a Process Key Result: n/a Encryption: Cryptographer Ready To Encrypt: false Cryptographer Has Pending Keys: true Has Keystore Key: false Passphrase Required: false Passphrase Type: kKeystorePassphrase Server Connection: not attempted Sync Engine: Backend Status: Initialized BlockReason: None Syncer: Unset DataType Manager: Stopped All data types: Not Running Updates Downloaded / Successful Commits: 0 No enabled sync-blocking policies are shown. Troubleshooting already completed Tested with a separate Edge user-data directory: initial sign-in synced successfully, but reopening reproduced the issue. Tested with extensions disabled: no improvement. Tested the separate Edge instance with --no-proxy-server: no improvement. This does not rule out system-level network filtering. Tested --enable-features=msForceOneAuthWAM: no improvement, although I did not independently verify whether the authentication library actually switched. Tried stopping sync while keeping data, then enabling it again: no improvement. Completed DISM repair successfully. Subsequent SFC and component-store checks reported no remaining corruption. Completed a Windows ISO in-place repair, keeping personal files and applications: the sync problem persisted. Created a new standard Windows local user and tested Edge there: first sync succeeded, but reopening Edge reproduced the same failure. Authentication tokens appear to be obtained successfully, while the sync encryption-key stage remains unsuccessful. I understand that the n/a HTTP and network fields do not establish whether a request was sent or rejected. Questions Is this a known issue affecting personal-account sync in this Edge version? What diagnostic logs would help distinguish a startup/key-loading problem from an account-side sync issue? Is there a supported workaround or fix that preserves existing browser data and cloud sync data? I can provide additional sanitized diagnostics. I would prefer to avoid further profile deletion or cloud-sync resets unless the logs indicate that they are necessary. Thank you for your help.274Views2likes3CommentsFeature Request: Native Multi-Container Tabs (Session Isolation) for Edge Workspaces and Tab Groups
Microsoft Edge developer team, As a developer who regularly tests complex web applications locally and on staging environments, I rely heavily on Microsoft Edge's Tab Groups and Workspaces to keep my projects organized. However, testing multi-role workflows—such as simultaneously testing Admin, Manager, and Standard User accounts on localhost—is currently very frustrating. When logging into a secondary account in another tab within the same Edge window, the newly created authentication token overwrites the existing cookies, localStorage, and session context across all open tabs for that domain. This causes the first tab to automatically switch sessions upon refresh or navigation, breaking side-by-side workflow testing. Mozilla Firefox solves this problem cleanly with Multi-Account and Temporary Containers, allowing tabs inside the same window to maintain fully isolated storage contexts. Bringing native container tabs or tab-level session isolation to Microsoft Edge, especially tightly integrated with Tab Groups, would eliminate the need to run multiple heavy browser profiles or separate windows. It would make Edge the absolute premier browser for developers, QA engineers, and power users who manage multiple user roles daily. Please consider adding tab-level container isolation to the Edge product roadmap.429Views2likes2CommentsMicrosoft Edge Workspaces deleted/hidden after update.
All my workspaces in Edge are hidden and/or are deleted. I updated my windows yesterday night (the restart also updated Edge which was pending) and noticed this issue this morning. I had 10+ workspaces and none of them are here to be found. Tried restarting the browser but no luck there.493Views0likes3CommentsMicrosoft Edge Enterprise — Intermittent Blue Coat Proxy Authentication Prompt
Product: Microsoft Edge for Business / Microsoft Edge Enterprise Component: Proxy authentication, HTTP networking and integrated authentication Operating system: Windows 11 Enterprise Proxy: Blue Coat / Broadcom forward proxy, port 8080 Proxy authentication configuration: Basic Auth/ IWARealm exact authentication method to be confirmed Affected browser: Microsoft Edge for Business Comparison browser: Mozilla Firefox, where the same behaviour has not been observed Impact: Intermittent interruption of browsing and loss of access to existing tabs until the user reauthenticates We are experiencing intermittent, unexpected proxy authentication prompts in Microsoft Edge for Business. The dialog states: Sign in to access this site. The proxy http://[bluecoat-host-url]:8080 requires a username and password. Your connection to this site is not secure. The prompt appears sporadically, sometimes while the browser is idle or while tabs displaying otherwise idle ServiceNow, deepl etc. pages cannot be accessed until user reauthenticates with autofill if proxy password is saved in order to be able to access those sites again. No explicit navigation or user interaction is necessarily taking place when the dialog appears. This behaviour was not observed previously and has become noticeable more recently especially since the migration of a lot of our workloads to the microsoft cloud. Firefox does not appear to exhibit the same symptom under comparable. We suspect that a background request, a new or reused proxy connection, proxy-session reauthentication, or an incomplete integrated-authentication exchange may be triggering the prompt. However, we have not yet identified the exact request or established whether the root cause is Edge, the proxy configuration, PAC routing, or the authentication infrastructure. usage conditions. Edge should silently authenticate to the configured enterprise proxy through the organisation's approved authentication mechanism, without unexpectedly displaying a credential prompt during normal browsing or background activity.442Views0likes2CommentsSecurity Review for Microsoft Edge version 152
We have reviewed the new settings in Microsoft Edge version 152 and determined that there are no additional security settings that require enforcement. The Microsoft Edge version 151 security baseline continues to be our recommended configuration which can be downloaded from the Microsoft Security Compliance Toolkit. Microsoft Edge version 152 introduced 4 new Computer and User settings; we have included a spreadsheet listing the new settings to make it easier for you to find. Starting with version 152 Microsoft Edge is moving to a more frequent release cycle. To better align with the needs of the enterprise customers, the Microsoft Edge security baseline is expected to align with the Extended Stable Channel, which provides major feature updates on an eight-week cadence while continuing to receive security and quality updates between releases. This approach provides organizations with additional time to evaluate and deploy feature changes while ensuring security protections remain current. Why the change? Security baselines are intended to provide guidance for managing security relevant configuration settings, not to track every feature introduced in a browser release. With the move to a two-week release cadence, publishing baseline updates for every release would increase operational overhead while providing limited security benefit. The Extended Stable cadence offers a more practical balance for enterprise customers by allowing additional time for testing and evaluation, while continuing to receive security and critical fixes between major feature releases. By aligning with Extended Stable, we can update the baselines less frequently and focus on publishing them earlier in the release cycle, giving IT administrators more time to review and plan for upcoming changes. Our goal is to make security baseline adoption more predictable and easier to manage while continuing to provide timely security guidance. As a friendly reminder, all available settings for Microsoft Edge are documented here, and all available settings for Microsoft Edge Update are documented here. Please continue to give us feedback through the Security Baselines Discussion site or this post.2.1KViews0likes6CommentsMicrosoft Edge default browser with Intune
Hello everyone, I am looking for the best way to configure Microsoft Edge as the default browser for Windows devices managed through Microsoft Intune. I have reviewed the available Microsoft Edge settings in the Settings Catalog but have not been able to identify a specific setting that configures Edge as the default browser. Is there a supported and recommended way to enforce Microsoft Edge as the default browser for managed Windows 10/11 devices? If there are multiple approaches available, I would appreciate recommendations on the preferred method for enterprise environments. Thank you.659Views0likes2Comments