Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 16267 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

Restart needed for updates to take effect - Not clearing

Tyler_EFI322

Hello all,

I am fairly new to working with Sophos but sometimes we get a machine that will keep the "Restart needed for updates to take effect {0x0000006d]". Typically, I am able to resolve it by following the knowledgebase support page below. However, I have rebooted the machine several times, reinstalled the software, and followed the steps outlined in the links with no luck.

http://www.sophos.com/en-us/support/knowledgebase/31540.aspx
/search?q= 6865

The client computer has been able to contact the Enterprise console after all reboots. I have noticed that the registry value, HKLM\Software\Wow6432Node\Sophos\AutoUpdate\UpdateStatus\VolatileFlags, does not appear for this machine as well. I have tried to import the key from another client and it did not have an effect.

Does anyone have any ideas on how to resolve this issue?

Thanks

:51326


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

    Thank you Jax,

    The ALC log is still showing that an update needs to take place. I have created the VolatileFlag key and set it to 0. Then after running the update, there was no change in the Enterprise Console. I ran the process monitor and was unable to see the alupdate.exe when trying to update remotely but saw the process if I ran the update from the client. Could this be a connection issue between the client and management server? I tried another computer that is not showing the "Restart needed for updates to take effect" and it worked just fine. In both cases, I was unable to see the registry key on the problem client.

    I have also noitced that the computer in question is updating less frequently than the other servers in the same group (gaps of a day or two).

    Im not sure if this is helpful at all, but I ran a query against the error table on the database and see that the error's source is ALC with the number 109. I will be trying to some additional fixings (suggestions always welcome :smileyhappy:) but if there is no progress, I may just try to give a reinstall another go.

    Thanks again.

    :51366
Reply
  • 0

    Thank you Jax,

    The ALC log is still showing that an update needs to take place. I have created the VolatileFlag key and set it to 0. Then after running the update, there was no change in the Enterprise Console. I ran the process monitor and was unable to see the alupdate.exe when trying to update remotely but saw the process if I ran the update from the client. Could this be a connection issue between the client and management server? I tried another computer that is not showing the "Restart needed for updates to take effect" and it worked just fine. In both cases, I was unable to see the registry key on the problem client.

    I have also noitced that the computer in question is updating less frequently than the other servers in the same group (gaps of a day or two).

    Im not sure if this is helpful at all, but I ran a query against the error table on the database and see that the error's source is ALC with the number 109. I will be trying to some additional fixings (suggestions always welcome :smileyhappy:) but if there is no progress, I may just try to give a reinstall another go.

    Thanks again.

    :51366
Children
No Data