Discussion in 'Windows 10' started by SAM-R, Mar 18, 2019.
You need to login to view this posts content.
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.
There is nothing to update, this is self standing web browser and have absolutely nothing to do with the old one. It's Chromium browser with Microsoft design and where is added Microsoft junk.
It consists of two basic parts - the browser and the updater. These are also two separate programs. And that is all.
This has been the case since the first Chrome browser came out, it must have been on 2012 or something similar.
This Chrome based browser is not part of Windows. At least not yet.
I don't know
did you installed and deployed the group policies?
No, I make the modifications to the registry, and it works for the other settings (edge://policy/)
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
You have the wrong information and you are asking the very wrong place.
Current uBlock Orign is 1.24.4 not 1.24.2.
It's listed in the official blog post that Microsoft Edge will be rolling out to the public (Release Preview first, and then it will expand to a broader set of rings & audiences) in several weeks/months time.
We're talking about the consumer version of Windows Update (WU), not the corporate version of Windows Update which is WSUS.
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.
You are right. You're probably the only one who has this problem.
Another thing, you are also right that all Chromium based browsers produce a lot of junk, but cannot forgot, the same does Firefox.
If Crome-based browsers change the location of files during installation, then the Firefox will copy all files to another place. So Firefox produces even more junk.
We have nothing to do here, that is the noble idea of a smart engineer.
Each Microsoft Edge update produces slightly less than 750MB of junk files, Google Chrome produces about 650MB and Firefox about 450MB.
If You said that the installer is ~70MB, then you were pretty much wrong. Typical Microsoft Edge installer is about 295MB + updater.
~70MB is only deeply compressed .zip packgage what even doesn't contain updater.