Microsoft Edge - Welcome screen vs. don't show policy
Hi, We have a GPO that disables the Edge welcome screen (sets the SOFTWARE\Policies\Microsoft\Edge key's HideFirstRunExperience variable to 1). On some of our PC's when the user try to run Edge, they get a blank page with invalidurl error. This white page can not be closed, only way to dismiss if you stop edge processes with the taskmanager. If you set the registry value to 0, then it can reach the welcome screen and you have to do the first steps. This policy should disable the welcome screen and not just hrowing an error. how could we avoid this screen to appear? Is there any setting that let Edge think it was already started and omits this screen completely? Why did this bug appeared in the first place? This policy was working for years now, and only show this bug randomly. Edge - stable, latest version; Windows10 22H2;
PersonalizationReportingEnabled is being ignored
The https://learn.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#personalizationreportingenabled option ("Allow personalization of ads, Microsoft Edge, search, news and other Microsoft services by sending browsing history, favorites and collections, usage and other browsing data to Microsoft") is being ignored. When using the Group Policy option to set it to Disabled, it doesn't show as managed policy in edge://policy When using Group Policy to set the Registry value (again to disable it), it appears as a managed policy, but seems to be ignored on first-run. We use Edge for our exam environment. As users have no profile on logon, users are being asked to confirm they agree to personalisation before they can continue.My IT Support Cannot Provide a ProxyMode Exception
My environment has Chrome's and Edge's ProxySettings locked down to ProxyMode:direct. This prevents me from running a local (system) proxy, specifically Fiddler, so that I can check and debug the SharePoint Framework (SPFx) solutions I am developing. I have passed on all the documentation I have found (see below) and the support staff have been unable to provide me with an exception so that my setting is ProxyMode:system. Is this a limitation with how policies are managed for Chromium or is there additional guidance I can provide to my IT support personnel? Edge Policy Configuration: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies Proxy Configuration: https://docs.microsoft.com/en-us/deployedge/edge-learnmore-cmdline-options-proxy-settings Chrome Policy Configuration: https://support.google.com/chrome/a/answer/187202?hl=en Proxy Configuration: https://developer.chrome.com/extensions/proxy
WebAppInstallForceList not adding shortcuts to the desktop
I'm trying to test deploying a PWA using the WebAppInstallForceList policy on Edge 88 with the following: [{ "create_desktop_shortcut": true, "default_launch_container": "window", "url": "https://service.example.com/"}] The problem is that the PWA gets installed but its not creating a desktop shortcut. Manually trying to pin the desktop shortcut at edge://apps/ also does nothing. When the WebAppInstallForceList policy is disabled and the PWA is installed manually I can pin the desktop shortcut at edge://apps/ just fine. How would I go about troubleshooting this?NewTabPageManagedQuickLinks (Group Policy)
I just discovered that NewTabPageManagedQuickLinks has a max value of 3. Meaning if I try to pin more than 3 website it errors. Any reason why? This isn't mentioned anywhere in the documentation. https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#newtabpagemanagedquicklinks Also, as a suggestion. I think we should be allowed to configure an XML file path instead of having the use a single line format. Having to use single line is a little annoying { "url": "https://www.contoso.com", "title": "Contoso Portal", "pinned": true }, { "url": "https://www.office.com/", "pinned": true, "title": "Office" } ] Compared to an XML file <key>NewTabPageManagedQuickLinks</key> <array> <dict> <key>pinned</key> <true/> <key>title</key> <string>Contoso Portal</string> <key>url</key> <string>https://contoso.com</string> </dict> <dict> <key>pinned</key> <true/> <key>title</key> <string>Office</string> <key>url</key> <string>https://www.office.com</string> </dict> </array>Whats the point of downloading different policy files when they are applied to all channels of Edge?
I have Edge 86 stable and Edge 87 Dev installed on latest Windows 10. Downloaded policy files for Edge Dev 87 using configurations shown above, installed it, set a couple of policies from Windows group policy and then I see that they are being applied not only to Edge dev 87 but also to Edge stable 86! Why is this happening exactly? am I missing something that would let me target a specific Edge channel/version using group policy configurations? From my (non-Edge-developer) standpoint, when this website https://www.microsoft.com/en-us/edge/business/download offers to download different group policy files for each version/channel, it's expected for those policies to only be applied to that specific Edge channel, not to every installed Edge instance.Tutorial: How to run Legacy and Chromium-based Edge simultaneously side by side Without Group Policy
1. Uninstall Chromium Edge either from Control panel or from Windows 10 settings => Apps 2. Go to Registry Editor by typing "regedit" in Windows 10 search 3. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft​ OR paste this in the address bar area of Registry editor Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft​ 4. Right-click on "Microsoft" and create a new key And name it "EdgeUpdate" (without quotes) 5. Then right-click on "EdgeUpdate", go to New and create a new DWord 32-bit and call it "Allowsxs" (without quotes) Allowsxs 6. Set its value to 1 7. Exit Registry Editor 8. now go to www.microsoft.com/Edge to download Edge stable again. install it and after that you will be able to access both Legacy and new Edge from start menu or Windows 10 search. Source: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-update-policies#allowsxs This tutorial is for using only Registry editor, there is also another method to do this which is through Group Policy https://docs.microsoft.com/en-au/deployedge/microsoft-edge-sysupdate-access-old-edge#how-to-enable-a-side-by-side-experience-with-both-versions-of-microsoft-edge for that you also will need the policy files which you can get from here: https://www.microsoft.com/en-us/edge/business/downloadEdge as default browser GPO error
In the current Stable build 81 when you install Edge and have the Edge Group Policy set to set Edge as the default browser, the error shown below shows up on the pc. As far as i could find online this happens if Edge doesn't change the default browser using the correct API in Windows 10 and corrupts the settings.Request: "Offline" Keep Favorite in Sync IE11 <-> Edge (Chromium)
The 'Legacy' MS Edge had a Group Policy that allowed an "offline" browser favorite Sync on a local system between IE and Edge: Windows Components/Microsoft Edge "Keep favorites in sync between Internet Explorer and Microsoft Edge" For Enterprises that aren't leveraging O365 and account Sync (or for whatever reason can't) this would make for a smooth sailing scenario. Any possibility for implementation?
