Legacy
12 TopicsTutorial: 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/download17KViews4likes9CommentsAccess Microsoft Edge Legacy/Classic (EdgeHTML) after installing the new version of Microsoft Edge
Access Microsoft Edge Legacy/Classic (EdgeHTML) after installing the new version of Microsoft Edge (Chromium) This article describes how to access Microsoft Edge Legacy (version 45 and earlier) after installing the new version of Microsoft Edge. Note: This article applies to the Microsoft Edge Stable channel. The procedures in this article apply to systems that have been updated with the latest security updates, up to and including November 2019. When the new version of Microsoft Edge is installed, the old version (Microsoft Edge Legacy) will be hidden. All attempts to launch the old version will redirect the user to the newly installed version of Microsoft Edge. Before you begin Before using the detailed instructions in this article, consider the following 2 steps to enable a side-by-side browser experience. These steps will let your users run Microsoft Edge Legacy and the next version of Microsoft Edge (Beta channel) side-by-side. Prevent the automatic install of the next version of Microsoft Edge by Windows Update. For more information, see Windows Update: FAQ Install the Beta channel of the new version of Microsoft Edge. Note This side-by-side solution is less complex and requires less management that the detailed solution described next in this article. How operating system (OS) changes are triggered After the systems are fully updated and the Stable channel of the next version of Microsoft Edge is installed, the following registry key and value is set: Key: SOFTWARE\Microsoft\EdgeUpdate\ClientState\{56EB18F8-B008-4CBD-B6D2-8C97FE7E9062} Key value: BrowserReplacement Important This key is over-written every time the Microsoft Edge Stable channel is updated. As a best practice, we recommend that you don’t delete this key to allow users to access both versions of Microsoft Edge. How to enable a side-by-side experience with both versions of Microsoft Edge Installing the Stable channel of the next version of Microsoft Edge at system-level will cause the current version (Microsoft Edge Legacy) to be hidden. If you want to let your users to see both versions of Microsoft Edge side-by-side in Windows, you can enable this experience by setting the Allow Microsoft Edge Side by Side browser experience group policy to "Enabled". To enable the side by side browser experience policy: Open the Group Policy Editor. Under Computer Configuration, go to Administrative Templates>Microsoft Edge Update>Applications. Under Applications, select "Allow Microsoft Edge Side by Side browser experience" and then click Edit policy setting. Select Enabled and then click OK. Note By default, this group policy is set to "Not configured", which results in Microsoft Edge Legacy being hidden when the new version of Microsoft Edge is installed. For the best experience, the Allow Microsoft Edge Side by Side browser experience should be enabled before the new version of Microsoft Edge is deployed to your users' devices. If the group policy is enabled after Microsoft Edge is deployed, there are the following side effects and required actions: Allow Microsoft Edge Side by Side browser experience won't take effect until after the installer for the new version of Microsoft Edge is run again. Note The installer can be run directly or automatically when the new version of Microsoft Edge updates. Microsoft Edge Legacy will need to be re-pinned to Start or the Taskbar because the pin is migrated when the new version of Microsoft Edge was deployed. Sites that were pinned to Start or the Taskbar for Microsoft Edge Legacy will be migrated to the new version of Microsoft Edge. Source16KViews0likes2CommentsMicrosoft is Adding Classic ‘Edge Mode’ to New Edge Browser
Microsoft is developing a new 'Edge Mode' that lets users visit sites using the same rendering engine as Classic Edge to continue using legacy web applications. In the Chromium-based Microsoft Edge, users can enable a feature called 'Internet Explorer Mode' that causes the browser to emulate Internet Explorer 11. This mode is designed for organizations that need to utilize web apps that were designed for the legacy browser. When Internet Explorer mode is enabled, the Internet Explorer icon will appear in the address bar and sites that you visit will think you are running Internet Explorer 11. Edge in Internet Explorer Mode If Internet Explorer mode is enabled, the Microsoft Edge Dev and Canary builds have also added a new option called 'Open sites in Edge mode'. While nothing official has been announced about this feature, it will most likely allow the browser to emulate Classic Edge. Open sites in Edge mode To use this feature, an Edge flag named "Enable IE Integration" at edge://flags/#edge-internet-explorer-integration must be set to 'IE Mode'. Enable IE Integration flag Once configured, users can then launch the new Microsoft Edge program with the '--ie-mode-test' command line argument to enable the Internet Explorer mode feature. Launch with --ie-mode-test argument Once that feature is enabled, an additional 'Open sites in Edge mode' option will become available under Options -> More Tools. This new mode does not appear to do anything as of yet. Still being developed This feature is still being developed as can be seen by the browser user-agents being sent when using these emulation modes. When a browser visits a web site, a user-agent string is sent to the web site with each request that can be used to identify the name and version of the browser. This user-agent can then be used by the site to determine what features the browser supports and any code changes that need to be made so that the web site renders properly. Below are the various user-agent strings sent by Microsoft Edge, Classic Edge, and the IE and Edge modes. New Microsoft Edge browser user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4023.0 Safari/537.36 Edg/81.0.396.0 Classic Microsoft Edge user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Edge/18.19013 Internet Explorer Mode user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko Edge Mode user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4023.0 Safari/537.36 Edg/81.0.396.0 As you can see, when in Internet Explorer Mode the user agent is set to the one used by Internet Explorer 11. Edge Mode, though, still uses the same user-agent as the new Microsoft Edge rather than Classic Edge, which indicates that this feature is still in its infancy and being developed. As with all Microsoft software features, this one may not make it to Release, but based on the availability of IE Mode, we can expect that it will. Source16KViews3likes10CommentsFullscreen Dropdown doesn't have a close and minimize button
The Enable Fullscreen Dropdown button is a very good feature but lacks certain improvements which needs to be published. Every time when I want to close the browser when it is already full screen, I first had to toggle fullscreen. Then I had to close the browser. Also there is no minimize button, both these features were there in edge classic. Kindly add these. Also when certain HTML elements such as video elements or frames are made fullscreen using the attribute fullscreen, the fullscreen dropdown doesn't appear instead traditional circled x appears. Such as when youtube videos are made full screen using fullscreen button on videos, the dropdown doesn't appear. Kindly make these minimize and close button available in fullscreen dropdown. These too was present in edge legacy. Lastly, the fullscreen dowpdown activation area in fullscreen mode and pdf toolbar activation area in fullscreen mode coincide, which makes it impossible to use pdf toolbar in fullscreen mode when using dropdown. This too was present in edge legacy.6.7KViews3likes11CommentsTaskbar peek in fullsreen mode
Edge chromium currently hides the taskbar in fullscreen mode. User has to press Win + T or Win keys every time to display taskbar while in fullscreen. When being fullscreen taskbar should be visible when the mouse is brought down near the taskbar. Edge legacy had this feature. Kindly work on it. I am attaching a screenshot from the deg legacy.6.6KViews9likes7Comments[FIXED] Legacy Edge extensions on Windows store after installing the new Edge
Today I came across this extension when browsing Windows store https://www.microsoft.com/store/productId/9P59WXTBHZZM I could install it without any issue but the thing is it doesn't work when I have the Stable version of Chromium based Edge installed. clicking "launch" opens the new Edge only, nothing else happens. I think the proper way to handle this situation is to either hide these extensions from Windows store once the new Edge is installed, OR show a message to user that: "it's not compatible with the current installed version of Edge browser". My suggestion is to add the new Chromium based Add-ons to the Windows store to be easily available and installed by users. https://microsoftedge.microsoft.com/Solved5KViews4likes8CommentsPotential Improvement - Content Decryption Unproductive CPU utilisation
MissyQDeleted Utility: Media Foundation Content Decryption Module Service consumes a lot of extra unwanted CPU as in the below screenshot it can be seen to be consuming 15% CPU in Browser Task Manager which it is consuming in vain by doing extra work of transferring the media data to the Windows Decription Module. Instead try optimizing it by sharing the bowser's media data with decryption module and render it by just drawing output frames of decryption module. This way it will be optimized like Films and Tv app which hardly consumes 1% CPU and just consumes GPU. Try to remove this middle decryption layer service as it is not performing any productive computation. The reason this small performance issue I am highlighting is that as the playback rate increases the CPU usage of this service increases which is not a good sign. I have conveyed it through feedback. This Video Playback through Media Foundation is a very important flag which if optimized will make it best upcoming built-in browser and this feature will also save much battery if optimized. o1.5KViews0likes1CommentPDF Inking on the new Edge is compatible with legacy Edge
I just realized this cool feature. Inking and drawings done on a PDF file in the new (Chromium based) Edge can be erased in the legacy Edge, and vice versa. Highlighted texts in either of the browsers can also be modified And removed in the other browser. lastly, added sticky notes in Edge classic on a PDF file can also be seen on the new Edge. More info: https://techcommunity.microsoft.com/t5/discussions/new-feature-pdf-inking-improvements-more-colors-and-thickness/m-p/11028531.3KViews5likes0Comments[Downloads UI] Legacy UI is used when a download comes from a pop-up window
What is the issue? Edge now uses a modern-UI for handling downloads: an icon on the toolbar, just after the end of the Address Bar, which shows a vertical-list of downloads. However, when a download starts from a pop-up window, such as from the Microsoft Update Catalog site, the old-UI is used instead, which feels a bit inconsistent! Expected outcome That only the modern-UI will be used. Proposed solutions My preferred-solution would be to add a setting into Edge where the user can ask for pop-ups to load into a new tabs, instead of separate windows -- Internet Explorer 11 had such a setting. This would then mean pop-up content gets treated like any-other tab, and so would use the modern-UI. Alternatively, when a download starts from a pop-up window, the parent-window should come to the foreground, and the download then begin in that window. Before posting here, have you submitted feedback via the "Send Feedback" feature in Edge? Yes Browser and Operating System Edge 90.0.818.62 (Official build) (64-bit) Windows 10 Home (64-bit) Version 20H2 (Build 19042.985; May 2021 update-level)979Views0likes0CommentsFeature Resquest - More video formats to be playable
Since now there is a flag for media foundation video playback, so I suppose the supported video formats must be increased from just mp4 to several more like mkv, etc. which at present it doesn't support. It would be good if more formats are supported as many people like me use browser for everything from media playback to document editing. So it would be nice if the media formats list is extended. You don't have to worry for the codec as the Windows Decryption module would decrypt it.961Views1like1Comment