New Copilot for Windows 11 includes a full Microsoft Edge package, uses more RAM
April 5, 2026
A new iteration of Copilot is making its way to Windows 11, marking a significant shift from native code (WinUI) to web components. This transition, anticipated based on prior analyses, comes with the unexpected inclusion of a fully-fledged version of Microsoft Edge. While it remains unclear whether Microsoft is falling behind in the AI landscape, it is evident that the company has struggled to establish a cohesive Copilot experience for Windows, frequently altering its approach every few months.
The latest update replaces the previous native app, which itself had succeeded the WebView version, which in turn had replaced the Progressive Web App (PWA), and so forth. This evolution has seen Copilot transition from a sidebar feature to its current form.
For those yet to experience the new Copilot, a visit to the Microsoft Store is in order. A search for “Copilot” will reveal a new listing titled “Microsoft Copilot,” complete with a download button—even if the application is already installed on your device. Clicking the Download button results in an almost instantaneous completion, as it does not download the Copilot app directly but rather an installer akin to the Microsoft Edge installer.
Copilot using Edge installer
The Store indicates that further action is required in another window, highlighting that the Copilot download process is no longer managed directly through the Microsoft Store, a pattern reminiscent of Microsoft Teams. Once the update is complete, the previous native Copilot app, built on the WinUI framework, vanishes from the Start menu and other locations, making way for the new version.
Upon launching the new Copilot, users will notice a striking resemblance to the web version (web.copilot.com). The experience is notably smoother and almost feels native; however, it comes with certain drawbacks, particularly concerning high RAM usage, which raises concerns about Microsoft’s ongoing efforts to enhance Windows performance.
Copilot’s new version is a resource hog, a hybrid version that ships with its own Edge browser
In testing conducted by Windows Latest, it was observed that Copilot consumes up to 500MB of RAM in the background, escalating to nearly 1GB during user interaction. In contrast, the previous native Copilot maintained a RAM usage of less than 100MB.
Copilot in Task Manager
This prompted further investigation into the differences of the new “web-based” Copilot app, revealing it to be a hybrid web application that operates with a rebranded and forked instance of Edge within a WebView2 container. The installation folder for Copilot contains a directory labeled 146.0.3856.97, indicating a complete Microsoft Edge installation, which occupies approximately 850 MB. This folder houses all necessary Edge binaries, including msedge.exe and various supporting files.
Notably, the msedge.dll file within the Copilot app package is 315 MB, confirming the presence of a full Chromium browser engine. If this were a standard WebView2 or PWA, it would have utilized the existing Edge integration in Windows 11 rather than shipping with its own version of Edge.
Additionally, Edge subsystems are embedded within Copilot’s package, encompassing Browser Helper Objects, Trust Protection Lists, and various other components. The new Copilot app for Windows 11 possesses both WebView2 and full browser capabilities, as evidenced by the inclusion of msedgewebview2.exe and multiple .dll files, indicating a bundled WebView2 runtime alongside Microsoft Edge.
Image Courtesy: WindowsLatest.com
This latest version of Copilot presents an intriguing application, potentially explaining its enhanced speed compared to typical web apps or PWAs. By incorporating a private copy of Edge within the Copilot app, along with a custom launcher (mscopilot.exe), the Copilot UI functions as a web app rendered via WebView2. However, despite its performance, the necessity of such applications on Windows 11 is debatable, given the existing abundance of web apps, PWAs, and Electron-based applications. What are your thoughts on this development? Feel free to share in the comments below.
New Copilot for Windows 11 includes a full Microsoft Edge package, uses more RAM
A new iteration of Copilot is making its way to Windows 11, marking a significant shift from native code (WinUI) to web components. This transition, anticipated based on prior analyses, comes with the unexpected inclusion of a fully-fledged version of Microsoft Edge. While it remains unclear whether Microsoft is falling behind in the AI landscape, it is evident that the company has struggled to establish a cohesive Copilot experience for Windows, frequently altering its approach every few months.
The latest update replaces the previous native app, which itself had succeeded the WebView version, which in turn had replaced the Progressive Web App (PWA), and so forth. This evolution has seen Copilot transition from a sidebar feature to its current form.
For those yet to experience the new Copilot, a visit to the Microsoft Store is in order. A search for “Copilot” will reveal a new listing titled “Microsoft Copilot,” complete with a download button—even if the application is already installed on your device. Clicking the Download button results in an almost instantaneous completion, as it does not download the Copilot app directly but rather an installer akin to the Microsoft Edge installer.
The Store indicates that further action is required in another window, highlighting that the Copilot download process is no longer managed directly through the Microsoft Store, a pattern reminiscent of Microsoft Teams. Once the update is complete, the previous native Copilot app, built on the WinUI framework, vanishes from the Start menu and other locations, making way for the new version.
Upon launching the new Copilot, users will notice a striking resemblance to the web version (web.copilot.com). The experience is notably smoother and almost feels native; however, it comes with certain drawbacks, particularly concerning high RAM usage, which raises concerns about Microsoft’s ongoing efforts to enhance Windows performance.
Copilot’s new version is a resource hog, a hybrid version that ships with its own Edge browser
In testing conducted by Windows Latest, it was observed that Copilot consumes up to 500MB of RAM in the background, escalating to nearly 1GB during user interaction. In contrast, the previous native Copilot maintained a RAM usage of less than 100MB.
This prompted further investigation into the differences of the new “web-based” Copilot app, revealing it to be a hybrid web application that operates with a rebranded and forked instance of Edge within a WebView2 container. The installation folder for Copilot contains a directory labeled 146.0.3856.97, indicating a complete Microsoft Edge installation, which occupies approximately 850 MB. This folder houses all necessary Edge binaries, including msedge.exe and various supporting files.
Notably, the msedge.dll file within the Copilot app package is 315 MB, confirming the presence of a full Chromium browser engine. If this were a standard WebView2 or PWA, it would have utilized the existing Edge integration in Windows 11 rather than shipping with its own version of Edge.
Additionally, Edge subsystems are embedded within Copilot’s package, encompassing Browser Helper Objects, Trust Protection Lists, and various other components. The new Copilot app for Windows 11 possesses both WebView2 and full browser capabilities, as evidenced by the inclusion of msedgewebview2.exe and multiple .dll files, indicating a bundled WebView2 runtime alongside Microsoft Edge.
This latest version of Copilot presents an intriguing application, potentially explaining its enhanced speed compared to typical web apps or PWAs. By incorporating a private copy of Edge within the Copilot app, along with a custom launcher (mscopilot.exe), the Copilot UI functions as a web app rendered via WebView2. However, despite its performance, the necessity of such applications on Windows 11 is debatable, given the existing abundance of web apps, PWAs, and Electron-based applications. What are your thoughts on this development? Feel free to share in the comments below.