If that's true why was January 15th all over Microsoft's site for the beginning of the staged automatic roll out, and why are there posts of issues with the update?
The news at the time certainly made it look like if you did a manual update that the new Edge would be offered.
It is in fact on WSUS. Still looks like an evolving product at this stage for the purpose of updating. It reports for example 79.0.309.71 as 79.0.309.65. But this is largely the case with various .NET Framework versions which are not reported correctly to WSUS.
Edge DevTools Are Now Available in 11 Languages. Open Microsoft Edge. Type edge://flags into the address bar. Find the flag Enable localized Developer Tools. Set it to Enabled.
So guys, any reason why some extensions on the Edge Store are outdated compared to their Chrome counterpart? For example, uBlock Origin version for Edge is 1.23.0, while on Chrome its 1.24.2
I have been able to successfully integrate Microsoft Edge Chromium in an offline WIM. Once I add that feature to my Optimize-Offline project on Github, I will write an independent PowerShell script and post it here.
I know that, I only mentioned WSUS to show that there are intentions from Microsoft to eventually provide updates via WU. In general, WSUS tends to mirror WU, sometimes in advance, at other times later, although this is not 100% the case.
Am I the only one who is annoyed all to Hell because the installer copies it's installer files over and over and over all over my drive? The final install folder is about 3 times what it should be because of left over "installers" of the full package. Does Chrome and all the other Chromium based browsers do that too? The ~70 MB installer bloats itself into 10+ times that by the time it's installed FFS.