Each computer is unique.
Originally Posted by pokeefe0001
What works on one system may not work the same on another system.
My original advice regarding a proper clean reinstall of KIS 2016 was merely a "best practices" recommendation that could be deployed with a period of testing before reinstalling it to see if your issue resolves with KIS 2016 uninstalled.
That would help to point to KIS as possibly contributing to the issue (perhaps the imported 2015 configuration settings).
In order to tease it out, it would help to know if the problem reoccurs after reinstalling KIS with a proper, clean reinstall.
This is how I would approach it:
1) Temporarily, cleanly uninstall KIS, as I previously described (saving ONLY license info, not settings). Do not reinstall KIS yet, and run with the native WD and WF for a while.
2) If the problem resolves with KIS uninstalled, then I would proceed to the next step: a clean reinstall of KIS 2016.
A. If the problem returns with KIS reinstalled, then that suggests that there is something going on with your system/configuration/software-conflict/etc.; further work would be needed to sort it out.3) Needless to say, if the problem persists despite uninstalling KIS and leaving it uninstalled, then the root cause is something else.
B. If the problem does NOT return with KIS reinstalled, then the issue might be attributed to the prior KIS installation that was fixed by the clean reinstall.
C. It's important to be sure to verify after reinstalling KIS that both WD and WF are disabled. Having either of those running in the background could cause issues, not only with KIS, but with most other 3rd-party AV/firewall programs.
>>It would help to know what other security applications are now installed or have been previously installed on this system. Leftovers and remnants can cause subtle performance and stability issues.
Not that I am aware of, but I will defer to others more expert in these matters.
Has there been a report of 3rd party security software causing this particular update problem? At least one person reporting the problem uses Norton. I don't know about the others.