If you're a designer/developer and used the Edge F12 developer tools the new Edge Chromium was a major downgrade in this regard. So you may want to reinstall Edge just for this purpose.
If you have already installed Edge Chromium or it was installed in a recent update you can follow these steps to bring back the classic Edge and/or run both browsers at the same time.
First, download the Edge Chromium installer and Policy Files from here:
Now extract the Policy files any copy msedge.admx and msedgeupdate.admx from the extracted folder.
copy these to the C:\Windows\PolicyDefinitions folder on your computer.
Once you have done that then open group policy editor,
once open, under Computer Configuration go to Administrative Templates, Microsoft Edge Update, Applications then open "Allow Microsoft Edge Side by Side browser experience" and set to enabled.
now uninstall Edge Chromium.
Once its uninstalled open search and type "Edge" and the old edge icon should show up, pin this to your task bar because you will not be able to after Chromium is reinstalled.
Now if you want Chromium installed as well, install the .msi package from the step above that you downloaded from Microsoft downloads.
Now you should be able to run both browsers together.
So you open up F12 and see this obscure error:
In some cases this is caused by browser updates or perhaps server changes like adding gzip support to IIS.
This error in most cases is to to some code not properly closing before another script is executed thus chunking the response.
You should review the code for the page and look for Response.Close(); method. Something like this:
and replace it with a proper Response.End(); method instead.
Now save and reload your page.
First if you have not yet done so enabling dynamic compression on IIS improves page load speed by about 300% in most cases. To do so you can follow the following steps.
From Server Manager choose "Add Roles and Features"
Now Next on the before you begin page if you have not already checked the box for "Skip this page by default" option previously.
Leave the default of "Role-Based or feature-based installation" selected and choose Next.
Now expand "Web Server (IIS)", "Web Server", "Performance" and check the box for "Dynamic Content Compression" then choose Next, Next then Install.
Now you're done.
In some cases some older code can cause you issues after doing this. For example some .net code previously written to use Response.Close(); method will toss a net::ERR_INCOMPLETE_CHUNKED_ENCODING error in Chrome and Edge Chromium browsers.
You can solve this with the following method.
How to solve the net::ERR_INCOMPLETE_CHUNKED_ENCODING error.
First if you have not already install the IIS role on your windows system.
Open IIS and choose the top level folder(your server) then choose Server Certificates
Now choose Create Self Signed Certificate from the far right
friendly name should be the DNS name of the device you need to create the pem file for, then choose ok.
Now open the certificate manager on your system, to do this run mmc
File > Add/Remove snap-in
Choose Certificates > Add > Computer account > Next > Local computer > Finish > OK
Now expand the certificates folder you create the cert in, by default this is Personal > Certificates.
right click on the certificate you created and choose all tasks > export > next > No, > next > Base-64 > next >
pick a file name
Now, you can rename the .cer file to .pem and that's it you're done.
This can be one of the most frustrating errors because your UNC path may work from some computers but not others. If you are receiving this error the following steps should solve the issue.
Go to Control Panel
- change the view by to small icons
- select "User Accounts"
- select "Manage your credentials"
- select "Windows Credentials"
- then "Add a Windows Credential"
Now enter your UNC server and share path for example: \\UNCServer\SharedFolder
Username and password, then click OK.
Now you should be able to access your UNC share from the windows explorer shell.