Jump to content


  • Content Count

  • Joined

  • Last visited

About GuiltySpark

  • Rank
  1. Kaspersky is not rebooting our machines, it's just asking for a reboot. I rebooted the machine and then Kaspersky asks for another reboot about 10-15 minutes lates; it's not forcing a reboot of the machines. No matter how many times I reboot, KES wants another reboot. It's like the update is not getting applied. That's why I thought the Self-Defence was the issue but that didn't do the trick. This is happening on many of our machines.
  2. https://drive.google.com/file/d/0B56C0MkfQ8hDa2FETUFscUdCZFk/view?usp=sharing
  3. The self defense trick did not work. I noticed that when tracing was enabled the reboot prompt did not come back after a reboot. After I turned tracing off, the reboot prompt came back in about 20 minutes. As you said, KSC is not reporting the reboot as critical. Still unable to upload a GSI report because it's too big. Trace.zip
  4. I'm unable to provide you with the full GSI report with event logs since it's bigger than 4MB. I'm currently trying disabling Self-Defense then rebooting and seeing the reboot prompt comes back.
  5. There is a different thread open for this question. I'd like to know more about these updates and when a reboot will be required. Apparently, it has something to do with KES OpenSSL components. I have received the update notification multiple times.
  6. I have rebooted several of our machines and this message reappears after the reboot. Is the update getting applied? Why do I need to keep restarting? Needed a reboots 7/13/2017 3:18:09 AM 7/14/2017 8:16:57 PM 7/17/2017 12:16:00 PM 7/18/2017 12:13:44 AM In KSC, it doesn't show that a reboot is required. Only on the client does it show that a reboot is required. 7/18/2017 12:13:44 AM : Quit and reopen the application to complete updating Application: Kaspersky Endpoint Security 10 for Windows User: DOMAIN\USER (Active user) Result: You have to restart Kaspersky Endpoint Security 10 for Windows
  7. Any update on a fix for this issue? We're having the same issues. A reboot fixes the issue or running avp.com EXIT /login:username /password:password then restarting the avp service also fixes the issue. Wish we didn't have the issue in the first place.
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.