And then it comes to the described scenario that after the upgrade the older Edge 84.0 instead of the actually previously existing Edge version 86.0.xxxx lands on the machine. Microsoft does not seem to provide daily updated installation images as feature updates on their update servers.

It's already clear that a feature update will take the content of the respective installation image and set an integrated edge to an older version.

And the WSUS doesn't help either… And a downgrade lock I could not (yet) find? It does a downgrade so to speak! You have to manually reinstall the MSI with the 86.0 version again, because the GPO can't do that by itself. Both EDGE versions in the program directory, but only 84.0 available. If I do the Windows 10 update to 20H2 via WSUS now, the update will iron the Edge 84.0 over it. Latest version 86.0.xxx on 19 is distributed and up everywhere, updating via WSUS. I am distributing the new Edge via MSI in the company. He told me his experience when upgrading to Windows 10 20H2 from 1809 or 190x: German blog reader CJ drew my attention the days in this comment to a problem when upgrading to Windows 10 20H2. Microsoft Edge downgrade during the upgrade With the first mentioned variant of a complete upgrade, the old operating system is replaced by the new variant from the installation image.

When upgrading from Windto the 20H2, only a several hundred KByte Enablement Update is needed to unlock the features of the new Windows 10 20H2.

When upgrading from older Windows 10 versions, the multi-gigabyte feature update is rolled out via WSUS and installed on the clients.

For Windows 10 20H2 (October 2020 Update), there are two options: Administrators can upgrade Windows 10 clients to newer builds via Windows Server Update Services (WSUS).

Reinstalling microsoft edge