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!
Video Super Resolution Missing Options in Setting
Enhance videos in Microsoft Edge (Flag: #edge-video-super-resolution) is missing critical options in setting, making it impossible to function properly. In Version 136.0.3240.29 (Official build) beta (64-bit), as well as the previous beta build, it is missing the option to choose from three methods of video enhancement, as shown in screenshot. Here is the setting from latest beta build: This is how it is supposed to look: Thus, beta build defaults to Microsoft Super Resolution and I can't find a way to use graphics driver enhancement like RTX Super Resolution, which is critical to my experience. Also, HDR is no longer supported when video enhancement is enabled, which I believe is a limitation of Microsoft Super Resolution.
100% CPU usage since Edge 105 on Mac M1 ?
After browsing for a little while, CPU usage increases to 100%. When I checked in Task Manager, it's not related to any specific tab but the "browser" process. Closed all tabs doesn't solve it. I temporarily switched to 106 (dev) and the issue is gone for awhile but then resurfaces
[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!I like EDGE and use it since alpha ,a huge PERFORMANCE BUG(since 118 ,the bug can't avoid by flag)
This long thread will take your some time to read. A long-term BUG or design problem regarding the integration of EDGE and WINDOWS Explorer (EXPLORER.EXE) ALT+TAB view. This bug is very unbearable for me, and nearly 30 years of programming experience generally makes me try to solve the problem myself, but in the end, there is nothing I can do, and I decided to write my findings here. Recap: 1. This property integrates some tabs of EDGE with windows explorer in ALT+TAB to provide faster task switching 2. I turned off this function in the settings, and the corresponding registry key value is: 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\MultiTaskingAltTabFilter' = 3 Problem Description: 1. In daily life, I am used to keeping 600-700 TABs in EDGE. With the latest version of the tab sleep function, EDGE works well, but EXPLORER will start to crash as my TAB increases. 2. After observation, it is known that in this case, EXPLORER's GDI OBJECT and HANDER will grow abnormally, so as to break the default limit of 10000, and then crash. After the crash, HANDER will increase slowly, and this behavior will continue to loop my thoughts: 1. In my programmer's thinking mode for many years, when you turn off this function, EDGE should not share the content of TAB with EXPLORER, occupying system resources for no reason, but should cut off the information of this API. He only needs to tell EXPLORER How many windows you have, the title content of each WINDOW is enough. 2. Before the EDGE browser added ALT+TAB to switch tabs, I even reached 1000 tabs. The system runs smoothly without any experience problems, and the EXPLORER will not crash. My intuition tells me that this function is the cause 3.The registry key 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\MultiTaskingAltTabFilter' = 3 just hides these TABs, but in fact these TAB views still occupy full system resources (handle resources in EXPLORER), This kind of deception can't really solve the performance problem of the system. The real shutdown of this problem should be made by the EDGE development team and the WINDOWS development team to make some kind of switch/registry/group policy, so that EXPLORER completely ignores the details of the EDGE tab content in certain cases . I made a crashdump and some picture to help your find the problem all of @Edgedev. Wish you can fix this problem ASAP , thank you !
Critical Pen Hover & Stray Ink Issue on New Surface Pro 11 for Business with Slim Pen 2
Hello Microsoft Community and Support Staff, I am writing to report a critical and seemingly widespread issue with the pen input on the brand-new Surface Pro for Business, 13-inch (Intel model, often called Surface Pro 11 "Luna Lake"). The Core Problem: Pen Draws Without Touching the Screen When using the Surface Slim Pen 2, the device begins to register ink input while the pen is still hovering a few millimeters above the screen. It does not require any physical contact or pressure. This "hover-inking" makes handwriting completely unusable. As I write, any time I lift the pen to start a new letter or stroke, the pen continues to draw a line as it moves through the air to its next position. This results in messy, connected handwriting with unwanted "tails," completely defeating the purpose of having a premium inking device. This is Not a Defective Unit - It's a Replicable Problem Initially, I thought I had a faulty device. However, to isolate the issue, I have performed extensive testing: I have personally tested this on [3] brand-new Surface Pro 11 (Intel) devices. I have used [4] different Slim Pen 2s. The exact same hover-inking problem occurred on every single combination of device and pen. Furthermore, I have already performed all standard troubleshooting steps, including: Clean OS installation via Surface Recovery Image. Ensuring all Windows, driver, and firmware updates are installed. Running the Surface Diagnostic Toolkit (which reported no errors). However, the same issue continues to occur even after trying these methods. Additionally, it has been reported that the issue also appears on the latest Surface Pro 12-inch model with the Snapdragon X Plus, just like on the Surface Pro 11 that uses the Qualcomm Snapdragon X Elite instead of Intel’s Lunar Lake. (I do not own any Snapdragon devices myself. If you own a Snapdragon device and are experiencing the same issue, please share your feedback.)" Video Evidence: I have recorded a clear video demonstrating the problem. It shows the pen drawing while hovering on the Surface Pro 11 and makes unwanted tails on handwriting letters. Video Link: https://youtube.com/playlist?list=PLG_7BXFA-cL4evqe0RmRz--iFjDC1HVgT&si=EmEypaAqSyRozr67 Questions for Microsoft: Is this a known issue with the new Surface Pro 11 (Intel) model's firmware or drivers? What are the official steps to escalate this issue directly to the Surface engineering team for a fix? This is a major flaw in a flagship product that severely impacts its core functionality. I have submitted a formal bug report through the Feedback Hub, which can be found here: Feedback Hub Link: https://aka.ms/AAxzh27 I urge the Microsoft team to investigate this with high priority and release a firmware or software update to recalibrate the pen's Initial Activation Force (IAF). Thank you for your attention to this serious matter.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:
