In-place build upgrade failure and workaround

Elden_Christensen 

Thank you for the reply. In my opinion there are there possible solutions to this issue, that I assume is, most likely, present not just in Windows Server vNext LTSC, but also on standard Windows 10 Insider builds.

1) Chromium Edge is not bundled with Windows Server, but it comes later through manual install from the Enterprise msi installer or via Windows Update. I guess this is the easiest solution;

2) Chromium Edge is bundled with Windows Server, but not part of install.wim and it gets installed on the later stages of the Windows install process. This would make Edge a program installed on Windows like other non-Windows programs that are installed in Windows and, on in-place upgrade from build to build, the Windows upgrade function shall treat it like any other installed program and migrate it (like Microsoft Office or Microsoft SQL);

3) Chromium Edge is deeply bundled with Windows 10 and Windows Server and it gets updated only through Windows Update, like a Windows component. In case of an in-place upgrade from build to build, it should be replaced with the rest of the OS (kernel, Windows Explorer etc). This last solution is, probably, the hardest and, I assume, the developers know it.