Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 5 subscribers
  • Views 3372 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

Unable to change Screen Saver

ia-hawk-fan07

I have safguard easy 5.50.1.17 and Windows 7 64 bit on Lenovo T510 laptops. We have discovered that we can no longer changed the screensaver. Any changes we make are changed back as soon as we are done. While we are not sure if this is being caused by Sophos we thought we would ask and see if anyone else has experienced this problem.

Thanks!

:6767


This thread was automatically locked due to age.
  • 0

    My best guess at this is, that in Windows 7 the "secure" screensaver is the blank one. So when you compter goes to screensaver and you have Sophos encryption installed you can not change it. Mainly because you need the secure one to log back in to Windows. I am hoping someone here on the forums or someone from Sophos might confirm or deny this.

    Thanks!

    :6945
  • 0

    I've seen the same problem with v 5.50.1 and 5.50.8. SGNAuthService is resetting the screensaver immediately. I have a TS log raised and at the moment, support know nothing about it either but they are investigating. I've sent full procmon evidence in which clearly shows SGN is doing this so hopefully we'll have an answer soon. I will post more when I have a response.

    Matt

    :8963
  • 0

    Fantastic!

    Support have taken 10 days so far, seemingly made no progress finding this problem despite having the below registry trace and their answer after I chased; 'can you send me a copy of system info and a zip of the event logs'. What on earth are they looking at, the evidence is in plain view in the registry trace. You've got your fingers into more than you should I feel.

    Anyone else started to notice this? Specifically we're standalone and I can reproduce the issue on all 5.50 versions on Windows 7 (haven't tested on vista/xp). Just set the screensaver to anything and watch SGN change it back to 'blank'.

    Matt

    Time of Day Process Name PID Operation Path Result Detail
    55:20.3 rundll32.exe 2956 RegQueryValue HKCU\Control Panel\Desktop\SCRNSAVE.EXE SUCCESS Type: REG_SZ, Length: 66, Data: C:\Windows\system32\scrnsave.scr
    55:20.3 rundll32.exe 2956 RegQueryValue HKCU\Control Panel\Desktop\SCRNSAVE.EXE SUCCESS Type: REG_SZ, Length: 66, Data: C:\Windows\system32\scrnsave.scr
    55:24.3 rundll32.exe 2956 RegSetValue HKCU\Control Panel\Desktop\SCRNSAVE.EXE SUCCESS Type: REG_SZ, Length: 64, Data: C:\Windows\system32\Ribbons.scr
    55:24.3 SGNAuthServicen.exe 1828 RegQueryValue HKCU\Control Panel\Desktop\SCRNSAVE.EXE SUCCESS Type: REG_SZ, Length: 64, Data: C:\Windows\system32\Ribbons.scr
    55:24.3 SGNAuthServicen.exe 1828 RegSetValue HKCU\Control Panel\Desktop\SCRNSAVE.EXE SUCCESS Type: REG_SZ, Length: 66, Data: C:\Windows\system32\scrnsave.scr
    55:24.3 SGNAuthServicen.exe 1828 RegQueryValue HKCU\Control Panel\Desktop\SCRNSAVE.EXE SUCCESS Type: REG_SZ, Length: 66, Data: C:\Windows\system32\scrnsave.scr
    55:24.3 SGNAuthServicen.exe 1828 RegQueryValue HKCU\Control Panel\Desktop\SCRNSAVE.EXE SUCCESS Type: REG_SZ, Length: 66, Data: C:\Windows\system32\scrnsave.scr
    55:24.3 SGNAuthServicen.exe 1828 RegQueryValue HKCU\Control Panel\Desktop\SCRNSAVE.EXE SUCCESS Type: REG_SZ, Length: 66, Data: C:\Windows\system32\scrnsave.scr
    55:24.4 Explorer.EXE 2884 RegQueryValue HKCU\Control Panel\Desktop\SCRNSAVE.EXE SUCCESS Type: REG_SZ, Length: 66, Data: C:\Windows\system32\scrnsave.scr
    :9299
  • 0

    Well it appears my rant may have sparked some action with TS... This is now confirmed as a bug that affects Win7 probably Vista too (untested) but not XP clients. The fault is to do with the policy element Authentication Policy > Lock screen after X minutes inactivity which when changed from its default of 0 on Win 7, prevents changes to the screensaver and time value. SGN will rewrite these values when you 'apply' to their previous states so for example, if you had 'blank' as your screensaver when you installed SGN, you will not be able to change it.

    Engineering have the fault but as yet there's no information on a fix. Chances are, we won't see anything for a while. So the workround is to leave this policy element set to zero or, set your screensaver choice prior to installing your policy configuration.

    Matt

    :9327
Unfiltered HTML