Microsoft Edge known issues

This article tracks the known issues, workarounds, and fixes for Microsoft Edge.

High impact issues

These issues are high impact as identified by Customer Service & Support. Check this article often as the Microsoft Edge team provides workarounds and fixes.

The following table lists the issues that the Microsoft Edge team is tracking closely, working on, or resolved.

Recent issues

Version	Symptom	Workaround	Comment
155	After upgrading to Microsoft Edge Stable version 155, some users may be unable to launch Microsoft Edge. This issue can occur after an update or restart and affects existing browser profiles.	For affected devices, administrators can disable the scheduled update restart task in the Microsoft Edge management service and delete the contents of the Microsoft Edge User Data\Policy folder, except for the Primary Account file.	Microsoft has mitigated the issue by rolling back the related service-side change to prevent additional customers from encountering it. A client-side fix is under investigation.
154	In Microsoft Edge version 154, search engines configured through Recommended Default Search Provider policies may become invalid after Microsoft Edge has been running for a short period of time. When this occurs, address bar searches stop working.	Change the affected Default Search Provider policies from Recommended to Mandatory, or Use the ManagedSearchEngines policy as an alternative administrative configuration. It also allows search engines to be deployed as recommended and should not be impacted by this regression. Previous Default Search Provider policies need to be removed beforehand, since their existence makes ManagedSearchEngines non-functional.	This issue is fixed in Microsoft Edge stable release 155.0.4283.45.
154	In Microsoft Edge version 154, some users may experience printing failures when attempting to print from Microsoft Edge, including through both the standard print experience (Ctrl+P) and the Windows system print dialog (Ctrl+Shift+P). Symptoms include print dialogs failing to appear, closing unexpectedly, or printing operations failing with error messages, exclusively when using the "Microsoft Print to PDF" printer.	Customers using the Microsoft Edge standard print experience (Ctrl+P) can choose the "Save As PDF" printer instead of choosing the "Microsoft Print to PDF" printer. This workaround is not applicable to the Windows system print dialog (Ctrl+Shift+P). Customers experiencing this issue can also temporarily roll back to Microsoft Edge version 153.	This issue is fixed in Microsoft Edge stable release 154.0.4258.48.
153	In Microsoft Edge version 153, some web applications may become unresponsive during user interaction. When the issue occurs, the affected browser window may freeze and stop responding to mouse or keyboard input.	Customers experiencing this issue can temporarily roll back to Microsoft Edge version 152.	This issue is fixed in Microsoft Edge stable release 153.0.4234.48.
N/A	Some customers may experience a crash during an update when running MicrosoftEdgeUpdate.exe with msedgeupdate.dll version 1.3.261.11.	N/A	EdgeUpdate with msedgeupdate.dll 1.3.263.3 contains a fix for this crash. This crash does not involve Microsoft Edge (browser) or the Microsoft WebView2 Runtime.
150	In Microsoft Edge Stable version 150, when Microsoft Edge is run with different user credentials or when used as a published application where the Windows Shell is unavailable, auto-launching a target application for a given file type stops working. The download completes successfully, but the associated application does not open.	Open the downloaded file manually by navigating to its download location in File Explorer, or roll back to Microsoft Edge Stable version 149.	This issue is fixed in Microsoft Edge stable release 150.0.4078.96.
136	On Microsoft Edge versions earlier than 136, translation will stop working after July 30, 2026.	N/A	Users can update their browser by going to Settings and more (...) > Help and feedback > About Microsoft Edge; install the update and restart when prompted. Admins should update managed devices to the latest version of Microsoft Edge.
150	In Microsoft Edge Stable version 150, third-party extensions are temporarily disabled on m365.cloud.microsoft.	N/A	This issue is fixed in Microsoft Edge stable release 151.0.4129.59.
149	Starting in Microsoft Edge Stable version 149.0.4022.52, the Downloads dialog may continue to display the "Keep/Delete" prompt for .rdp files after the download has completed. The file downloads successfully, but the Downloads dialog doesn't update to reflect completion.	Admins can configure the AutoOpenFileTypes policy to have "rdp" files open automatically. Admins can configure the ExemptFileTypeDownloadWarnings policy with value [{"file_extension":"rdp","domains":["*"]}]. Admins can roll back to Microsoft Edge Stable version 148.0.3967.96. Users can click outside the Downloads dialog (which closes it), then reopen Downloads (Ctrl+J or the Downloads button) and select Open, Save, or Save As.	This issue is fixed in Microsoft Edge stable release 149.0.4022.69.
148	Some users may not see the Work Feed, Discover Feed, or the feed toggle on the Copilot New Tab Page. This issue primarily impacts users whose tenant or user locale is outside supported language markets. Feed experiences are currently dependent on supported language/market coverage. Users outside these markets may not receive feed modules or toggle entry points.	N/A	This issue is fixed in Microsoft Edge stable release 149.0.4022.52.
147	In Microsoft Edge Stable version 147, printing PDFs protected with Azure Information Protection (AIP) or Microsoft Purview Information Protection (MIP) might cause a crash to the PDF renderer.	This issue only occurs with the new PDF reader. Enterprise administrators can temporarily avoid the issue by disabling the NewPDFReaderEnabled, or roll back to Microsoft Edge Stable version 146.	This issue is fixed in Microsoft Edge stable release 147.0.3912.98.
146	Microsoft Edge versions below 146.0.3856.117 will NOT work with Microsoft 365 Copilot chat in the sidebar. The Microsoft Edge internal container page that hosts compliant Microsoft 365 Copilot chat in the sidebar has been updated.  Moreover, blocking internal edge:// or chrome-untrusted:// URLs isn't recommended as this might lead to unexpected errors and will disable the Microsoft 365 Sidebar Copilot Chat experience. For more information, see Allowlist for Microsoft Edge endpoints.	N/A	The hosting infrastructure change was introduced on April 10, 2026 with the update of Microsoft Edge Stable version 146.0.3856.117. As a result of this change, the minimum supported version of Microsoft Edge is 146.0.3856.117 or later for Microsoft 365 Copilot chat in the sidebar to function.  Users with any version older than 146.0.3856.117, results in a non-working M365 Copilot chat in the sidebar experience
145	Some users might be unable to drag and drop files from the Downloads menu. This issue occurs in new Downloads menu, which is enabled as part of a controlled feature rollout for selected users.	N/A	This issue has been resolved and no longer affects users.

Archived issues

Version	Symptom	Workaround	Comment
144	After updating to Microsoft Edge version 144, automatic on-premises (DOMAIN\user) sign-in might fail for new Microsoft Edge profiles when internet connectivity is missing or restricted, causing sign-in dialogs instead of automatic sign-in and can create sync issues within the environment.	Admins can apply the OnlyOnPremisesImplicitSigninEnabled policy to prioritize on-premises implicit sign-in.
144	In Microsoft Edge Stable version 144.0.3719.82, macOS devices might experience a fully saturated CPU core under certain conditions.	N/A	This issue is fixed in Microsoft Edge stable release 144.0.3719.115.
144	In Microsoft Edge Stable version 144.0.3719.82, users who haven't fully completed their Microsoft Entra ID sign-in for their Microsoft Edge profile may be unable to access Conditional Access (CA) protected web resources, as Single Sign-on (SSO) won't function properly in this degraded sign-in state.	Use an unsigned‑in Microsoft Edge profile and ensure the following setting is enabled. Allow single sign-on for work or school sites using this profile (toggle ON) under edge://settings/profiles/multiProfileSettings. Click "Complete sign-in" in the Profile flyout and finish signing in to an Edge profile.	This issue is fixed in Microsoft Edge stable release 144.0.3719.104.
144	When a top-level page is loaded using a custom scheme (for example, myapp://example/index.html) and its resources are served through WebResourceRequested, the main page renders correctly. However, any iframe within that page that also navigates to a custom-scheme URL resolves to about: blank, and any embedded links using the custom scheme fail to load as well. This specific problem has affected all versions of SAP GUI based on WebView2 control.	N/A	This issue is fixed in Microsoft Edge stable release 144.0.3719.92.
143	Starting in Microsoft Edge Stable version 143.0.3650.66, Local Network Access is enabled by default. This may affect web applications that embed a cross-origin iframe that may eventually perform network requests to locations that are considered local, together with all domains the iframe host may navigate to. This requires web application changes from the owner of the web application. Also, any publicly accessible host that may be resolved to an IP address range considered local. This is impactful for hosts that are resolved to Carrier-Grade NAT address ranges (100.64.0.0/10), typically seen with certain VPN and proxy solutions (Zscaler, for example). Using the Microsoft Edge Browser Policy Documentation LocalNetworkAccessAllowedForUrls Microsoft Learn may help resolve these issues, but if the website contains a cross-domain iframe (like the Intune portal), then this policy might not be enough to mitigate impact.
143	LocalNetworkAccess support for OneDrive and SharePoint. The OneDrive Sync client has been updated to support the new changes in Microsoft Edge version 143 that requires Edge to prompt user or admins for OneDrive and SharePoint URLs to have fast performance and offline access.		As a result of this change, other SharePoint and/or OneDrive-related entries appear under the "Allowed to connect to any device on your local network" section of the Edge Local Network Access permission page (edge://settings/privacy/sitePermissions/allPermissions/localNetworkAccess). Deleting the registry keys added by OneDrive for the LocalNetworkAccessAllowedForUrls policy don't cause them to be recreated. The addition of these registry keys by OneDrive was a one-time action. This change only involved adding new keys, OneDrive didn't overwrite any existing Local Network Access policies already configured. Per machine SKU: The OneDrive Sync client applies the required permissions automatically and policies for existing users in Edge - no user action is needed. Per user SKU: The OneDrive Sync client prompts users via a notification to enable these permissions, and users should follow the notification instructions to complete setup.
142	In Microsoft Edge Stable version 142.0.3595.65, some third-party applications fail to start msedge.exe while using cmd /K cd /d %ProgramFiles(x86)%\Microsoft\Edge\Application && start msedge <url> from a command prompt window.	Roll back to Microsoft Edge Stable version 142.0.3595.53.	This issue is fixed in Microsoft Edge stable release 142.0.3595.76.
142	Enterprise customers encounter reload in IE mode entry points removed from the UI in user's devices.	As announced Securing the Future: Changes to Internet Explorer Mode in Microsoft Edge | Microsoft Browser Vulnerability Research UI entry points to reload a site manually in IE mode have been removed from consumer devices by default. This change has completed with the release of Edge 142 Stable. This change doesn't impact enterprise customers when their devices are configured properly under group policy InternetExplorerIntegrationLevel.
142	Starting in Microsoft Edge Beta version 142.0.3595.11, customers may experience a browser crash if the SearchSuggestEnabled policy is configured.	Roll back to Microsoft Edge Beta version 141.0.3537.57 or temporarily remove the SearchSuggestEnabled policy.	This issue is fixed in Microsoft Edge Beta release 142.0.3595.19.
142	Some customers unexpectedly start seeing the sidepane open with context for their Teams and Outlook links. In Microsoft Edge 142, the auto-open feature is temporarily rolled back and users may find if the sidebar was turned off (not visible), Microsoft Edge may auto-open Teams or Outlook context in the sidepane.	Users can manually toggle off the auto-open context experience in Microsoft Edge settings (Copilot and sidebar/App and notification settings/Teams + Outlook). Admins can turn off the Auto-Open experience by using either of these policies: HubsSidebarEnabled: Set as "False" ExtensionSettings: sidebar_auto_open_blocked flag set as "True"
N/A	In the Microsoft Edge management service (Microsoft Edge page in the Microsoft 365 Admin Center), customers may see an error message about cloud policy configurations failing to load.	Multiple refreshes may temporarily resolve this.	This issue is fixed for the Microsoft Edge management service.
140	Starting in Microsoft Edge Stable version 140.0.3485.54, customers may find after launching Microsoft Edge 1-3 times it triggers an unexpected browser exit.	Clearing %AppData%\Local\Microsoft\Edge\User Data\Default\Sync Data\ may temporarily resolve the issue or deleting and recreating the user profile may also temporarily correct the issue.	This issue is fixed in Microsoft Edge stable release 140.0.3485.66.
N/A	When Microsoft Edge is installed, it includes the Microsoft.MicrosoftEdge.Stable host package. This package is a browser host package and enables platform functionality that would otherwise be unavailable to the browser as a Win32 application (System Notifications, Taskbar/Start pinning with UWP-like features, etc.). It isn't recommended to remove it. Customers may observe that the host package is an older version than the current browser version.		This is expected behavior and doesn't indicate any security vulnerability. Additionally, it doesn't imply Microsoft Edge nor any other component is out of date. The host package is updated independently when detected when the package is either in a bad state or a new feature is added to the host package.
137	In Microsoft Edge Stable version 137.0.3296.52, customers encounter unexpected leading spaces in the browser window title, which can break automation workflow for non-English language environments.		This issue is fixed in Microsoft Edge stable release 137.0.3296.58.
136	In Microsoft Edge Stable version 136.0.3240.50, some text isn't displayed, and rendering is broken when viewing certain PDF files containing Japanese fonts. Note: This issue occurs when the system has fonts with Japanese file names installed.	This issue only occurs with the new Adobe Acrobat powered built-in PDF reader. Enterprise administrators can temporarily avoid the issue by disabling the NewPDFReaderEnabled policy. Each user can also temporarily avoid the issue by disabling the New PDF Viewer in edge://flags/#edge-new-pdf-viewer.	This issue is fixed in Microsoft Edge stable release 136.0.3240.92.
136	On the Microsoft Edge New Tab Page (NTP), customers may see differing feeds.  Even when NTP policies are configured, users may have the Discover or My Feed selected.		The NTP issue and Microsoft 365 admin center configuration issue is fixed.
136	For users with the 'Auto hidden' sidebar visibility setting, their Outlook or Teams link may not be showing the sidepane content as expected.		This issue is fixed in Microsoft Edge stable release 137.0.3296.52.
136	Microsoft Editor (spell checker) doesn’t offer suggestions for misspelled words	The issue was identified in Microsoft Editor. Users that need spell checking assistance, can rely on the Basic functionality. Enabled under edge://settings/languages or via Group Policy using the MicrosoftEditorProofingEnabled policy.	This issue is fixed in Microsoft Edge stable release 136.0.3240.64.
135	Customers may see an issue where the first-run experience (FRE) page edge://welcome-new-device opens and fails with an error message page that doesn't close. This occurs when FRE is disabled and might be triggered suddenly after upgrade.	Roll back Microsoft Edge to version 134.0.3124.95 or modify the HideFirstRunExperience policy to “0”.	This issue is fixed in Microsoft Edge stable release 135.0.3179.85.
134	Starting in version 134, customers may encounter an issue that affects extensions that bring up a window. The extension may get paused in the background if the window is minimized or occluded if the extension is meant to keep running always.	Enterprise administrators can avoid the issue by disabling the Sleeping Tabs feature using the SleepingTabsEnabled policy, or by adding the extension path in the SleepingTabsBlockedForUrls.	This issue is fixed in Microsoft Edge stable release 136.0.3240.92. Also, see Microsoft Edge v134 Sleeping Tabs feature affects the UiPath extensions 22.10, 23.4 and 23.10
134	Enterprise users with Multifactor Authentication (MFA) and Conditional Access (CA) may see popups when they start the Microsoft Edge browser.		Recognizing the broad impact this issue is having, Microsoft is working to temporarily mitigate this issue through the Experimentation and Configuration Service (ECS). To receive the mitigation, admins should either not configure the ExperimentationAndConfigurationServiceControl policy or set the policy to "FullMode" or "ConfigurationsOnlyMode".
134	Enterprise users with MFA and CA may not have Single Sign-on (SSO) with Microsoft 365 Copilot Chat. The user may see a "sign in" button.		The user may see a "sign in" button when they try to use Copilot.
134	Customers may not be able to start the Microsoft Edge browser programmatically using --inprivate and --app (application mode) via the command line because the browser crashes.	Customers can start the browser using "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" https://www.contoso.com --inprivate. Alternatively, they can roll back to Microsoft Edge version 133.0.3065.92.	This issue is fixed in Microsoft Edge stable release 134.0.3124.83.
133	Customers may not be able to start the sync functionality or open AIP-protected PDF files in Microsoft Edge. A bug in version 133 caused excessive traffic to the MIP service.	For sync: "sign out (keeping locally saved data)" then "sign in" again. For AIP-protected PDFs, use Azure Information Protection Viewer.	This issue is fixed in Microsoft Edge stable release 133.0.3065.69. Note: For some users, it may still be necessary to sign out and sign in again.
131	With Microsoft Edge Stable version 131.0.2903.48, some text isn't displayed, and rendering is broken when viewing certain PDF files containing Japanese fonts.	This issue doesn't occur with the new Adobe Acrobat powered built-in PDF reader. Enterprise administrators can avoid the issue by enabling the NewPDFReaderEnabled policy. Each user can also avoid the issue by enabling the New PDF Viewer in edge://flags/#edge-new-pdf-viewer. Note: When you set NewPDFReaderEnabled to 1, the PDF is displayed correctly in Microsoft Edge. However, the same issue occurs in the print preview. Some text doesn't display correctly in the print preview, but the actual printout is correct.	This issue on Windows is fixed in Microsoft Edge stable release 131.0.2903.70. This issue on macOS is fixed in Microsoft Edge stable release 132.0.2957.115.
130	With Microsoft Edge Stable version 130.0.2849.46, some browser extensions are no longer working if they're using the chrome.storage.managed API.	Roll back Microsoft Edge to version 129.0.2792.89.	This issue is fixed in Microsoft Edge stable release 130.0.2849.56.
130	In version 130.0.2849.46, nonspecial scheme URL handling was updated to align with the URL Standard, which may affect site compatibility.	Don't configure or set ExperimentationAndConfigurationServiceControl to "FullMode" or "ConfigurationsOnlyMode". Alternatively, roll back to version 129.0.2792.89.	Microsoft temporarily disabled this feature via ECS. A browser restart is needed. A code change in version 130.0.2849.80 also disables it if ECS blocked by policy. Note: Re-enabled in version 133.0.3065.10+.
128	With Microsoft Edge Stable version 128.0.2739.42, pages may fail to fully load when retrieving resources from the HTTP cache. When the issue is encountered, DevTools shows the requests failing with net::ERR_FAILED.	Roll back Microsoft Edge to version 127.0.2651.105 for Microsoft Edge Stable or version 126.0.2592.137 for Microsoft Edge Extended Stable. A force reload (Ctrl+Reload button) can mitigate individual page loads. Site owners may also consider reducing the use of HTTP caching for impacted resources until the issue is addressed.	Microsoft is collaborating with the Chromium project via Chromium bug 362788339 to address the issue. This issue is fixed in Microsoft Edge stable release 128.0.2739.63.
128	With Microsoft Edge Stable version 128.0.2739.42, customs configured start pages appear to be stuck in the loading state.	Roll back Microsoft Edge to version 127.0.2651.105 for Microsoft Edge Stable or version 126.0.2592.137 for Microsoft Edge Extended Stable. Use the command line argument: "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --disable-features="msIrm, msIrmv2, msEndpointDLp" Note: Command line args are case sensitive.	The fix is included in Stable version 128.0.2739.54.
124	Specific HTTPS websites may show ERR_CONNECTION_ABORTED or ERR_SSL_PROTOCOL_ERROR. Linked to the "TLS 1.3 hybridized Kyber support" feature.	Disable Kyber via edge://flags/#enable-tls13-kyber. Enterprises can use the PostQuantumKeyAgreementEnabled policy. Registry: [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge] (DWORD) "PostQuantumKeyAgreementEnabled"=0	This workaround is temporary and will be removed in future versions. Disabling weakens TLS security.
121	Specific HTTPS websites may show ERR_SSL_KEY_USAGE_INCOMPATIBLE, caused by enforcing X.509 key usage extensions.	Set the RSAKeyUsageForLocalAnchorsEnabled policy. Registry: [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge] (DWORD) "RSAKeyUsageForLocalAnchorsEnabled"=0	This policy isn't effective in Microsoft Edge version 124 and later.
120	Microsoft Edge opens HTTP URLs as HTTPS when the server supports HTTPS due to the "HttpsDefault" feature.	Use the HttpsUpgradesEnabled policy to disable automatic HTTPS. Previously, the AutomaticHttpsDefault policy was used, but it's deprecated in Microsoft Edge version 136. Registry: [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge] (DWORD) "HttpsUpgradesEnabled"=0. To disable per-site, use InsecureContentAllowedForUrls.
119	Specific HTTPS websites may show ERR_SSL_PROTOCOL_ERROR due to removal of SHA-1 in TLS handshakes.	Set InsecureHashesInTLSHandshakesEnabled policy. Registry: [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge] (DWORD) "InsecureHashesInTLSHandshakesEnabled"=1	This policy was removed in version 124+. Enabling this increases impersonation risk.

See also

• Microsoft Edge Enterprise landing page