Merging changes synced from https://github.com/MicrosoftDocs/Edge-Ent…

…erprise-pr (branch live)

edgeenterprise/microsoft-edge-known-issues.md

@@ -3,7 +3,7 @@ title: "Microsoft Edge known issues"
 ms.author: archandr
 author: dan-wesley
 manager: likuba
-ms.date: 11/19/2024
+ms.date: 11/21/2024
 audience: ITPro
 ms.topic: conceptual
 ms.service: microsoft-edge
@@ -30,7 +30,7 @@ The following table lists the issues that the Microsoft Edge team is tracking cl
 
 |  Version  | Symptom | Workaround | Comment |
 | --- | --- | --- | --- |
-| 131 | Starting with Microsoft Edge Stable version 131.0.2903.48, some text is not 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](/deployedge/microsoft-edge-policies#newpdfreaderenabled) policy. Each user can also avoid the issue by enabling the New PDF Viewer in *edge://flags/#edge-new-pdf-viewer*. |   |
+| 131 | Starting with Microsoft Edge Stable version 131.0.2903.48, some text is not 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](/deployedge/microsoft-edge-policies#newpdfreaderenabled) policy. Each user can also avoid the issue by enabling the New PDF Viewer in *edge://flags/#edge-new-pdf-viewer*.<br><br>**Note:**<br>When you set NewPDFReaderEnabled to 1, the PDF is displayed correctly in Edge. However, the same issue occurs in the print preview. Some text does not display correctly in the print preview, but the actual printout is correct.  | The root cause is identified, and we are working on releasing a fix as soon as possible. |
 | 130 | In Microsoft Edge Stable Version 130.0.2849.46, non-special scheme URL handling was updated to become compliant with the URL Standard ([https://url.spec.whatwg.org/](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](http://bit.ly/url-non-special). | Ensure your clients receive configuration payloads by either not configuring the [ExperimentationAndConfigurationServiceControl](/deployedge/microsoft-edge-policies#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)](/deployedge/edge-configuration-and-experiments). This feature disablement is now fully rolled out to Edge 130 Stable (100%), so it is expected that this will take effect after a browser restart.<br><br>In addition, for enterprises [where ECS is disabled through policy](/deployedge/microsoft-edge-policies#experimentationandconfigurationservicecontrol), a code change to temporarily disable this feature is included in Microsoft Edge stable release 130.0.2849.80 and later.<br><br>**Note:** This feature is planned to be turned on again in Microsoft Edge version 133. Admins can use the `msedge.exe --enable-features=StandardCompliantNonSpecialSchemeURLParsing` command line argument to explicitly enable the feature in the [Edge Canary Channel](https://www.microsoft.com/en-us/edge/download/insider?msockid=3d18d32cb9d96ec733a3c7b1b8636f96&form=MA13FJ). Customers are encouraged to test the impact of this upcoming feature and prepare for the change in behavior.|
 | 124    |  Specific HTTPS websites are no longer accessible, with the error:<br>ERR_CONNECTION_ABORTED or ERR_SSL_PROTOCOL_ERROR.<br>This error might also occur when fetching resources on the page, causing display or delay issues.<br><br> 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`.<br><br>Enterprise administrators who need more time to update their certificates can set the **PostQuantumKeyAgreementEnabled** enterprise policy as a temporary workaround. Note:<br>- This fix is a temporary measure that will be removed in future versions of Microsoft Edge.<br>- Disabling this policy means that user traffic is unprotected from decryption by quantum computers.<br>The registry-key for the  policy is:<br>[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge] <br>(DWORD) "PostQuantumKeyAgreementEnabled"=0 |     |
 | 121    |  Specific HTTPS websites are no longer accessible, with the error:<br>ERR_SSL_KEY_USAGE_INCOMPATIBLE<br><br>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.<br>The registry-key for the policy is:<br>[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge]<br>(DWORD)"RSAKeyUsageForLocalAnchorsEnabled"=0 |      |