• This configuration should only be used in specific cases where testing with both browser versions is required. The Microsoft Edge Legacy desktop app will reach end of support on March 9, 2021 in favor of the new Microsoft Edge. This means that Microsoft Edge Legacy will not receive security updates after that date.
• Test IE11 and Microsoft Edge Legacy using free Windows 10 virtual machines you download and manage locally Select a download Virtual Machines Select one IE8 on Win7 (x86) IE9 on Win7 (x86) IE10 on Win7 (x86) IE11 on Win7 (x86) IE11 on Win81 (x86) MSEdge on Win10 (x64) Stable 1809 Choose a VM platform: Select one.

1. Browser - Edge 18
2. Edge 18 Browser Update
3. Microsoft Edge Browser App
4. Browserslist Edge 18
5. Microsoft Edge Browser 18
6. Web Browser Edge 18

Note: I expect to update this post over time. Last update: 12/10/2020.

As our new Edge Insider builds roll out to the public, we’re starting to triage reports of compatibility issues where Edge79+ (the new Chromium-based Edge, aka Anaheim) behaves differently than the old Edge (Edge18, aka Spartan, aka Edge Legacy) and/or Google Chrome.

EXTRA BENEFITS: – 600+ servers in 40+ countries – Automatic timezone change – Individual VPN settings for different sites – The connection speed of up to 100 Mbit – Priority customer support service HOW TO START USING BROWSEC 1. Get Browsec from the Edge Store by clicking the “Get” button. Install the app in the browser 3.

In general, Edge79+ will behave very similarly to Chrome. When comparing Edge and Chrome behavior, be sure to compare against the corresponding Chrome Stable, Beta, Dev and Canary channels; Edge 80 vs Chrome 80, etc.

We expect there will be some behavioral deltas between Edge79+ and its Chrome-peer versions, so I’ll note those here too.

Note: I’ve previously blogged about interop issues between Edge18 and Chrome.

Navigation

• For security reasons, Edge79 and Chrome block navigation to file:// URLs from non-file URLs.
• In Edge18 and Internet Explorer, attempting to navigate to an App Protocol with no handler installed shows a prompt to visit the Microsoft Store to find a handler. In Chrome/Edge79, the navigation attempt is silently ignored.
• Edge 18 and Internet Explorer offer a msLaunchUri API for launching and detecting App Protocols. This API is not available in Edge 79 or Chrome.
• Edge 18 and Internet Explorer allow an App Protocol handler to opt-out of warning the user on open using the WarnOnOpen registry key. Edge 79 and Chrome do not support this registry key.

Downloads

• Unlike IE/Edge18, Edge79/Chrome do not support DirectInvoke, a scheme whereby a download is converted into the launch of an application with a URL argument. DirectInvoke is most commonly used when launching Office documents and when running ClickOnce applications. For now, users can workaround the lack of ClickOnce support by installing an extension. Update: In Edge 78+, DirectInvoke is enabled; to enable ClickOnce, see the edge://flags/#edge-click-once setting.
• Edge79/Chrome do not support the proprietary msSaveBlob or msSaveOrOpenBlob APIs supported in Edge18. In most cases, you should instead use an A element with a download attribute.
• Edge18 did not support navigation to or downloading from data URLs via the download attribute; Edge79/Chrome allow the download of data URLs up to 2mb in length. In most cases, you should prefer blob urls.

Network Proxy

• Edge 79+/Chrome adopt the system’s proxy settings by default. If a proxy script is supplied, it is evaluated using the built-in V8 script engine. In contrast, Edge 18 and earlier use the WinHTTP Proxy Service in Windows. Further discussion of the implications of this difference can be found at the end of this post.
  Microsoft DirectAccess and similar networking software may not work properly when Chromium performs proxy determination internally. You can instruct Edge 79+ to use the WinHTTP Proxy Service by launching the browser with the –winhttp-proxy-resolver command line argument. This feature will be exposed to Group Policy in a future release of Edge.
• Edge 79+/Chrome do not allow loading a PAC script from a file:// URI. (IE allowed this long ago, but it hasn’t been supported in a long time).
• If you are behind an authenticating proxy server and choose to save your proxy username/password in Edge 18 or Internet Explorer, the WinHTTP Proxy Service will store those credentials in CredMan and reuse those proxy credentials for subsequent challenges even if you restart the browser. The credentials will also be available for silent use by other applications (e.g. the Windows Store app). Even if you don’t tick the “Remember my credentials” checkbox, the proxy credentials will be remembered for the Windows logon session.
  In contrast, if you choose to save your proxy username/password in Edge79+, Chrome, or Firefox, you will be shown an authentication prompt once every time you restart your browser. The username:password will be pre-filled but you must hit “OK” to submit the credentials. Stored credentials will not be available for use by other applications that wish to use the proxy.

Network Protocols & Cache

• Chrome/Edge79+ support the HTTP3/QUIC protocol. Edge 18 and earlier do not.
• Generally, Chrome/Edge79+ have enhanced support for caching directives, fixing many limitations in the IE/Edge18 cache. However, one delta is that Chrome/Edge79+ do not respect Cache-Control directives specified by META HTTP-EQUIV directives inside a HTML page. Caching directives must instead be specified in the appropriate HTTP Response headers.
• Chrome/Edge have limited support for, and will eventually remove, the FTP protocol.
• Edge Legacy supports the Cache-Control token immutable; Chromium-based browsers do not (yet).
• Chrome/Edge/Safari will fail responses served over HTTP2 with ERR_HTTP2_PROTOCOL_ERROR if a response header name contains a space. Edge Legacy/Firefox will just ignore the header, and IE will allow it.

HTTPS – TLS Protocol

• Edge79 and Chrome enable TLS/1.3 by default; Edge18 does not support TLS/1.3 prior to Windows 10 19H1, and even on that platform it is disabled by default (and known to be buggy).
• Edge79 and Chrome support a different list of TLS ciphers than Edge18.
• Edge79 and Chrome send GREASE tokens in HTTPS handshakes; Edge18 does not.
• Edge79, Chrome, Firefox, and Safari prohibit connections for HTTP/2 traffic from using banned (weak) ciphers, showing ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY if the server attempts to use such ciphers. Edge18 did not enforce this requirement. This has primarily impacted intranet websites served by IIS on Windows Server 2012 where the server was either misconfigured or does not have the latest updates installed. Patching the server and/or adjusting its TLS configuration will resolve the problem. End-users should complain to the server operators, and can work around the problem by closing all instances of Edge then restarting with a commandline argument msedge.exe –disable-http2 to disable support for the faster network protocol.

HTTPS – Certificates

• Edge79 and Chrome require that a site’s certificate contain its domain name in the SubjectAltName (SAN) field. Edge 18 permits the certificate to omit the SAN and if the domain name is in the Subject Common Name (CN) field. (All public CAs use the SAN; certificates that chain to a local/enterprise trusted root may need to be updated).
• Firefox, Edge79 and Chromium 41+, reject wildcarded SubjectAltNames where the * is not the entirety of the leftmost label. In contrast, Edge18 and IE will match a SubjectAltName of w*.example.com to the server http://www.example.com while the modern browsers will not.
• Edge79 and Chrome do not allow server certificate chains that contain SHA-1 signatures. Edge Legacy and IE permit SHA-1 in chains that certificates that chain to a local/enterprise root. A policy added in Edge 86 will temporarily allow SHA-1 chains.
• Edge79 and Chrome require certificates that chain to trusted root CAs to be logged in Certificate Transparency (CT). This generally isn’t a problem because public roots are supposed to log in CT as a part of their baseline requirements. However, certain organizations (including Microsoft and CAs) have hybrid roots which are both publicly trusted and issue privately within the organization. As a result, loading pages may error out with NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED. To mitigate this, such organizations must either start logging internal certificates in CT, or set one of three policies under HKLMSOFTWAREPoliciesMicrosoftEdge. Edge18 does not support CT.
• For most (non-EV) certificates, Chrome/Edge79 will not request certificate revocation information from the network (OCSP, CRL download), using revocation information only if it’s cached on the client or stapled in the TLS handshake. Internet Explorer and Legacy Edge would actively hit the network for revocation information by default. See What’s the story with certificate revocation? for discussion.
• Edge79 and Chrome use a custom Win32 client certificate picker UI, while Edge18 uses the system’s default certificate picker.

Cookies

• Edge79 and Chrome support the Leave Secure Cookies Alone spec, which blocks HTTP pages from setting cookies with the Secure attribute and restricts the ways in which HTTP pages may interfere with cookies sent to HTTPS pages. Legacy Edge does not have these restrictions.
• Edge79 and Chrome support Cookie prefixes (restrictions on cookies whose names begin with the prefixes __Secure- and __Host-). Legacy Edge does not enforce these restrictions.
• Edge79, Chrome, and Firefox ignore Set-Cookie headers with values over 4096 characters in length (including cookie-controlling directives like SameSite). In contrast, IE and Edge18 permit cookies with name-value pairs up to 5118 characters in length.

Authentication and Login

• In Edge79, Edge18, and Firefox, running the browser in InPrivate mode disables automatic Integrated Windows Authentication. Chrome and Internet Explorer do not disable automatic authentication in private mode. You can disable automatic authentication in Chrome by launching it with a command line argument: chrome.exe --auth-server-whitelist='_'
  Starting in Edge 82, flags on the edge://flags page allow re-enabling Automatic Authentication for Guest and InPrivate sessions.
  
• Edge18/Edge79 integrates a built-in single-sign-on (SSO) provider, such that configured account credentials are automatically injected into request headers for configured domains; this feature is disabled in InPrivate mode. Chrome does not have this behavior for Microsoft accounts.
• Edge18 supports Azure Active Directory’s Conditional Access feature. For Chrome, an extension is required. Edge79 has not yet integrated support for this feature.
• Chrome and Edge 79+ choose the strongest HTTP Authentication scheme advertised by the server, regardless of the order of WWW-Authenticate headers provided. In contrast, Edge 18/IE prioritize the first non-BASIC scheme offered. This can lead the new Edge to choose Negotiate in cases where the older Edge might pick NLTM.
• By default, Internet Explorer and Edge Legacy would automatically send a client certificate to a server on your Local Intranet if the client only had one certificate available. In Chromium, a Group Policy must be set.
• Edge Legacy and IE encode BASIC authentication credentials using iso-8859-1. Chromium, Safari, and Firefox use UTF-8 as suggested by RFC7617.

WebAPIs

• Edge18 includes an API window.external.GetHostEnvironmentValue that returns some interesting information about the system, including whether it is running in the “Windows 10 S” lockdown mode. Edge76 and Chrome do not support this API. Update: Edge 78 restored this API with a limited set of tokens:
  {“os-architecture”:”AMD64″,”os-build”:”10.0.18362″,”os-sku”:”4″,”os-mode”:”2″}. The os-mode of 2 indicates a Windows 10 S configuration.
• Edge 18 Legacy and Internet Explorer are the only browsers that consider all local-PC file:// URIs to be same-origin, allowing them to refer to other resources on the local computer. Other browsers treat file origins as unique, blocking DOM interactions between frames from different files, blocking transform of XML files using adjacent XSL files, etc.
• Google Chrome ships with the Portable Native Client plugin; Edge79 does not include this plugin. The plugin is little-used and you’re unlikely to encounter problems with its absence except on the Google Earth website. PNaCl is deprecated in favor of WebAssembly and is slated to be removed from Chrome in Q2 2019.
• The Edge Platform Status site also includes a short list of features that are supported in Edge18 but not Chromium-derived browsers.
• The HTML5 SpeechRecognition API fails silently in Edge 76 to 82 because we do not connect to Google Web Services and have not yet done the work to hook this API up to a Microsoft Web Service. Forum thread.
• The Edge Legacy and IE implementation offer only a limited set of algorithms (Test page) and have some undocumented limits (e.g. you must use a 12byte IV for AES-GCM). The Chromium implementation offers better support for a wider variety of scenarios.
  

Group Policy and Command Line Arguments

Edge79+’s Policy List includes a set of Group Policies that match Chrome’s Group Policies and Edge’s command line arguments generally match Chrome’s. The minor changes include:

If you’re using the registry to set a policy for Edge, put it under the

…node instead of under the

node.

If you’re trying to use a Chrome command line argument when launching in the new MSEdge.exe and it’s not working, check whether it has “blacklist” or “whitelist” in the name. If so, we probably renamed it.

For instance, want to tell Edge not to accept a 3DES ciphersuite for TLS? You need to use

…instead of

….as you would with Chrome.

Zones

Chrome and Edge 79+ make very limited use of the Windows Security Zones architecture. See this post for more information.

In contrast, Internet Explorer made extensive use of Zones to control security and compatibility changes. By way of example, back in IE8, a change was made to the browser such that the file upload control would no longer send the full path of an uploaded file. For instance, when uploading C:usersericlawdesktopThisIsMyFile.jpg to the server, the browser would instead send C:fakepathThisIsMyFile.jpg. The main reason is privacy: we didn’t want the remote website to be able to infer that the user uploading the file was named “EricLaw” based on the information about their local file system paths. This redaction became a web standard—now ALL browsers send “fakepath” and doing so is required by the HTML specification. However, for compatibility reasons, Internet Explorer would only apply this protection to sites in the Internet Zone; sites loaded in the Intranet zone would continue to send the unredacted file path. This behavior is controlled by the “Include local directory path when uploading files to a server” setting in the Internet Control Panel:

Modern browsers, including Microsoft Edge, do not have any setting like this one; there’s no way to turn off the redaction of the file path. Available workarounds would be to either 1) Put this site in IE Mode, or to 2) restructure the application such that it does not attempt to get a local file path from the user using a File Upload control.

User-Agent

Browsers identify themselves to servers using a User-Agent header. A top source of compatibility problems is caused by sites that attempt to behave differently based on the User-Agent header and make incorrect assumptions about feature support, or fail to update their checks over time. Please, for the love of the web, avoid User-Agent Detection at all costs!

Chrome User-Agent string:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36

Edge77 Beta (Desktop) User-Agent string:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.19 Safari/537.36 Edg/77.0.235.9

Edge18 User-Agent string:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Edge/18.18362

Edge73 Stable (Android) User-Agent string:
Mozilla/5.0 (Linux; Android 10; Pixel 3 XL) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.90 Mobile Safari/537.36 EdgA/42.0.4.3892

You’ll note that each of the Edge variants uses a different token at the end of the User-Agent string, but the string otherwise matches Chrome versions of the same build. Sites should almost never do anything with the Edge token information– treat Edge like Chrome. Failing to follow this advice almost always leads to bugs.

Sites are so bad about misusing the User-Agent header that Edge was forced to introduce a service-driven override list, which you can find at edge://compat/useragent. Alas, even that feature can cause problems in unusual cases. For testing, you can tell Edge to ignore the list by starting it thusly:

Upcoming Changes

Perhaps the biggest change with the move to the new Chromium-backed Microsoft Edge is a much faster pace of change in the Web Platform. You can keep an eye out on upstream changes using the ChromeStatus schedule page, and Microsoft’s list of site-impacting-changes.

Stay compatible out there!

-Eric

These release notes provide information about new features and non-security updates that are included in the Microsoft Edge Stable Channel.

• All the security updates are listed here.
• Archived release notes for Microsoft Edge Stable Channel are located here.

To understand Microsoft Edge channels, see the Overview of the Microsoft Edge channels.

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.

Version 90.0.818.46: April 22

Stable channel security updates are listed here.

Version 90.0.818.42: April 19

Fixed various bugs and performance issues.

Version 90.0.818.41: April 16

Stable channel security updates are listed here.

Version 90.0.818.39: April 15

Stable channel security updates are listed here.

Feature updates

• Single Sign On (SSO) is now available for Azure Active Directory (Azure AD) accounts and Microsoft Account (MSA) on macOS. A user signed in on Microsoft Edge on macOS will now get automatically signed into websites that are configured to allow single sign on with Work and Microsoft accounts (for example, bing.com, office.com, msn.com, and outlook.com).

• Kiosk mode. Starting with Microsoft Edge version 90, we have locked down the UI print settings to only allow the configured printers and “Print to PDF” options. We have also done improvements within the assigned access single app kiosk mode to restrict the launch of other applications from the browser. For more information about the kiosk mode features please go here.

• Printing:

  • New print rasterization mode for non-PostScript printers. Starting with Microsoft Edge version 90, Admins can use a new policy to define print rasterization mode for their users. This policy controls how Microsoft Edge prints to non-PostScript printers on Windows. Sometimes print jobs on non-PostScript printers need to be rasterized to print correctly. The print options are Full and Fast.

  • Additional page scaling options for printing. Users are now able to customize scaling while printing webpages and PDF documents using additional options. The 'Fit to Page' option ensures that the webpage or document is fit into the space available in the selected 'Paper size' for printing. The 'Actual size' option ensures that there are no changes in the size of the contents being printed regardless of the selected 'Paper size'.

• Productivity:

  • Autofill suggestions are extended to include address fields content from clipboard. Clipboard content is parsed when you click on a profile/address field (for example, phone, email, zip code, city, state, etc.) to show as autofill suggestions.

  • Users can search for autofill suggestions even if a form or field isn’t detected. Today if you have your information saved on Microsoft Edge, autofill suggestions pop up automatically and help you save time while filling out forms. In cases where autofill misses a form, or if you want to fetch data in forms that don't typically have autofill (like temporary forms), you can search for your information use autofill.

• Access downloads from a flyout in the menu bar. Downloads will appear in the top-right corner with all the active downloads in one place. This menu is easily dismissible so users can continue browsing uninterrupted, and they can monitor overall download progress right from the toolbar. Learn more.

• Improvements to font rendering. Starting with Microsoft Edge version 90, we made improvements to the rendering of text to improve clarity and reduce blurriness. Part of the font rendering improvements will land in Beta version 90 but are disabled by default.

• Kids mode. We have updated the policy so that when the policy is enabled, it will disable the Kid Mode feature in addition to family safety. More about Kids Mode here

Policy updates

New policies

Eight new policies were added. Download the updated Administrative Templates from the Microsoft Edge Enterprise landing page. The following new policies were added:

• ApplicationGuardFavoritesSyncEnabled - Application Guard Favorites Sync Enabled
• FetchKeepaliveDurationSecondsOnShutdown- Fetch keepalive duration on shutdown
• ManagedConfigurationPerOrigin - Sets managed configuration values for websites to specific origins
• PrintRasterizationMode - Print Rasterization Mode
• QuickViewOfficeFilesEnabled - Manage QuickView Office files capability in Microsoft Edge
• SSLErrorOverrideAllowedForOrigins - Allow users to proceed from the HTTPS warning page for specific origins
• WindowOcclusionEnabled - Enable Window Occlusion
• WindowsHelloForHTTPAuthEnabled - Windows Hello For HTTP Auth Enabled

Deprecated policies

• NativeWindowOcclusionEnabled - Enable Native Window Occlusion
• SSLVersionMin- Minimum TLS version enabled

Version 89.0.774.77: April 14

Stable channel security updates are listed here.

Version 89.0.774.76: April 12

Fixed various bugs and performance issues.

Version 89.0.774.75: April 8

Fixed various bugs and performance issues.

Version 89.0.774.68: April 1

Stable channel security updates are listed here.

Version 89.0.774.63: March 25

Fixed various bugs and performance issues.

Version 89.0.774.57: March 18

Fixed various bugs and performance issues.

Version 89.0.774.54: March 13

Important

This update contains CVE-2021-21193 which has been reported by the Chromium team as having an exploit in the wild. For more information, see the Security Update Guide.

Stable channel security updates are listed here.

Version 89.0.774.50: March 10

Fixed various bugs and performance issues.

Version 89.0.774.48: March 8

Fixed various bugs and performance issues.

Version 89.0.774.45: March 4

Important

This update contains CVE-2021-21166 which has been reported by the Chromium team as having an exploit in the wild. For more information, see the Security Update Guide.

Stable channel security updates are listed here.

Resolved issues

• Taskbar and Start menu shortcut updates and fixes:
  • Right-clicking the Microsoft Edge shortcut in the Start menu will now properly show the option to unpin Microsoft Edge from the taskbar when it’s pinned.
  • Start layouts that include a taskbar configuration to pin Microsoft Edge to the taskbar will no longer result in a second Microsoft Edge shortcut getting pinned to the taskbar.
  • Organizations using Windows Roaming Profiles will no longer see a blank white icon in place of the Microsoft Edge icon on the taskbar when their users log on to Windows.

Feature updates

• Kiosk mode enables additional lockdown capabilities. Starting with Microsoft Edge version 89, we have added additional lockdown capabilities within kiosk mode to enable customers to get the job done in a productive and more secure experience. Learn more.

• The Enterprise Mode Site List Manager tool will be available in the browser through the edge://compat page. You can use this tool to create, edit and export your site list XML for Internet Explorer mode on Microsoft Edge. You can enable access to this tool as needed through group policy. Learn More.

• Improve browser performance with sleeping tabs. Sleeping tabs improves browser performance by putting inactive tabs to sleep to free up system resources like memory and CPU so active tabs or other applications can use them. Users can prevent sites from going to sleep and configure the length of time before an inactive tab goes to sleep. To keep users in their flow, there are also heuristics to prevent certain sites from going to sleep, such as intranet sites. This feature can be managed with group policies.

• Reset your Microsoft Edge sync data in the cloud manually. We are introducing a way to reset your Microsoft Edge sync data from within the product. This ensures that your data is cleared from Microsoft services, as well as resolving certain product issues that previously required a support ticket.

• Intelligent enablement of Single sign-on (SSO) for all Windows Azure Active Directory (Azure AD) accounts for users with a single non-Azure AD Microsoft Edge profile. Automatically turn this setting on for users that might benefit the most from this feature. If a user has only one Microsoft Edge profile (and it’s not Azure AD or Kids Mode), the setting will be automatically turned on when Microsoft Edge launches. This auto-toggle will also automatically turn off if a user later chooses to sign into a different Microsoft Edge profile with an Azure AD account. Users can manually update their preferences for this feature in Settings > Profiles >Profile Preferences > Allow single sign-on for work or school sites using this profile.

• Improvements to text selection experience within PDF documents. Users will begin to get a smoother and more consistent text selection experience across PDF documents opened in Microsoft Edge starting with version 89.

• Date of birth field now supported in autofill. Today Microsoft Edge helps you save time and effort while filling out forms and creating accounts online by auto filling your data like addresses, names, phone numbers, etc. Starting with Microsoft Edge version 89, we are adding support for another field that you can have saved and auto-filled - date of birth. You can view, edit and delete this information anytime in your profile settings.

Policy updates

New policies

Seven new policies were added. Download the updated Administrative Templates from the Microsoft Edge Enterprise landing page. The following new policies were added.

• BrowsingDataLifetime - Browsing Data Lifetime Settings
• MAMEnabled - Mobile App Management Enabled
• DefinePreferredLanguages - Define an ordered list of preferred languages that websites should display in if the site supports the language
• ShowRecommendationsEnabled - Allow recommendations and promotional notifications from Edge
• PrintingAllowedBackgroundGraphicsModes - Restrict background graphics printing mode
• PrintingBackgroundGraphicsDefault - Default background graphics printing mode
• SmartActionsBlockList - Block smart actions for a list of services

Browser - Edge 18

Obsoleted policies

The following policies are obsoleted.

• ForceLegacyDefaultReferrerPolicy - Use a default referrer policy of no-referrer-when-downgrade
• MetricsReportingEnabled - Enable usage and crash-related data reporting
• SendSiteInfoToImproveServices - Send site information to improve Microsoft services

Version 88.0.705.81: February 25

Fixed various bugs and performance issues.

Version 88.0.705.74: February 17

Stable channel security updates are listed here.

Version 88.0.705.68: February 11

Fixed various bugs and performance issues.

Version 88.0.705.63: February 5

Important

This update contains CVE-2021-21148 which has been reported by the Chromium team as having an exploit in the wild.

Stable channel security updates are listed here. Gta san andreas 1.08 apk data for android.

Version 88.0.705.62: February 4

Stable channel security updates are listed here.

Fixed various bugs and performance issues.

Version 88.0.705.56: January 28

Fixed various bugs and performance issues.

Version 88.0.705.53: January 26

Fixed various bugs and performance issues.

Version 88.0.705.50: January 21

Stable channel security updates are listed here.

Feature updates

• Emailchemy. Deprecations:

  • Deprecate support for FTP protocol. Support for the legacy FTP protocol has been removed from Microsoft Edge. Attempting to navigate to an FTP link will result in the browser directing the Operating System to open an external application to handle the FTP link. Alternatively, IT administrators can configure Microsoft Edge to use IE Mode for sites that rely on the FTP protocol.
  • Adobe Flash support will be removed. Starting with Microsoft Edge Beta version 88, Adobe Flash capability and support will be removed. Learn more: Update on Adobe Flash Player End of Support - Microsoft Edge Blog (windows.com)

• Authentication:

  • Single Sign On (SSO) now available for Azure Active Directory (Azure AD) accounts and Microsoft Account (MSA) on down-level Windows. A user signed in on Microsoft Edge on down-level Microsoft Windows (7, 8.1) will now get automatically signed into websites that are configured to allow single sign on with Work and Microsoft accounts (e.g., bing.com, office.com, msn.com, outlook.com).
    Note: A user may have to sign out and then sign back in if they'd signed into Microsoft Edge in a version prior to Microsoft Edge 88 to leverage this feature.

  • Single sign-on (SSO) to work sites using any Windows Azure Active Directory (Azure AD) accounts on system in non-Azure AD Microsoft Edge profiles. This feature can be enabled for any profile that isn’t signed-in with a work/school account and is not guest or in-private and allows the use of any signed-in work/school account on operating system with that profile. This feature can be configured in Settings > Profiles > Profile Preferences > Allow single sign-on for work or school sites using this profile.

    Note

    'Single sign-on (SSO) for all Windows accounts using the Microsoft Edge profile' is an update to the January 21 release notes.

• Kiosk mode option to end session. The 'End session' button is now available in a kiosk mode public browsing experience. This feature ensures that browser data and settings are deleted when Microsoft Edge is closed. Learn more about kiosk mode features and roadmap, Configure Microsoft Edge kiosk mode.

• Security and Privacy:

  • Alerts are generated if a user's password is found in an online leak. User passwords are checked against a repository of known-breached credentials and sends the user an alert if a match is found. To ensure security and privacy, user passwords are hashed and encrypted when they're checked against the database of leaked credentials.
  • Automatically upgrade mixed content. Secure pages delivered over HTTPS may contain references images that are served over non-secure HTTP. To improve privacy and security in Microsoft Edge 88, those images will be retrieved over HTTPS instead. If the image is not available over HTTPS, it will not be loaded.
  • View site permissions by site and by recent activity. Starting with Microsoft Edge 88, users will be able to manage site permissions more easily. They will be able to view permissions by web site rather than just permission type. Additionally, we’ve added a recent activity section that will show a user all the recent changes to their site permissions.
  • Increased controls for browser cookies. Starting with Microsoft Edge 88, users can delete third party cookies without affecting first party cookies. Users will also be able to filter their cookies by first or third party and sort by name, number of cookies, and the amount of data stored and last modified.

• Passwords:

  • Password Generator. Microsoft Edge offers a built-in strong password generator that you can use when signing up for a new account or when changing an existing password. Just look for the browser-suggested password drop down in the password field and when selected, it will automatically save to the browser and sync across devices for easy future use.
  • Password Monitor. When any of your passwords saved to the browser matches with those seen in the list of leaked credentials, Microsoft Edge will notify you and prompt you to update your password. Password Monitor scans for matches on your behalf and is on by default.
  • Edit Password. You can now edit your saved passwords directly in Microsoft Edge Settings. Any time a password has been updated outside of Microsoft Edge, it’s easy to replace the saved older password with the new one by editing the saved entry in Settings.

• Improve Microsoft Edge startup speed with startup boost. To improve Microsoft Edge startup speed, we’ve developed a feature named startup boost. Startup boost makes Microsoft Edge launch faster by enabling Microsoft Edge to run in the background. Note: This feature is limited to a randomly selected group of users who have enabled experimentation. These users are giving feedback to the feature team.

• Productivity:

  • Improve productivity and multi-tasking with vertical tabs. As the number of horizontal tabs grows, site titles start to get cut off and tab controls are lost as each tab shrinks. This interrupts user workflow as they spend more time finding, switching, and managing their tabs and less time on the task at hand. Vertical tabs let users move their tabs to the side, where vertically aligned icons and longer site titles make it easier to quickly scan, identify and switch to the tab they want to open.
  • Auto filling the date of birth field. Microsoft Edge already helps save time and effort while filling out forms and creating accounts online by auto filling user data such as addresses, names, phone numbers, etc. Microsoft Edge now supports the date of birth field which users can save and auto fill. A user can view, edit and delete this information anytime in their profile settings.
  • Improvements to Recently closed in History. Recently closed now keeps the last 25 tabs and windows from any past browsing session rather than just the previous session. Users can select Recently closed in the new History experience to see all the tabs that were open.
  • “Your day at a glance” feature enabled by default. Starting with Microsoft Edge version 88, information workers can benefit from intelligent productivity features on their New tab page (NTP). Microsoft Edge 87 users will also experience these features within 2 weeks after Microsoft Edge 88 release. We offer users signed in with their work or school account personalized and relevant content powered by their M365 Graph. Users can quickly scan their “Your day at a glance” modules to easily track their meetings and recent work as well as quickly launch the applications they want to use.

• History and open tabs sync. History and open tabs sync is now available for users to enjoy. Enabling these features will help users pick up where they left off by making their browsing history and open tabs available on all their syncing devices. We've updated sync and browser history policies, so now users are connected and productive across any devices by using Microsoft Edge. Learn more.

• PDF:

  • PDF document display in book view (two page). Starting with Microsoft Edge version 88, users can view PDF documents in a single page or in the two page book view. To change the view, click the Page View button in the toolbar.
  • Anchored text notes support for PDF files. Starting with Microsoft Edge version 87, users can add typed text notes on any piece of text in PDF files.

• Fonts:

  • Browser icons are updated to the Fluent design system. As part of our continued work around Fluent Design in the browser, we've made changes to closer align icons to the new Microsoft icon system. These changes will impact many of our high-touch user interfaces, including tabs, address bar, as well as navigational and wayfinding icons found in our various menus.
  • Improved font rendering. Text rendering is improved for better clarity and to reduce blurriness.

Policy updates

New policies

Eighteen new policies were added. Download the updated Administrative Templates from the Microsoft Edge Enterprise landing page. The following new policies were added.

• BasicAuthOverHttpEnabled - Allow Basic authentication for HTTP.
• BlockExternalExtensions - Blocks external extensions from being installed.
• InternetExplorerIntegrationLocalFileAllowed - Allow launching of local files in Internet Explorer mode.
• InternetExplorerIntegrationLocalFileExtensionAllowList - Open local files in Internet Explorer mode file extension allow list.
• InternetExplorerIntegrationLocalFileShowContextMenu - Show context menu to open a link in Internet Explorer mode.
• IntranetRedirectBehavior - Intranet Redirection Behavior.
• PrinterTypeDenyList - Disable printer types on the deny list.
• ShowMicrosoftRewards - Show Microsoft Rewards experiences.
• SleepingTabsEnabled - Configure Sleeping Tabs.
• SleepingTabsTimeout - Set the background tab inactivity timeout for Sleeping Tabs.
• SleepingTabsBlockedForUrls - Block Sleeping Tabs on specific sites.
• StartupBoostEnabled - Enable startup boost.
• TargetBlankImpliesNoOpener - Do not set window.opener for links targeting _blank.
• UpdatePolicyOverride - Specifies how Microsoft Edge Update handles available updates from Microsoft Edge.
• VerticalTabsAllowed - Configures availability of a vertical layout for tabs on the side of the browser.
• WebRtcAllowLegacyTLSProtocols - Allow legacy TLS/DTLS downgrade in WebRTC.
• WebWidgetAllowed - Enable the Web widget.
• WebWidgetIsEnabledOnStartup - Allow the Web widget at Windows startup.

Deprecated Policies

• ProactiveAuthEnabled - Enable Proactive Authentication.
• ProxyBypassList - Configure proxy bypass rules.
• ProxyMode - Configure proxy server settings.
• ProxyPacUrl - Set the proxy .pac file URL.
• ProxyServer - Configure address or URL of proxy server.
• WebDriverOverridesIncompatiblePolicies - Allow WebDriver to Override Incompatible Policies.

Obsoleted Policies

• AllowPopupsDuringPageUnload - Allows a page to show popups during its unloading.
• DefaultPluginsSetting - Default Adobe Flash setting.
• PluginsAllowedForUrls - Allow the Adobe Flash plug-in on specific sites.
• PluginsBlockedForUrls - Block the Adobe Flash plug-in on specific sites.
• RunAllFlashInAllowMode - Extend Adobe Flash content setting to all content.

Version 87.0.664.75: January 7

Stable channel security updates are listed here.

Version 87.0.664.66: December 17

Fixed various bugs and performance issues.

Version 87.0.664.60: December 10

Fixed various bugs and performance issues.

Version 87.0.664.57: December 7

Fixed various bugs and performance issues. Stable channel security updates are listed here.

Version 87.0.664.55: December 3

1password facebook. Fixed various bugs and performance issues. The following feature was updated for this release.

• Shopping is enabled by default. Starting with Microsoft Edge version 87, enterprise users can benefit from shopping in Microsoft Edge. With Shopping features, Microsoft Edge helps users find coupons and better prices while shopping online. (The coupon experience was released with Stable version 87.0.664.41). The price comparison experience is now available with this update. This feature can be configured using the EdgeShoppingAssistantEnabled policy. See our Blog and Learn More about Microsoft Shopping.

Version 87.0.664.52: November 30

Fixed various bugs and performance issues.

Version 87.0.664.47: November 23

Fixed various bugs and performance issues.

Version 87.0.664.41: November 19

Stable channel security updates are listed here.

Feature updates

• Automatic redirection for incompatible sites from Internet Explorer to Microsoft Edge. Starting with the Microsoft Edge 87 Stable update, public websites that show an incompatibility message on Internet Explorer will be automatically redirected to Microsoft Edge. To learn more and to configure this experience, see Redirecting incompatible sites.

• Kiosk mode privacy features enabled. Starting with Microsoft Edge version 87, kiosk mode features that will help enterprises around the privacy of user data will be enabled. These features will enable experiences such as clear the user data on exit, delete downloaded files and to reset the configured start experience after a specified amount of idle time. Learn more about how to Configure Microsoft Edge kiosk mode

• Shopping features enabled by default. Starting with Microsoft Edge version 87 enterprise users can also benefit from shopping in Edge. With Shopping features, Microsoft Edge helps users to find coupons and better prices while shopping online. Coupon experience is available with this update and price comparison will be released in upcoming updates for Microsoft Edge 87. This feature can be configured through EdgeShoppingAssistantEnabled policy. See our Blog and Learn More about Microsoft Shopping.

• ClickOnce deployment enabled by default. ClickOnce is enabled by default in Microsoft Edge 87, which reduces the barriers for enterprises to deploy software and better align with Microsoft Edge Legacy browser behavior. Starting in Microsoft Edge 87, the ClickOnceEnabled policy's 'Not configured' state will reflect the new default ClickOnce state of Enabled (as compared to the previous default state of Disabled).

• The enterprise new tab page (NTP) integrates productivity with customizable, work-relevant feed content. The enterprise NTP blends the Office 365 productivity page we offer to users signed in with their work or school account with personalized, work-relevant company and industry feeds that are organized in a single page. Users will be able to recognize the familiar Office 365 content and Microsoft Search for Business powered by Bing. In addition, they can easily customize 'My Feed' by choosing the most relevant content to them from the available content and modules for their organization. IT Administrators can control the News feed settings for their organization, including the selected industry for the Edge new tab page by going to Microsoft 365 admin center. Learn more

• Privacy and Security:

  • Support TLS Token Binding for policy-configured sites. TLS Token binding helps prevent token theft attacks to ensure that cookies can't be reused from a device other than the device upon which they were initially set. The use of TLS token binding requires setting the AllowTokenBindingForUrls policy and requires that the sites listed support this feature.

• Keyboard support for highlighter on PDF files. Users can use their keyboard keys to highlight any text on a PDF.

• Printing:

  • Choose which side to flip on when printing on both sides. Users can choose to flip on the long side or the short side of a sheet when printing on both sides.
  • Choose print rasterization mode for the enterprise. Control how Microsoft Edge prints to a non-PostScript printer on Windows. Sometimes print jobs on non-PostScript printers need to be rasterized to print correctly. The print options are 'Full' and 'Fast'.

Policy updates

New policies

Ten new policies were added. Download the updated Administrative Templates from the Microsoft Edge Enterprise landing page. The following new policies were added.

• ConfigureFriendlyURLFormat - Configure the default paste format of URLs copied from Microsoft Edge, and determine if additional formats will be available to users.
• EdgeShoppingAssistantEnabled - Shopping in Microsoft Edge enabled.
• HideInternetExplorerRedirectUXForIncompatibleSitesEnabled - Hide the one-time redirection dialog and the banner on Microsoft Edge.
• KioskAddressBarEditingEnabled - Configure address bar editing for kiosk mode public browsing experience.
• KioskDeleteDownloadsOnExit - Delete files downloaded as part of kiosk session when Microsoft Edge closes.
• PasswordRevealEnabled - Enable Password reveal button.
• RedirectSitesFromInternetExplorerPreventBHOInstall - Prevent install of the browser helper object (BHO) to redirect incompatible sites from Internet Explorer to Microsoft Edge.
• RedirectSitesFromInternetExplorerRedirectMode - Redirect incompatible sites from Internet Explorer to Microsoft Edge.
• SpeechRecognitionEnabled - Configure Speech Recognition.
• WebCaptureEnabled - Enable web capture feature in Microsoft Edge.

Deprecated Policy

NewTabPageSetFeedType - Configure the Microsoft Edge new tab page experience.

Obsoleted Policy

EnableDeprecatedWebPlatformFeatures - Re-enable deprecated web platform features for a limited time.

Version 86.0.622.69: November 13

Important

This update contains CVE-2020-16013 and CVE-2020-16017, that have been reported by the Chromium team as having an exploit in the wild.

Stable channel security updates are listed here.

Version 86.0.622.68: November 11

Edge 18 Browser Update

Stable channel security updates are listed here

Version 86.0.622.63: November 4

Important

This update contains CVE-2020-16009, that has been reported by the Chromium team as having an exploit in the wild.

Stable channel security updates are listed here.

Version 86.0.622.61: November 2

Fixed various bugs and performance issues.

Version 86.0.622.58: October 29

Fixed various bugs and performance issues.

Version 86.0.622.56: October 27

Fixed various bugs and performance issues.

Microsoft Edge Browser App

Version 86.0.622.51: October 22

Browserslist Edge 18

Stable channel security updates are listed here

Version 86.0.622.48: October 20

Fixed various bugs and performance issues.

Microsoft Edge Browser 18

Version 86.0.622.43: October 15

Web Browser Edge 18

Fixed various bugs and performance issues.

See also