Keep Edge Up to Date

Drew - 810 Reputation points
2020-07-15T07:08:57+00:00

Please, see the last entry in this thread for what the latest Version of Edge is or should be, to keep yours up-to-date.  Thank-you ��

Cheers,

Drew

Microsoft Edge | Other | Windows 10

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

363 answers

Sort by: Newest
  1. Drew - 810 Reputation points
    2024-10-04T04:59:34+00:00

    Version 129.0.2792.79: October 3, 2024

    Fixed various bugs and performance issues.

    Stable channel security updates are listed here.

    Cheers,
    Drew![](https://learn-attachment.microsoft.com/api/attachments/fcd432c4-0607-4b12-997d-2b44c4d27ae2?platform=QnA

    Was this answer helpful?

    0 comments No comments
  2. Drew - 810 Reputation points
    2024-09-27T06:14:19+00:00

    Image

    Image

    Version 129.0.2792.65: September 26, 2024

    Fixed various bugs and performance issues, and feature updates.

    Stable channel security updates are listed here.

    Feature updates

    • Microsoft Edge sidebar updates. For inactive sidebar users and new Edge users, the sidebar is turned OFF. Users can always return to Settings > Sidebar and turn the sidebar ON again at any time. For active sidebar users, the current sidebar state stays the same.

    Administrators can control the availability of the sidebar using the HubsSidebarEnabled policy.

    Note:

    For the Stable Channel, updates will roll out progressively over one or more days. To learn more, see Progressive rollouts for Microsoft Edge updates.

    Microsoft Edge Web Platform constantly evolves to improve user experience, security, and privacy. To learn more, see Site compatibility-impacting changes coming to Microsoft Edge.

    Cheers,
    Drew![Image](https://learn-attachment.microsoft.com/api/attachments/f1156e3d-261e-4600-88ab-7a93a74cc0b5?platform=QnA

    Was this answer helpful?

    0 comments No comments
  3. Drew - 810 Reputation points
    2024-09-20T16:31:32+00:00

                                                            Take a look at What's New [**HERE**](https://www.microsoft.com/en-us/edge/update/129?form=MT00QN&channel=stable&version=129.0.2792.52 "www.microsoft.com").  
    

    Version 129.0.2792.52: September 19, 2024

    Fixed various bugs and performance issues, feature updates, site impacting compatibility changes, and policy updates.

    Stable channel security updates are listed here.

    Note

    Portions of this release note are modifications based on work created and shared by Chromium.org and used according to terms described in the Creative Commons Attribution 4.0 International License. Dev Channel updates The following Dev channel updates preceded this Stable channel release. The following Dev notes provide detailed information about the changes in each release.

    Fixes

    Feature updates

    • Update to Microsoft Edge supported operating systems. The minimum supported macOS version is increased to macOS 11. Users on older versions of macOS will no longer receive Microsoft Edge updates. For more information, see Microsoft Edge Supported Operating Systems.
    • Deprecation of the CryptoWallet feature. To improve end user experience, the CryptoWallet feature and the CryptoWalletEnabled policy is deprecated. The CryptoWalletEnabled policy will be obsolete in an upcoming release.

    Site compatibilty impacting changes

    • Deprecation of non-standard declarative shadow DOM serialization. The prototype implementation, which shipped in 2020 and then updated in 2023, contained a method called getInnerHTML() that could be used to serialize DOM trees containing shadow roots. That part of the prototype was not standardized with the rest of the declarative shadow DOM, and has only recently reached spec consensus (for details, see Github. As part of that consensus, the shape of the getInnerHTML API changed.
    • Deprecate the includeShadowRoots argument on DOMParser. The includeShadowRoots argument was a never-standardized argument to the DOMParser.parseFromString() function, which was there to allow imperative parsing of HTML content that contains declarative shadow DOM. This was shipped as part of the initial shipment of declarative shadow DOM. Since the standards discussion rematerialized in 2023, the shape of DSD APIs changed, including this feature for imperative parsing. Now that a standardized version of this API, in the form of setHTMLUnsafe() and parseHTMLUnsafe() shipped, the non-standard includeShadowRoots argument needs to be deprecated and removed. All usage should shift accordingly: Instead of: (new DOMParser()).parseFromString(html,'text/html',{includeShadowRoots: true}); This can be used instead: document.parseHTMLUnsafe(html);
    • Rename inset-area to position-area. The CSS working group (CSSWG) resolved to rename this property from inset-area to position-area. For more details, see the CSSWG discussion in Github. The old and new property names will be supported for a few milestones, to help developers migrate to the new position-area name. We are shipping the new property name, position-area, as a synonym for inset-area. The inset-area property is currently planned for removal in Microsoft Edge version 131.

    Policy updates New policies

    Deprecated policies

    EnhanceSecurityModeOptOutUXEnabled - Manage opt-out user experience for Enhanced Security Mode (ESM) in Microsoft Edge (deprecated)

    Cheers,
    Drew![](https://learn-attachment.microsoft.com/api/attachments/64072481-abe4-4128-ac42-a19bce1f8d17?platform=QnA

    Was this answer helpful?

    0 comments No comments
  4. Drew - 810 Reputation points
    2024-09-13T08:34:30+00:00

    Version 128.0.2739.79: September 12, 2024

    Fixed various bugs and performance issues, improved reliability.

    Stable channel security updates are listed here.

    Fixes

    • Fixed an issue that caused deployed pinned Shortcuts to the Taskbar to be duplicated.

    Improved reliability

    • Fixed a browser crash that occurred when trying to launch a custom protocol from a web page when using the URLAllowlist policy on a managed device.

    Cheers,
    Drew![](https://learn-attachment.microsoft.com/api/attachments/5eda0188-5865-4135-a2d0-853f9ca5432a?platform=QnA

    Was this answer helpful?

    0 comments No comments
  5. Drew - 810 Reputation points
    2024-09-07T06:37:46+00:00

    Version 128.0.2739.67: September 5, 2024

    Fixed various bugs and performance issues.

    Cheers,
    Drew![](https://learn-attachment.microsoft.com/api/attachments/e6ced713-e1b0-4a50-8910-059579aba1f0?platform=QnA

    Was this answer helpful?

    0 comments No comments