Block Microsoft from running experiments in the Microsoft Edge browser
Browsers like Firefox, Chrome or Microsoft Edge come with built-in functionality to run experiments. Browser makers like Mozilla or Google may enable or disable features or changes in select browsers; this is often used to A-B test features or get early feedback on new implementations. While most users may not even notice that experiments are running in their browsers, it happened in the past that experiments caused issues. The latest case was revealed in November when administrators from around the world reported that a Chrome experiment would crash browsers in organizations worldwide. Negative side-effects of experiments are a problem for home users and business users alike, and it is often desirable to disable or block experiments from being downloaded and run. Microsoft distinguishes between controlled feature rollouts and experiments in the company's new Chromium-based Microsoft Edge web browser. Both are made available to part of the user base when they start to roll out but similarities end here. Microsoft notes: Microsoft Edge builds have features and functionality that are still in development or are experimental. Experiments are like CFR, but the size of the user group is much smaller for testing the new concept. These features are hidden by default until the feature's rolled out or the experiment's finished. Experiment flags are used to enable and disable these features. System administrators may use the "Control communication with the Experimentation and Configuration Service" on pro and Enterprise editions of Windows 7, 8.1 or 10 to prevent experiments in the browser. Here is what is needed for that: Get the latest Microsoft Edge policy file from the Microsoft Edge Insider website. It is likely that the policies will become available natively eventually when Edge is released and integrated in Windows. Extract the file (first a cab, then a zip). Open Windows > Admx. Copy the two .admx template files to C:\Windows\PolicyDefinitions\. Open the language folder that matches the system language and copy the .adml files to the corresponding language folder of C:\Windows\PolicyDefinitions\ Open Start, type gpedit.msc and hit the Enter-key to open the Group Policy Editor. Consult this Docs page on the Microsoft website for additional scenarios, e.g. when domain controllers are used. Open Computer Configuration > Administrative Templates > Microsoft Edge. Open the policy "Control communication with the Experimentation and Configuration Service" policy. Set the policy to Enabled. Set it to either "Retrieve configurations only" or "Disable communication with the Experimentation and Configuration Service". Retrieve will download configuration payloads only, disable won't download or enable them. The behavior of not configuring the policy differs depending on whether it is a managed or unmanaged device. Managed devices will download the configuration only while unmanaged devices will retrieve configurations and experiments. Source
Edge Dev CreateProcess bug
I'm using Edge Dev Version 143.0.3638.1 (Official build) dev (64-bit) downloaded from https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/3b9b41d3-7038-420a-bb07-66fe54926f0f/MicrosoftEdgeDevEnterpriseX64.msi Opening a new Edge instance by using the code: BOOL bRet = ::CreateProcess((LPCTSTR)L"C:\\Program Files (x86)\\Microsoft\\Edge Dev\\Application\\msedge.exe", (LPWSTR)L" --new-window www.bing.com", NULL, NULL, FALSE, CREATE_DEFAULT_ERROR_MODE, NULL, NULL, &si, &pi); is no longer working. I can see the process starting and then terminating quickly. It works though when using Edge Version 141.0.3537.99 (Official build) (64-bit). Is this the correct place to report & track the bug?Mica issues again (title bar + context menus)
Weird bug again - in both Stable/Dev the title bar mica effects are not working, but the dropdown & context menu (three dot settings) is. In Canary, the title bar mica effect *is* working, but the dropdown/context menu is not (solid white). I reported via feedback as well. Canary: Dev/Stable:Theme automatically changes to match Bing NTP image
Starting with the latest Edge Dev build today (139.0.3394.0) if you have your new tab page set to display the Bing wallpaper, the theme will automatically change to select a colour based on the picture without your consent. And if you attempt to reset the theme or change to another one, opening a new tab will just force it to change again. See my video below:Extension toolbar button not working (Edge Dev 132.0.2931.1)
In the latest Dev channel build, clicking on the extension button in the toolbar you see the UI is all strange and only shows one of your extensions taking up the whole window. You are also missing the bottom part of the UI. I've submitted feedback but I'm not sure if it captured a screencap of the issue. Screenshot below:
The edge dev is not opening
From the previous update of 119.0.2116.0 my microsoft edge dev is not opening. I think the problem come after this update and now I have manually updated to the latest 120.0.2165.1 with the installer and the problem is still there. I have seen the task manager the msedge process starts and run for sometime then automatically get terminated. Please Show any fix.
