- Dec 20, 2014
- 619
Haha, this bug will be fixed in 2017 versionhere reply from Kaspersky:
Kaspersky 2016 requires reboot after updating daily. Is it normal?
- Thread starter Maxxx58
- Start date
Please provide comments and solutions that are helpful to the author of this topic.
- Status
- Apr 5, 2014
- 6,010
- Apr 28, 2015
- 9,039
- Feb 7, 2016
- 79
ill wait to April then [removed] glass of patient overflowed
2016MR1 16.0.1.445b
2016MR1 16.0.1.445b
Last edited by a moderator:
- Mar 16, 2016
- 46
what do u think ?
stay untill 2017...(9 months)
Screw that. 9 months for the fix, heckla no for a company that worth billion of dollars industry.
- Jan 14, 2015
- 1,761
in all fairness, there is a workaround which is downgrade to an early version MR0.
if they didnt care about it, they would have not come out clean.
It is important to give credit where is deserved and in this case it is deserved, regardless how long will it take for a fix to be deployed.
Choosing to deploy the fix in 2017 version (where Kaspersky historically releases their "next year" version sometime half way through the year) is a good move instead of a rush and not properly tested fixed for next patch instead.
- Apr 28, 2015
- 9,039
There would be a different wordaround: install a beta version of Patch C which it seems is available yet in the beta/test server, and then revert to standard update servers, this could fix the problem, but these days only working with laptop (KES10) and can't confirm/test it.
- Status
Similar threads
