In-place build upgrade failure and workaround
I have noticed that, since the first build the new Microsoft Edge was bundled with Windows Server vNext, I could not upgrade from one weekly build to the next without re-installing from scratch. I could upgrade from an older build that did not include Edge to a newer one that did, but not from one with Edge to anther with Edge. I tought that Edge was the culprit, but I could not uninstall it through the regular means, for I have wound a guide to forcly uninstall it via command line. It was uninstalled, but Windows upgrade to the new build failed again. Then, I tought that enabling Network Sharing was the culprit. So, did a fresh install once again, but kept it disabled, as out of the box. The latest build came, it failed in-place upgrade, but at an earlier stage. Yet, Edge was updated after the fresh installation a few days ago and it was removable through Control Panel or Settings. So I did uninstall it, then tried an in-place upgrade and it worked. It had reinstalled Edge. So, I guess the update/upgrade system for the Chromium Edge between Windows builds (that upgrade like previous redstones, through a Windows re-install mechanism with documents, settings and programs being kept) it is not fully developed. Edge updates on a different way then the OS itself, in a way enherited from the Chromium browser, it is not fully integrated into Windows yet, altough I have looked via 7zip and the Windows Install.wim file contains it. Probably, due to that, especially when the installed version of the Chromium Edge browser is updated beyong what is in the install.wim, issues can appear. I guess that, if the update/upgrade mechanism for Edge in Windows it is not solved, that Edge should not be bundled with Windows until that, while still being available for users via the Microsoft Edge msi installer for Enterprise. A workaround, so far, seems to be uninstalling it before an in-place build upgrade..