Categoria,Tags Geral / Produto,"Microsoft Edge, Edge Linux, Copilot, Barra Lateral" Sistema Operacional,"Zorin OS, Linux, Ubuntu, Debian" Assunto / Bug,"Bug, HubApps, Solução, Workaround, Correção" Versão (Opcional),"Zorin OS 17, Edge Stable"

1 Topic

[Wayland] PWAs no longer appear as separate app windows — all group under main Edge icon
Hi, Since around 2025-09-07 to 2025-09-10, I’ve noticed that on GNOME (Wayland) all installed PWAs (even across different profiles) now appear grouped under the main Edge browser icon in the GNOME Shell dash/taskbar. Previously, each PWA would open in its own window group with its own icon. This is still the behavior in Chromium/Brave/Chrome, and can be restored there by editing the PWA’s .desktop file to set: StartupWMClass=<same value as Icon> However, Edge now seems to ignore StartupWMClass completely on Wayland, breaking workspace separation and making task switching hard. Environment: Ubuntu 25.04 GNOME 48.0 / Mutter (Wayland) Kernel 6.14.0-29 Intel Iris Xe GPU Edge (latest stable, observed post 2025-09-13) Repro steps: Install any PWA (e.g. Outlook, Teams, Spotify) from Edge Launch it (from any profile) Observe that it appears grouped under the main Edge browser icon Expected: PWA shows under its own icon and window group like in Chromium-based browsers Actual: All PWAs are bundled into the main Edge window group Editing StartupWMClass in the .desktop file no longer helps This regression makes PWAs much harder to manage on Wayland. Please route to the Linux/Wayland team if possible. Thanks!
AZia_atsgnet
Nov 24, 2025 Place Discussions
1KViews
10likes
16Comments
MS Edge - Sidebar and copilot not working on Linux Ubuntu v24 LTS
Sidebar not syncing or accepting new app additions (+). Copilot button is dead/inactive. Sidebar settings are well configured. Using the latest version of the Ubuntu OS and MS Edge. Functionality appears to be absent as product was released without full functionality....Lame!
bxhorn
Nov 22, 2025 Place Discussions
24KViews
41likes
57Comments
Can't see Copilot icon anymore!
Hey everyone. Today, after updating Microsoft Edge in my Windows 11, I can't see Copilot icon on top right of the window anymore (even in Edge Dev and Edge Can). Also, I can't access Bing Chat over sidebar shortcut that I've created. Why?? Actually, the last version of Edge was greatly working and didn't have any problems. I could completely work with Copilot, even in PDF files; but not anymore. Well, what should I do??😑😭 Thanks for your support.
NouriehFerdosian
Nov 09, 2025 Place Discussions
25KViews
11likes
25Comments
PWA shortcuts don't keep asociated with window - Linux
I recently upgraded to version140.0.3485.14 (Official build) beta (64-bit) and noticed that my PWA, even if they open correctly in a independent window, don't show the "running window counter" on the taskbar. So, for example, if a open Outlook, the window open and loads the app, but if a I click the icon again, it opens another window, wich is a little annoying. I tried removing the PWA from Edge, rebooting, and installing again, but didn't work. Because the only change I made is updating Edge, I think is related to this build. (too lazy to go back or install the stable release)
feligato
Nov 03, 2025 Place Discussions
873Views
9likes
8Comments
Have Secure Network (VPN) and AI Mode been removed in Edge 141.0.3537.85?
I recently updated to Edge version 141.0.3537.85 and noticed that two features I regularly use seem to have disappeared: The Secure Network (VPN) toggle is no longer visible under edge://settings/privacy/security, and I can't find any related flags. The AI assistant on the default page (Copilot or AI mode) is also missing. I'm not sure if this is a bug, a rollout change, or something specific to my setup. I haven't found other reports online, so I'm wondering if anyone else is experiencing this. These features were important to my workflow, especially the VPN and proxy support. If they've been intentionally removed, I’d appreciate some clarification or changelog reference. If it's a bug, I hope it's being tracked. Any insights or confirmations from other users or the Edge team would be helpful.
HiCharlie
Oct 19, 2025 Place Discussions
54Views
0likes
0Comments
Cannot enable copilot for edge sidebar

Mohamed_Almutawa
Aug 22, 2025 Place Enterprise
12KViews
1like
5Comments
Please Provide Option to Disable "Ask Copilot" in Address Bar
I use Kagi as my default search engine. Recently, I've noticed that if the search string reaches a certain length, the default search option changes from Kagi to "Ask Copilot." See the image below. This is driving me insane! I don't necessarily mind the "Ask Copilot" feature but having it automatically selected when the search string reaches a certain length is unbearable. Please, at least provide an option to turn this behavior off. This is so annoying that I have had to stop searching from the address bar and navigate to the Kagi website for each search.
dblagent007
Jul 15, 2025 Place Discussions
353Views
6likes
4Comments
Copilot or Discover browser extension not working as expected for managed Edge browser
If your organization manages the MS Edge browser or has decided to limit the availability of Copilot (previously known as Discover in Edge) until administrators have a handle on its capabilities and risks, then this post may be helpful. You will find in the following article -- https://learn.microsoft.com/en-us/copilot/edge#summarization-by--in-edge -- Microsoft suggests for Admins who want to manage Copilot in Edge, they can "use multiple group policy settings to manage the behavior of the Copilot in Edge sidebar:" # I have found it very strange, especially when referencing brand new tools like Copilot, that Microsoft documentation suggests admins are still using, or should use group policy as opposed to more modern management tools like Intune # The article suggests the below "group policy settings" can be used to manage Copilot behavior in Edge: To allow or block Copilot in Edge from using browsing context, use the https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies policy. This prevents Copilot from using webpage or PDF content from being used to respond to prompts. To disable Copilot in Edge entirely, use the https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies policy. Blocking Copilot in Edge automatically blocks all Edge sidebar apps from being enabled. Now according to these instructions, you would use the https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies policy to allow Copilot in Edge to use browsing context and seemingly (since https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies is used to disable Copilot) you would set https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies to enabled in order to force Copilot to appear and be available for your users. To an admin still using group policy to set these maybe everything works fine -- In previous testing I have hacked my registry to create the above keys and can't remember the results, but it was kind of a pointless test since I personally use Intune to manage our Edge browser. If you're like me and use Intune to manage Edge's browser configuration at your organization, then seeing the keys above may prompt you to head to the Intune settings catalog to look for equivalent settings that you can use to set similar policy. Next, I'll share my findings from diving into how I might use something available in the Intune settings catalog. My findings are as follows: Show Copilot -- you will find this setting if you nav down through edge://settings/sidebar. With no settings configured related to Copilot you will see this in the off state and when you hover the briefcase icon where you would usually see "this setting is managed by your organization," you will just see a blank textbox. Right out of the gate this is a weird behavior and the only thing I have been able to chalk it up to so far is a bug -- my thinking is if your browser is managed by the organization then by default the Show Copilot setting will be in the off state. Ok, so now how do we actually get this thing on if we are ready for our users to use it? Discover feature In Microsoft Edge -- this is a setting you can find in the Intune settings catalog. Previously Copilot in Edge was called Bing Discover and it had a "B" icon. If you configure this setting today and set it to enabled you might expect it to display Discover or Copilot, however, when you check the edge://policy report you will find that EdgeDiscoverEnabled (as it shows up on the report) actually errors out and is described as an "unknown policy," and there will be no effect to the browser or to the Show Copilot setting I discussed above. https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies -- now back to the HubsSidebarEnabled setting referenced in the linked Microsoft documentation. Supposedly you would use this setting to "disable Copilot in Edge entirely." Now you can find a setting called Show Hubs Sidebar in the Intune settings catalog and you can set it to enabled. When you nav to the edge://policy report you will even see it successfully configured and reporting in as OK. However, in my testing I have not seen this have any effect on the Always show sidebar setting found at edge://settings/sidebar, and I have not seen this have any effect on the Show Copilot setting found at edge://settings/sidebar when you drill into the Copilot settings. So, my only conclusion here is that the HubsSidebarEnabled from the Intune settings catalog isn't ready for showtime. https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies -- This is a setting you can find in the Intune settings catalog called Enable Discover access to page contents for AAD profiles. This setting will successfully configure and report back as OK in edge://policy report, however, I have not tested any further and can't tell you if it is actually doing what it intends to since I have not successfully configured Copilot using the other Intune settings. The only success I have found so far in all of this Copilot, Discover and Sidebar research are the following two extension IDs that can be added to your force install extension list -- and as a result the Copilot browser extension should appear. If you are new to using Intune to manage browser policy and aren't sure what I mean by the 'force install extension list,' drop a comment and I'll be happy to add some detail about that. Extension IDs: nkbndigcebkoaejohleckhekfmcecfja ofefcgjbeghpigppfmkologfjadafddi I found these extension IDs by using ctrl + f on the edge://sidebar-internals page looking for results related to the search term "Discover." At the moment this seems like the best way to enable and test Copilot until the Intune settings currently available begin working as they are described. This is not meant to criticize the speed at which Microsoft has made settings available or set them up to work perfectly, but to prompt discussion and help others who might be going in circles trying to figure out if they're configuring something incorrectly. TL;DR There are currently settings in the Intune settings catalog that don't seem to work as expected if you are trying to enable/disable Copilot for a managed instance of Edge at your organization. As a workaround there are a couple extension IDs that can be added to your ForceInstallExtension list to help display Copilot in the Edge sidebar. I've attached some screenshots related to different things referenced in this post.
Solved
pjv4tx
Jun 23, 2025 Place Discussions
13KViews
3likes
6Comments
Copilot does not open in new tabs on Canary Channel
I installed the canary version of Microsoft Edge this week to test the Copilot functionality of opening in new tabs. After working fine the first time, it stopped working unexpectedly. Now when I open a new tab, it loads the MSN news page. Does anyone know what happened? Thanks.
Marcelo_Strippoli
May 23, 2025 Place Discussions
123Views
0likes
2Comments
Edge Linux: Collections and Workspaces
Hey y'all, I use Edge Dev on both Linux (at home) and Windows (at work). I started using Collections recently, and I was upset to find it doesn't work on Edge Linux (yes, my packages are up to date). Although I haven't tried Workspaces yet, it's not working either on Linux. Even if you enable it, it doesn't show up. I can see that the tab expands, but the button doesn't appear. With Collections, enabling has no effect at all. Is this a known bug, or it just doesn't work on Edge Linux yet? Ubuntu 22.04.2 LTS x86_64. Version 115.0.1851.0 (Official build) dev (64-bit).
farchettiensis
May 13, 2025 Place Discussions
2.6KViews
3likes
5Comments