screen freezes while reading MSN articles

[Grum4]

While viewing MSN, reading articles, I frequently have the screen freeze and only partially fill in.  I then get a narrow banner across the bottom that says "msn.com is not responding due to a long running script".  And then there is a gray box that says "stop script".  If I click on that box, then it will complete filling in the screen and I am then able to scroll through the articles.  This situation may occur several times in an hour or then again not that often.

[IT_WinSec]

Hello @Grum4 

Welcome !

The situation is caused most likely due to Internet Explorer - the Microsoft "browser" that you use. But even Microsoft senior representatives do not consider this a browser any more. They call it "legacy solution" - source >> https://www.zdnet.com/article/microsoft-security-chief-ie-is-not-a-browser-so-stop-using-it-as-your-...

• Your solutions -> switch to modern real browser - consider Firefox by Mozilla (my recommendation)

or Google's Chrome, or Opera (based on Chrome)

Firefox is modern, secure, free and open source browser which cares about your privacy + it can add multiple extensions. Good articles - Why choose Firefox ?

• https://itsfoss.com/why-firefox/
• https://www.fastcompany.com/90174010/bye-chrome-why-im-switching-to-firefox-and-you-should-too

[IT_WinSec]

If you love IE too much and do not want to move away from it, here are instructions which you may try:

• You could also turn off the script warnings:

From within IE, go to  Tools> Internet Options> Advanced
Check "Disable script debugging" and uncheck "Display a notification about every script error"

• If you're seeing the message on all or nearly all sites, a browser add-on might be causing it.

Start Internet Explorer without add-ons from Start> Programs> Accessories> System tools> Internet Explorer (no add-ons)
or

from Start> Run (or Windows logo key + r) type in iexplore.exe -extoff

(iexplore.exe<space>-extoff) then hit Enter.

Try with the MSN website.

If the problem goes away, an add-on is causing it.

To determine which add-on is causing the problem see this old (but still relevant) article:

IE Blog  Troubleshooting and Internet Explorer’s (No Add-ons) Mode >> http://blogs.msdn.com/ie/archive/2006/07/25/678113.aspx