

Yet, the users will be stuck with Edge Chromium 84. This is installer will bomb-out with “there is a newer version already installed”. The issue at hand though is that Edge Chromium is a moving target, so including even the latest version today in whatever upgrade process you have – will most likely in a months time have an older version than what you have installed on your endpoint. If you deploy Edge Chromium later version (like 87? 88?) to your 1909/2004 devices – and then upgrade to Windows 10 20H2, you will effectively downgrade Edge Chromium to 84.Īs far as I can understand – the details, the workarounds and apparently a promise that this will be better is all published on Borncity. Specifically – Edge Chromium v84 (something something)
