Firefox 49.0.1 unusable since Flash Plugin 23.0 update yesterday
Hi! After updating Shockwave Flash plugin to 23.0 yesterday, I've been unable to access anything using Firefox 49.0.1...not even duckduckgo.com OR mozilla.org! I had to use my other browser, Pale Moon 26.4.1, & even IT kept freezing! I finally opened 'Private Browsing' in Pale Moon, just so I could post this. I did check to see if there was an issue with my WiFi, by running the Troubleshooter. I was so happy because it looked like it found a problem & fixed it. Unfortunately, the message box just said that the, 'Network adapter was reset.....Fixed', but I guess it doesn't mean that it was broken in the first place. The site I need the most just won't load, but it has 3 Live Nest Cams on it, so Flash or HTML 5 is needed for it to function. Here's the site in case you need to check it:
https://www.eagles.org/eagle-nest-cams/romeo-juliet/
Firefox & Pale Moon completely freeze, & not just loading the page; I can't even minimize/close/right-click, etc. I have absolutely NO control over either browser, in fact, the only way I could close them was to use Task Manager & 'end process'. It's very important to get things working again, but I don't know where to go or how to fix this. I know the danger of using an outdated Flash plugin, but it seems like this update has a glitch in it. Especially since even Pale Moon gave me trouble, (but I was able to use its 'Private Browsing' window so I could post here). There was a post with similar problems from a while ago, but the instructions were a bit over my level of tech comprehension. I hope that someone will guide me through this so I can watch my Bald Eagles again! Thanks in advance for taking the time to read & respond to my post. I really appreciate your help! All the Best, Nuts4Mutts :)
All Replies (1)
I don't think that the flash plugin would cause that much trouble, but let's check it out.
Flash: Grab the uninstaller from here: Uninstall Flash Player | Windows Uninstall Flash Player | Mac
Now try those pages again. Is the problem still there?