Ανάγνωση στα Αγγλικά Επεξεργασία

Κοινή χρήση μέσω

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.

Version Symptom Workaround Comment
133 Customers may not be able to start the sync functionality or open AIP-protected PDF files in Microsoft Edge. A bug in Microsoft Edge version 133 is causing excessive traffic to the MIP service, which has resulted in the temporary blocking of sync functionality and the inability to open AIP-protected PDF files in Microsoft Edge. For sync functionality to resume, users can "sign out (keeping locally saved data)"and then "sign-in" again.  For AIP-protected PDF files, please use other tools such as the Azure Information Protection Viewer. This issue is fixed in Microsoft Edge stable release 133.0.3065.69. Note: For some users it still might be necessary to "sign out (keeping locally saved data)"and then "sign-in" again for sync functionality to resume.
130 In Microsoft Edge Stable Version 130.0.2849.46, nonspecial scheme URL handling was updated to become compliant with the URL Standard (https://url.spec.whatwg.org/). This change has site compatibility impacts which may require changes to your web sites. For more information and web developer guidance, see http://bit.ly/url-non-special. Ensure your clients receive configuration payloads by either not configuring the ExperimentationAndConfigurationServiceControl policy or setting the policy to "FullMode" or "ConfigurationsOnlyMode". Alternatively, roll back to Microsoft Edge to version 129.0.2792.89. Recognizing the broad impact this issue is having, Microsoft decided to temporarily disable this feature through the Experimentation and Configuration Service (ECS). This feature disablement is now fully rolled out to Microsoft Edge 130 Stable (100%), so it's expected that this will take effect after a browser restart.

In addition, for enterprises where ECS is disabled through policy, a code change to temporarily disable this feature is included in Microsoft Edge stable release 130.0.2849.80 and later.

Note: This feature is turned on again in Microsoft Edge version 133.0.3065.10 and higher. Customers are encouraged to test the impact of this feature and prepare for the change in behavior.
124 Specific HTTPS websites are no longer accessible, with the error:
ERR_CONNECTION_ABORTED or ERR_SSL_PROTOCOL_ERROR.
This error might also occur when fetching resources on the page, causing display or delay issues.

The "TLS 1.3 hybridized Kyber support" feature causes this error.		 To verify if the issue is related the Kyber key encapsulation in TLS, you can disable the feature through its flag in edge://flags/#enable-tls13-kyber.

Enterprise administrators who need more time to update their certificates can set the PostQuantumKeyAgreementEnabled enterprise policy as a temporary workaround. Note:
- This fix is a temporary measure that will be removed in future versions of Microsoft Edge.
- Disabling this policy means that user traffic is unprotected from decryption by quantum computers.
The registry-key for the policy is:
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge]
(DWORD) "PostQuantumKeyAgreementEnabled"=0
121 Specific HTTPS websites are no longer accessible, with the error:
ERR_SSL_KEY_USAGE_INCOMPATIBLE

This issue is caused by enforcing X.509 key usage extensions for RSA keys in TLS 1.2 and earlier versions.		 Enterprise administrators who need more time to update their certificates can set the RSAKeyUsageForLocalAnchorsEnabled enterprise policy as a temporary workaround. This policy was temporarily available for administrators who needed more time to update their certificates to meet the new RSA key usage requirements. Note: This policy is removed in Microsoft Edge version 124 and later.
The registry-key for the policy is:
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge]
(DWORD)"RSAKeyUsageForLocalAnchorsEnabled"=0
120 When Microsoft Edge starts with an external HTTP-URL (for example, http://www.example.com), Microsoft Edge opens the page directly with HTTPS, in case the server also enabled HTTPS. The same thing happens if you follow a hyperlink like this http://www.example.com in a new tab.

This change in behavior is due to the feature "HttpsDefault", which was enabled by default.		 With Microsoft Edge 120.0.2210.89, the policy AutomaticHttpsDefault can be used to disable the automatic switch from HTTP to HTTPS.
If you need to turn off the automatic switch from HTTP to HTTPS, deploy this policy:
"Configure Automatic HTTPS" -> "Automatic HTTPS functionality is disabled." (value 0)
The registry-key for the policy is:
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge]
(DWORD) "AutomaticHttpsDefault"=0

In a scenario where you only want to disable the automatic switch for specific websites, you can use the policy InsecureContentAllowedForUrls to configure these sites.
119 Specific HTTPS websites are no longer accessible, with the error: ERR_SSL_PROTOCOL_ERROR.

This issue is caused by removing support for signature algorithms using SHA-1 for server signatures during the TLS handshake.		 Enterprise administrators who need more time can set the InsecureHashesInTLSHandshakesEnabled enterprise policy as a temporary workaround. Note:
- This policy is temporary. It was removed in Microsoft Edge version 124 and later.
- Because this allows an insecure hash function in a critical part of the TLS handshake, enabling this policy increases the risk of attackers impersonating servers in an enterprise deployment.
The registry-key for the policy is:
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge]
(DWORD) "InsecureHashesInTLSHandshakesEnabled"=1