Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 14 subscribers
  • Views 2211 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

Sophos Intercept X has not updated: stuck to version 2022.1.1.22

Fabio Danzetta work

Hello everybody,

after a long time of not coming back, I went to the release notes page and saw that our version of Sophos Intercept X is a couple of releases behind.
The last one tells me: Version 2022.1.3.3
Can you tell me what it could be due to?
And finally, is there a way to forcibly update both my pc and all the other clients from Central to the latest release?

Thank you all.



This thread was automatically locked due to age.
Parents
  • 0

    2022.1.3.3 is the latest, as detailed here: Sophos release notes

    I have:

    Is there a chance you are using controlled updating? If enabled in Central, then at the clients, in the registry, for this example, under:

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sophos\AutoUpdate\Service\CloudSubscriptions\HitmanProAlert

    ...there will be a FixedVersion value.  E.g. If I pause updating when on 2022.1.3.3 the value will be 2022.1.3.3.0.

    So checking if you have FixedVersion string value under the following keys will answer that question.

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sophos\AutoUpdate\Service\CloudSubscriptions\Base
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sophos\AutoUpdate\Service\CloudSubscriptions\CloudAV
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sophos\AutoUpdate\Service\CloudSubscriptions\Encryption
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sophos\AutoUpdate\Service\CloudSubscriptions\HitmanProAlert
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Sophos\AutoUpdate\Service\CloudSubscriptions\MDR

    Not all customers are updated to the latest at the same time, so there is a chance this could be expected but checking you haven't paused updating is probably the first thing to do.

  • 0 in reply to Sophos User930

    Hello,

    I checked in Central and automatic updates are set.
    I also did the verification of the registry keys and in none I found the FixedVersion value.

    Thank you

Reply Children
  • +1 in reply to Fabio Danzetta work

    Without having a FixedVersion string in the registry, then it doesn't sound like you have controlled updates enabled.

    When I check SophosUpdate.log I have:

    2022-10-30T16:45:23.255Z [ 7616: 7016] I Syncing suites [sdds3.WindowsCloudAV_11.6.562.93124a541a.dat, sdds3.WindowsCloudClean_1.0.42.55133bcba5.dat, sdds3.WindowsCloudEncryption_2022.1.0.58.a3e31667a8.dat, sdds3.WindowsCloudHitmanProAlert_2022.1.3.3.0.cde6db1a43.dat, sdds3.WindowsCloudMDR_2022.1.0.57.158580cb0f.dat, sdds3.WindowsCloudNextGen_2022.2.2.1.0.52b88181d9.dat]
    2022-10-30T16:45:23.255Z [ 7616: 7016] I Release groups [A] 

    This shows I am getting "sdds3.WindowsCloudHitmanProAlert_2022.1.3.3.0.cde6db1a43.dat"

    I first had it here:
    2022-10-14T20:56:20.309Z [10460:11100] I Syncing suites [sdds3.WindowsCloudAV_11.6.562.93124a541a.dat, sdds3.WindowsCloudClean_1.0.42.55133bcba5.dat, sdds3.WindowsCloudEncryption_2022.1.0.58.a3e31667a8.dat, sdds3.WindowsCloudHitmanProAlert_2022.1.3.3.0.cde6db1a43.dat, sdds3.WindowsCloudMDR_2022.1.0.57.158580cb0f.dat, sdds3.WindowsCloudNextGen_2022.2.2.1.0.52b88181d9.dat]

    But as I say, not all customers get it at the same time.

    You can probably see in your log that:

    a) The update log ends with
    A SophosUpdate has completed (exit 0).
    I.e. all is OK.

    b) What version you are getting as a sdds3 package?

    You will probably have to contact support to understand when you might get the version.

Unfiltered HTML