I have those policies working on an Active Directory domain and they work on all supported OS, or at least those tested by me and this is not only Windows 10, but Windows 7 64-bit, Windows 2012 R2, Windows Server 2019, Windows 10 1809 LTSC. The Homepage and NewTab policies do not apply or apply only partially on standalone/workgroup computers and I think this is documented behaviour. I still have to test the search policies on standalone. Other policy that seems to work somehow but does not show in the GUI correctly is "Set application locale". This one works in full only by combining it with some manual tweaking, which defeats the purpose of having a policy. Example: Set application locale to en-AU. In the GUI, en-GB is shown, but not en-AU, which strictly speaking is almost correct, although there are non-essential differences in showing the date for the 2 variations of the English language. If en-AU is added manually in the GUI, then the policy is shown as enforced as expected for en-AU, but the order which should be en-AU to the top is not shown. There is a file which can be seen with a text editor like Notepad++ "%localappdata%\Microsoft\Edge\User Data\Local State" where the settings can be seen as applying, regardless of the GUI but needs more testing, potentially for other localisations. This behaviour seems to be known from Chrome and is likely not specific to Edge Chromium. Note: There are 2 different aspects when it comes to browser localisation which need clarification. 1. User interface language. 2. Accept-Language request headers sent by the browser.
After a few days tinkering with it, I have to say, not bad, but basically Brave is a better version of the same basic thing. Same annoyances, but less of them (import works for example). It's kind of like Microsoft put out a 'Volkswagon' to compete with a bunch of 'Porches'.
Curious if anyone can confirm increased ping in Edge, at least in speed tests. For some reason, in both the old Edge and the Chromium based on, the ping is always around 8, while in Vivaldi it's 1-2. Pretty much same extensions, just one tab open, similar test conditions, and it's not just a fluke, it's been consistent over months now. Wonder why, and also why it's true for both Edge variants.
Tired of fighting the constant update error. The same as fighting in windmills. That is updated without problems, then it gives an error.
Installed in the default folder from the Microsoft Edge download page. OS 2004 (20H1) x64 build 19041.84 en-us.
To stop Auto Updates: 1. There are 3 update services, disable the two named something like (from memory) EdgeUpdate, and EdgeUpdatem. I removed them completely via command: "sc delete edgeupdate" and "sc delete edgeupdatem". 2. Disable or modify or *export backup then delete* the two scheduled tasks in Task Scheduler/Task Scheduler Library. MicrosoftEdgeUpdateTaskMachineCore and MicrosoftEdgeUpdateTaskMachineUA Manual update checks still worked. Probably by modifying those two scheduled tasks? Change the schedule/trigger? I forgot the exact defaults but it was like every logon, and every launch and every 5 minutes or some crazy amount.
I noticed something strange,,, the volume on Edge chromium is much lower than on any other application and lower than the regular Edge. I checked volume mixer and it is maxed out. Can someone else compare same video, lets say on youtube, on both Edge and Edge Chromium and tell me if they also hear a difference in volume? Thanks
Please, can someone explain what are advantages to install Microsoft Edge (Update)? It looks like Chrome but occupies x3-x4 hard disk space than Chrome and it's hungrier of CPU cycle. Really, until now i can't understand any enthusiasm for it, but i'd like proved me wrong