locked
Lockscreen image won't update on Domain Joined v1607 Workstations (Using GPO to set) RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am seeing a strange issue where the lockscreen image isn’t updating on our domain joined Windows Enterprise 10 v1607 workstations, it appears to be somehow stuck / using an old cached image file for the lockscreen even after having updated the file that group policy points to locally on our workstations.

    We currently have the existing old lockscreen image stored locally on the workstations like this: C:\images\lockscreenv1.jpg

    And then group policy points to that image file:

    Force a specific default lock screen and logon image: Enabled - Path to lock screen image: C:\images\lockscreenv1.jpg

    Prevent changing lock screen and logon image: Enabled

    What I am trying to do is use a simple script deployed via SCCM to just replace the current file referenced by the GPO, keeping the file name the same and thus not needing to change the GPO. I have a simple powershell script that does this successfully here:   

    #Delete existing Lockscreen Image

    Remove-Item C:\images\lockscreenv1.jpg

    #Copy new Lockscreen Image

    Copy-Item $PSScriptRoot\img0.jpg C:\images\lockscreenv1.jpg


    The issue is that even after the image file is changed to the new file with the same name, the lockscreen is not updated even after multiple reboots.  When going to the personalize GUI menu >Lock screen settings the “Some setting are managed by your organization is displayed” is shown due to GPO lockdown setting and the background is set to “picture”, the new image is actually shown in the preview correctly BUT it isn’t actually being used at the lockscreen.

    Is anyone aware of a cache image location for the Lockscreen image that needs to be cleared or a command that  can be run to do this? Somehow windows is stuck using the old cached version of the image and we need a way to force it to use the new image.

    Have tried this on multiple VMs and physical workstations with our Windows 10 Enterprise v1607 configuration, and same issue with it not updating in all cases.


    Monday, April 30, 2018 5:32 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Is anyone aware of a cache image location for the Lockscreen image that needs to be cleared or a command that  can be run to do this? Somehow windows is stuck using the old cached version of the image and we need a way to force it to use the new image.

    Yes, specifically here: C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P

    However, that folder is locked down and you won't be able to access it short of taking ownership and resetting the rights or accessing it from a process running as SYSTEM. In our case we use a scheduled task to do what's needed as system, and trigger it manually to refresh the cache after updating the source image.

    Inside that folder you'll find a lockscreen.jpg and various other files with resolutions appended - one for the native resolution and a bunch of thumbnails. What we do is delete all the contents, and copy the correct image into place as lockscreen.jpg. Windows then seems to generate the rest as needed.

    This fix was needed for us on 1607 and 1703, but seems fixed in 1803 (we skipped 1709).

    See also this thread: https://social.technet.microsoft.com/Forums/en-US/9b01f9ec-85de-413c-bf4c-ac12599d46b4

    And this thread: https://social.technet.microsoft.com/Forums/en-US/b4e6074f-09ce-4d77-8102-ba7a1cd33088

    Monday, April 30, 2018 6:17 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Is anyone aware of a cache image location for the Lockscreen image that needs to be cleared or a command that  can be run to do this? Somehow windows is stuck using the old cached version of the image and we need a way to force it to use the new image.

    Yes, specifically here: C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P

    However, that folder is locked down and you won't be able to access it short of taking ownership and resetting the rights or accessing it from a process running as SYSTEM. In our case we use a scheduled task to do what's needed as system, and trigger it manually to refresh the cache after updating the source image.

    Inside that folder you'll find a lockscreen.jpg and various other files with resolutions appended - one for the native resolution and a bunch of thumbnails. What we do is delete all the contents, and copy the correct image into place as lockscreen.jpg. Windows then seems to generate the rest as needed.

    This fix was needed for us on 1607 and 1703, but seems fixed in 1803 (we skipped 1709).

    See also this thread: https://social.technet.microsoft.com/Forums/en-US/9b01f9ec-85de-413c-bf4c-ac12599d46b4

    And this thread: https://social.technet.microsoft.com/Forums/en-US/b4e6074f-09ce-4d77-8102-ba7a1cd33088

    Monday, April 30, 2018 6:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Is anyone aware of a cache image location for the Lockscreen image that needs to be cleared or a command that  can be run to do this? Somehow windows is stuck using the old cached version of the image and we need a way to force it to use the new image.

    Yes, specifically here: C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P

    However, that folder is locked down and you won't be able to access it short of taking ownership and resetting the rights or accessing it from a process running as SYSTEM. In our case we use a scheduled task to do what's needed as system, and trigger it manually to refresh the cache after updating the source image.

    Inside that folder you'll find a lockscreen.jpg and various other files with resolutions appended - one for the native resolution and a bunch of thumbnails. What we do is delete all the contents, and copy the correct image into place as lockscreen.jpg. Windows then seems to generate the rest as needed.

    This fix was needed for us on 1607 and 1703, but seems fixed in 1803 (we skipped 1709).

    See also this thread: https://social.technet.microsoft.com/Forums/en-US/9b01f9ec-85de-413c-bf4c-ac12599d46b4

    And this thread: https://social.technet.microsoft.com/Forums/en-US/b4e6074f-09ce-4d77-8102-ba7a1cd33088

    Thanks so much, what a pain with the permissions on that directory. I used basically the same script in the other thread and it worked very well:

    # Take Permissions and Delete Windows SystemData Lockscreen cache images

    TAKEOWN /F C:\ProgramData\Microsoft\Windows\SystemData /r /d y

    ICACLS C:\ProgramData\Microsoft\Windows\SystemData /grant:r Administrators:F /T

    ICACLS C:\ProgramData\Microsoft\Windows\SystemData /setowner Administrators /T

    takeown /f C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P /r /d y

    icacls C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P\ /grant:r Administrators:F /T

    icacls C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P\ /setowner Administrators /T

    Remove-Item C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P\*.*

    #Copy new Image to folder GPO references

    Copy-Item $PSScriptRoot\img0.jpg C:\images\Lockscreen.jpg

    #Copy new Image to local lockscreen cache folder

    Copy-Item $PSScriptRoot\img0.jpg C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P\LockScreen.jpg


    Wednesday, May 2, 2018 10:36 PM