Microsoft announced in 2018 that they will rebuild the Edge browser and use the Chromium project (Which is a code subset of the Chrome browser) as code basis. The (first) final version has been released on January 15th 2020. Depending on your environment, you might have to perform some additional steps to get the new browser on your clients. Jan 13, 2020 The new Edge Browser integrates the browser engine based on Google’s Chromium project. Microsoft will distribute the final version of the Chromium-based browser to all systems with Windows 10 version 1803 and higher via Windows Update starting January 15, 2020.
[German]On January 15, 2020, (patchday) Microsoft starts the rollout of the Chromium-based Edge. Now Microsoft has clarified once again in which environments automatic update will take place and that enterprise envionments won’t get an automatic update. In addition, some known issues of the new Edge browser with Windows Mixer Users are become public.
Some Overview
Wsus Edge Chromium Software
One year ago Microsoft announced that they started a fundamentally rework of their own Edge browser. The new Edge Browser integrates the browser engine based on Google’s Chromium project. Microsoft will distribute the final version of the Chromium-based browser to all systems with Windows 10 version 1803 and higher via Windows Update starting January 15, 2020.
Microsoft is planning, to update Edge in cyclical intervals, approximately every 6 weeks. What to consider and how to prevent this auto-update is described in the blog post Microsoft’s Chromium Edge will be distributed via update soon.
Clarification: No auto-update in enterprise environments
Microsoft’s announcement to roll out the new Chromium-based Edge to Windows 10 machines via Windows Update has led to many requests from companies. Microsoft therefore felt compelled to clarify the situation.
Lots of speculation about automatic updates of the new Edge on Windows 10. We updated our documentation to make it clear that we’re not planning to push to commercial/enterprise devices. Enterprises have full control over their devices. Read more here: https://t.co/phrYWVgxQE
— Sean Lyndersay (@SeanOnTwt) January 10, 2020
The automatic update of the Edge browser is only available on machines running Windows 10 Home. The same applies to unmanaged machines running Windows 10 Pro, and updates are automatically obtained through Windows Update. Microsoft writes here:
Devices running Windows 10 Home or Pro Edition that are joined to an Active Directory or Azure Active Directory domain, are MDM managed, or are WSUS or WUfB managed, will also be excluded from this automatic update.
Note: Somewhat surprisingly, Windows 10 Home can be included in an Active Directory or Azure Active Directory domain. My knowledge so far is that Windows 10 Home cannot be part of a domain-or did I miss something?
Already on Windows 10 Pro machines using Windows Update for Business (WU4B), Microsoft will not distribute the update for the Edge Browser. The same applies to clients whose updates are distributed via WSUS/SCCM, Intune, or other management tools.
For information on controlling updates via management tools, see this Microsoft support post. On unmanaged Windows 10 machines, automatic updating can be blocked by policy or registry entry (Blocker Toolkit). Details can be found in the blog post Microsoft’s Chromium Edge will be distributed via update soon.
Attention with Windows Mixed Reality
Martin Geuß reports on Dr. Windows, hat users of Windows Mixed Reality cannot use the new Chromium-based Edge. Because according to Microsoft there are still some known issues in this environment in Windows 10 version 1903 or higher.
- Launching any Win32 app, including the new Microsoft Edge, causes the headset display to briefly freeze.
- The Microsoft Edge tile disappears from the Windows Mixed Reality Start menu (you can find it in the “Classic apps” folder).
- Windows from the previous Microsoft Edge are still placed around the mixed reality home, but cannot be used. Attempting to activate those windows launches Edge inside of the Desktop app.
- Selecting a hyperlink in the mixed reality home launches a web browser on the desktop instead of the mixed reality home.
- The WebVR Showcase app is present in the mixed reality home, despite WebVR no longer being supported.
- General improvements to keyboard launch and visuals.
Here it is recommended to block this update to the new Edge.
Similar articles:
Microsoft’s Chromium Edge will be distributed via update soon
Run old and new Edge in Side-by modus
Advertising
April’s Patch Tuesday brings us several, security-related, Microsoft Office updates and some small changes in UX and accessibility. In addition, Microsoft has also announced the much-needed retirement of the “legacy”, non-Chromium-based Edge Browser. The changes will come into effect at 10:00 PST. The decision to remove EdgeHTLML, by actively replacing it with Chromium, following the March end-of-support Edge announcement. At the same, Microsoft has encouraged organizations and consumers to upgrade to the latest Edge version.
April Patch Tuesday Highlights
On the 6th of April, Microsoft has pushed the KB4486672 update for Office Standard 2016, Office Professional 2016, Office Professional Plus 2016, Office Home and Business 2016, and Office Home and Student 2016.
As Askwoody’s MS-DEFCON columnists pointed out, Office 2016 was the only EOS MS product to receive an update. We would like to remind the users that Microsoft officially ended mainstream support for the 2016 business and home versions of Office on the 13th of October 2016. End of Support is scheduled for the 14th of October 2025. As expected, the vendor encourages all clients running any of the above-mentioned products to deploy the update as soon as possible.
So far, there’s just one issue associated with the KB4486672 deployment. Some users (i.e., Microsoft has yet to disclose if the issue predominantly affects home or enterprise end-users) might experience Office application stability or non-responsiveness issues. Microsoft stated that the problem lies in the registry code writing process and proposes the following fix:
- Download the KB4486672 update manually and execute the .msi pack. Alternatively, you can use Microsoft’s Update Center to automatically download and deploy the pack.
- Run Regedit.msc with administrative rights.
- Navigate to HKEY_CURRENT_USERSSoftwareMicrosoftOffice16.0General.
- Find the value EnableAdvancedRegistryHangDetection.
- Set value type to DWORD and Value data to 1. Save changes.
Note: if you are unable to locate the General key in 16.0, you will need to create one. When you’re done, define EnableAdvancedRegistryHangDetection under General by right-clicking on the right panel, highlighting new, and left-clicking on the DWORD button.
As mentioned in the intro, Patch Tuesday also delivers several UX and accessibility improvements. To name a few, as of the April roll, Microsoft fixed an issue with the zoom function that appears when a user utilizes the Microsoft Edge IE Mode on a multi-mon high DPI setup.
In addition, MS also fixed a minor HDR-related issue that made the display appear darker. Some child account-related issues were patched – users are now notified when a child account defined in the Family Safety section attains andor requests administrative privileges. Last, but not least, Microsoft also fixed an OneDrive syncing issue that caused the endpoint to stop working if the user would delete files or folders currently in use by OneDrive.
Edge’s anticipated retirement will impact most Windows 10 versions, from build 1803, released in April 2018, all the way to the 20H2 build. Microsoft’s decision to discontinue support for Microsoft Edge and replace the EdgeHTML rendering engine with the Chromium, open-source project, is a sound one and should facilitate the web development process as well as eliminating any disparities in web compatibility. Chromium updates will not impact users running Windows 7, Windows 8.0, or Windows 8.1.
Additional Security Tips
We always encourage our readers and customers to deploy every security and non-related security update in a timely manner. Here are some other things you can try in order to increase your overall security.
#1. Ensure that all Edge related updates are deployed correctly when using a private WSUS server.
To enforce the update all across your endpoint network, make sure that the new Edge version has been added to your WSUS catalog. Please refer to Microsoft’s Edge Management for additional information and instruction on how to deploy Edge with WSUS.
#2. Use legitimate means to deploy security updates.
Only download and install Windows Updates from known and legit sources like MS’s Update Center or MS’s official website. If you receive emails urging you to install critical Windows updates, please disregard and delete the email. Clicking on any of the links enclosed in such messages could lead to debilitating virus infections or even ransomware.
Heimdal™ Security recommends a safe and automatic updating and patching solution to prevent these fraudulent attempts. Patch & Asset Management is your one-stop, fully automated updating and patching toolbox that empowers you to download, install, and configure any 3rd party, MS, or updates for proprietary software.
#3. Restore points.
Wsus Edge Chromium Web
Before deploying the new updates, don’t forget to create restore points. No major issues have been reported so far, but better safe than sorry. Creating a restore point is easy and can save you from a lot of trouble if something goes wrong during an update.
Parting thoughts
Edge is dead, long live, well, Edge. April’s patching bout isn’t as ‘meaty’ as the one in March, but still crucial to your endpoint’s wellbeing. As always, stay safe, subscribe to Heimdal’s newsletter for more cybersecurity awesomeness, and shot me an email if you have any more questions.
Wsus Edge Chromium Free