Not what you are looking for? Ask the experts!
Sluggish after 1709 update - uninstalled Norton Security and issue is gone
Specs: Asus Laptop, i7, 8 GB RAM, Samsung EVO SSD, Windows 10 Home, Office Pro 2010, Norton Security v126.96.36.199
I had no issues with Norton Security installed with Win 10 1703. Each time I was auto upgraded to 1709, my performance suffered so I would revert back to 1703 and the issue would go away. Today, I attempted to spend some time troubleshooting to root cause and the cause was Norton Security, even with the latest 22.11..2.7 update applied. I tested uninstalling Norton Security before the upgrade to 1709 as well as leaving it on in 1703 and then performing the upgrade to 1709. When Norton Security was running in 1709, Word and Outlook were slow to open. Where Word took less than 1 sec. to pop open in 1703, it would take 3+ sec. in 1709. Outlook used to open in less than 2 sec. in 1703, and it takes 4-5 sec. in 1709. As I navigate around my laptop, I could easily sense that the laptop was not operating as well as when running 1703.
I determined that if I uninstalled Norton Security in 1709, my performance came back to where I was in 1703. During my testing where I uninstalled Norton Security while in 1703, then upgraded to 1709, before re-installing Norton Security, I had no issues with Word or Outlook. After re-installing Norton , the performance was immediately degraded again. I applied the 188.8.131.52 update and the performance was still sluggish. I don't know how much worse it could have been if I was on a spinning drive vs. a SSD.
Note: while Norton Security was installed in 1709, I even attempted to temporarily turn off real-time protection as well as the Firewall and test. The sluggishness still existed. Sluggishness only went away after I uninstalled Norton Security.
I feel like my testing clearly demonstrated that Norton Security was the cause of my sluggishness with Win 10 1709, whereas I did not have the issue when I was running Norton Security with Win 10 1703.
Anyone with the same issue?