Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 6725 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

Compatibility Registry Entry for Spectre/Meltdown vulnerability not being installed as part of update?spectre

Michael Andres-Larsen

In reading the various threads on the spectre/meltdown vulnerability, Sophos Endpoint Protection started to put the necessary registry key in to allow the the Microsoft updates on January 5th. I've got quite a few endpoints that don't have the registry key even though they've been updated multiple times since January 6th on. My update managers show up to date and the clients are current and up to date? Any ideas why this may be the case?

I can manually deploy the needed reg key but I want to find out why Sophos updating isn't inserting it as expected.



This thread was automatically locked due to age.
  • 0

    Hi Michael,

    Have you looked at this article, it explains how to check if you have received the update (which is an upgrade to the Sophos Auto Update component): https://community.sophos.com/kb/en-us/128060

    Please Note: As this update is being applied over a number of days, you may not see the versions listed below on an initial check. If you require the Microsoft patch to be applied before you receive the Sophos update, you can manually set the registry key and value or you can manually download and apply the Microsoft patch without the registry key.

    For reference though the first group of SEC managed and standalone customers started on Friday with the majority going out on Monday and a few on Tuesday. Most of Central managed machines will be completed today. Sophos Home also started on Friday. UTM managed and SVE will start shortly.

Unfiltered HTML