Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 2 subscribers
  • Views 5511 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Finding Source of "Restart Needed for Updates to Take Effect" (Code 0000006d) Alert

BrianM

In our environment we have several (around 10) systems in the Sophos Console reporting. Resolving the alerts isn't too difficult, as they appear to go away with a restart, as expected. The issue is we aren't sure why the alert is appearing. If it was a Sophos update, I would expect more than just 10 or so systems (they all, in theory, should be identical or very similar in configuration).

From reading the Knowledge Base article on the error, it sounds like Sophos may report this error for a third party reporting that a reboot is required.

So, two actual questions. First, is there a way to identify what is specifically triggering this error in Sophos? And second, is there any way to control or disable third party products triggering this error? I understand the reasoning behind it, but we would prefer Sophos returns errors specifically about Sophos, and not other software as well.

 

Thank you



This thread was automatically locked due to age.
  • 0

    Hello BrianM,

    as the article states three reasons.
    1. You'll always get this message for new installs. Web Protection for example requires a .dll to be loaded, so a running browser would have to be restarted before WP can take effect. A reboot assures that all potentially affected processes are restarted.
    2. Certain upgrades (not necessarily "big" SAV version changes but, for example, .dll or driver replacements) can cause this request and might not be requested on all seemingly identical systems for various reasons.
    3. As stated it's Best Practice to alert you. Note that while listed under Errors these are only warning, it's not possible to predict though whether this condition can eventually prevent (major) upgrades.

    a way to identify what is specifically triggering this error
    the only way is to analyze the endpoints' Install, CustomActions, and Uninstall logs. But then you'd likely find one of the reasons mentioned above.

    Christian 

Unfiltered HTML