# EdgeHTML Support

**URL:** <https://meta.discourse.org/t/edgehtml-support/138601>\
**Category:** Development\
**Created:** [January 14, 2020, 8:23pm UTC](https://meta.discourse.org/t/edgehtml-support/138601 "2020-01-14T20:23:37Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [January 14, 2020, 8:30pm UTC](https://meta.discourse.org/t/edgehtml-support/138601/19 "2020-01-14T20:30:09Z")

</div>

Microsoft have updated their documentation on this, to clarify the auto-update scenarios

[https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-blocker-toolkit](https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-blocker-toolkit)

The update will be automatically applied to home and unmanaged business editions. It will be optional on managed business and enterprise systems. I guess that lines up with most windows updates 🤷‍♂️

We will have to see what usage statistics look like in a few months.

> [@](#):
>
> - Organizations with updates managed through Windows Update for Business (WUfB) will not automatically receive this update and do not need to deploy the blocker toolkit.
> 
> - Organizations with environments managed with an update management solution such as Windows Server Update Services (WSUS) or System Center Configuration Manager (SCCM) do not have to deploy the Blocker Toolkit. They can use those products to fully manage deployment of updates released through Windows Update and Microsoft Update, including Microsoft Edge (Chromium-based), within their environment.
> 
> - This update is a stand-alone update (not part of the monthly cumulative update) to give Enterprise customers flexibility and maximum control over deploying this update.

---

_[View the full topic](https://meta.discourse.org/t/edgehtml-support/138601)._
