Forum Discussion
the New Microsoft Edge is not available in Dev build 21286
Now I know the reason for this, it's because Build 21286 is still using version 2004 code base.
Windows 10 only started having the new Edge preinstalled since version 20H2 (which is only in stable and release preview rings), so once the Dev channel of Windows insider starts receiving builds from a newer code base (20H2 and above) then they will have the new Edge preinstalled as well.
Dev/Fast ring version will most likely remain that way until just before release of next stable release (21H1), few months from now.
https://techcommunity.microsoft.com/t5/windows-insider-program/windows-10-insider-fast-ring-build-19002-but-the-settings-page/m-p/918646
HotCakeX wrote:Now I know the reason for this, it's because Build 21286 is still using version 2004 code base.
No it's not
the 2004 tag only get updated when the build is close to release and no longer evaluation (i.e. don't expire)
all insider preview builds after 19041 still have v2004 tag
version 20H2 didn't got new Edge preinstalled, they simply installed it via Enablement Package during Audit/sysprep installation, and then captured new install.wim image
that's why latest v20H2 ESDs/ISOs have bigger sizes, because the new Edge bloat alone adds > 560 MB
- HotCakeXJan 11, 2021MVPThanks, those are great info, so when do you think that Edge legacy will be replaced by the new Edge in insider channels?
And did you find out about the process by which they added new Edge to 20h2 on your own? Because that's interesting- abbodi1406Jan 12, 2021Steel Contributor
HotCakeX I don't know when legacy Edge wll be eliminated
Yes, it's not hard to inspect install.wim with 7-zip
this is the only way to install external Win32 program on Windows, you cannot integrate it offline, Audit/Sysprep is the "official" wayyou could see report likes this because of that, they did poor job in cleaning those syspreped install.wim
https://www.tenforums.com/drivers-hardware/166940-ghost-devices-20h2-device-manager.html