Advice Request Kaspersky 2016 requires reboot after updating daily. Is it normal?

[Maxxx58]

Hi all,
I'm having Kaspersky Total Security 2016 installed on my computer. I noticed a strange behaviour of my KTS some days ago: It requires reboot computer after update some components, but it's regularly, even daily!. I noticed that it often requires reboot and the afternoon and evening, never facing this problem before. I did a clean install of Windows and a clean install of Kaspersky after that, everything goes flawlessly till some days ago.
Some screenshot:

Does anyone have this problem, too?
Thanks all!

 

[omidomi]

Hi all,
I'm having Kaspersky Total Security 2016 installed on my computer. I noticed a strange behaviour of my KTS some days ago: It requires reboot computer after update some components, but it's regularly, even daily!. I noticed that it often requires reboot and the afternoon and evening, never facing this problem before. I did a clean install of Windows and a clean install of Kaspersky after that, everything goes flawlessly till some days ago.
Some screenshot:

Does anyone have this problem, too?
Thanks all!

yes i have this problem, but not daily...
i restart my system and problem fixed

 

[Maxxx58]

yes i have this problem, but not daily...
i restart my system and problem fixed

I also reboot my computer as its require, but today, it requires reboot again?
I'm doing a lots of projects on my computer, restarting is really annoying

 

[omidomi]

I also reboot my computer as its require, but today, it requires reboot again?
I'm doing a lots of projects on my computer, restarting is really annoying

i mean go to kaspersky and press restart button on kaspersky dashboard

 

[harlan4096]

It's a bug will be fixed in the upcoming Patch C for 2016MR1, but it seems Patch C has been delayed to later April, because also some others bugs will be fixed. That's why They retired 2016MR1 installers temporally from official WebSite.

Users may go back temporally to 2016MR0, or stay in 2016MR1, as (They say) system is protected and standard updates are still coming to system normally.

 

[omidomi]

It's a bug will be fixed in the upcoming Patch C for 2016MR1, but it seems Patch C has been delayed to later April, because also some others bugs will be fixed. That's why They retired 2016MR1 installers temporally from official WebSite.

Users may go back temporally to 2016MR0, or stay in 2016MR1, as (They say) system is protected and standard updates are still coming to system normally.

i also have this problem but its 1 week i do't have it

 

[Maxxx58]

i mean go to kaspersky and press restart button on kaspersky dashboard

Yes, I pressed reboot button in Kaspersky Dashboard and problem is not fixed

 

[Maxxx58]

It's a bug will be fixed in the upcoming Patch C for 2016MR1, but it seems Patch C has been delayed to later April, because also some others bugs will be fixed. That's why They retired 2016MR1 installers temporally from official WebSite.

Users may go back temporally to 2016MR0, or stay in 2016MR1, as (They say) system is protected and standard updates are still coming to system normally.

Thanks for the information! MR1 has tons of bugs, so sad!

 

[harlan4096]

It was working fine more or less until Patch A, I think with Patch B started to come some new bugs...

 

[SherKaan]

Same reboot problem here. This is the worst Kaspersky software release in many years. What a shame!

 

[Maxxx58]

Same reboot problem here. This is the worst Kaspersky software release in many years. What a shame!

What do you do with this problem? Reboot when it requires?

 

[SherKaan]

What do you do with this problem? Reboot when it requires?

Yes.

 

[Maxxx58]

Yes.

So annoying!

 

[SherKaan]

So annoying!

They are going downhill pretty fast, if they don't get their act together. Seriously.

 

[omidomi]

wow it seems many users have this issue ...

 

[harlan4096]

Yes, all users with 2016MR1 16.0.1.445b are affected

 

[SpartacusSystem]

I've just seen your thread! The minute after I've posted mine up!

 

[omidomi]

here reply from Kaspersky:

 

[Evgeny]

Yes, all users with 2016MR1 16.0.1.445b are affected

I guess this is only the Total Security version effect? because I have 16.0.1.445(b) (Kis) and dont have that problem.

 

[omidomi]

I guess this is only the Total Security version effect? because I have 16.0.1.445(b) (Kis) and dont have that problem.

me also i have KIS