Print this page | Go back to previous topic
Forum nameThe Computer Forum
Topic subjectWin 7 update slow Browser
Topic URLhttp://www.pcqanda.com/dc/dcboard.php?az=show_topic&forum=2&topic_id=564688
564688, Win 7 update slow Browser
Posted by Chickenman, Tue Nov-21-17 06:59 PM
Installed the latest Windows Updates yesterday. Noticed an immediate slow down in Browsing speeds with Chrome. Didn't check FF or IE as I don't use them. Popular pages that I frequent were laggy and some were timing out. Chrome is up to date.

Used System Restore to roll back to before updates and all is well again. Any other reports of issues after the latest Win 7 updates. There were about ten of them.
564689, RE: Win 7 update slow Browser
Posted by dtellier, Wed Nov-22-17 02:13 AM
Just updated a couple of Windows 7 systems over here and all seems well. No problem found yet.

Dave
564690, RE: Win 7 update slow Browser
Posted by Paul D, Wed Nov-22-17 06:47 PM

If you want fast, try the new Firefox (57.0). It's a complete rewrite - virtually a new browser, and it's VERY fast. But it does mean most old extensions no longer work.



Paul D
564691, RE: Win 7 update slow Browser
Posted by Pcqandaman, Wed Nov-22-17 10:26 PM
Quote:
If you want fast, try the new Firefox (57.0). It's a complete rewrite - virtually a new browser, and it's VERY fast. But it does mean most old extensions no longer work.
I've been using Firefox 57 for over a week now and unfortunately I haven't seen any increase in speed over Firefox 56! :-(
BTW I've managed to replace incompatible extensions by new or updated ones. :--)
564692, RE: Win 7 update slow Browser
Posted by Chickenman, Thu Nov-23-17 02:21 AM
I've gone over to the Dark side ( Chrome ) for some time now. Used to love FF, but just got fed up with issues that were never resolved.

Not switching back to FF. Wondering if any Chrome users had issues after the Win 7 updates. Had issues with my E-mail ( Windows Mail 2009 ) being slow to download as well.

Everything was fine after I used System Restore... so it definitely pointed to some sort of MS update issue.