W10 Logon Background

[Spence_101]

When setting a Windows 10 (education) logon background via

 

Computer Configuration > Administrative Templates > Control Panel > Personalization > Force a specific default lock screen and logon image

 

it works absolutely fine the first time. The logon image displays.

 

However, if I then replace the image (same name but different photo, for example), the workstations then just display a blue image as the logon screen image instead. No matter what I do, I cannot get it to update from the blue image, unless I revert back to the exact original image.

 

Anyone else come across this?

[BOOT]

Yes. If the filename doesn't change, it won't update the cached copy.

[Spence_101]

Yes. If the filename doesn't change, it won't update the cached copy.

 

I've tried changing the filename and updating the GPO with it, but still it shows the blue background.

[BOOT]

I use this in a startup PowerShell script:

 

icacls "C:\ProgramData\Microsoft\Windows\SystemData" /setowner "BUILTIN\Administrators" /T /C
icacls "C:\ProgramData\Microsoft\Windows\SystemData" /inheritance:e /T /C
icacls "C:\ProgramData\Microsoft\Windows\SystemData" /inheritance:d /C
icacls "C:\ProgramData\Microsoft\Windows\SystemData" /setowner "BUILTIN\Administrators" /T /C
icacls "C:\ProgramData\Microsoft\Windows\SystemData" /grant:r Administrators':'"(CI)(OI)(F)" /T /C
icacls "C:\ProgramData\Microsoft\Windows\SystemData" /grant SYSTEM':'"(CI)(OI)(F)" /T /C
Remove-Item -Path "C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P\*" -Force

Allows me to customise the image to add announcements, etc.

[Spence_101]

I use this in a startup PowerShell script:

 

icacls "C:\ProgramData\Microsoft\Windows\SystemData" /setowner "BUILTIN\Administrators" /T /C
icacls "C:\ProgramData\Microsoft\Windows\SystemData" /inheritance:e /T /C
icacls "C:\ProgramData\Microsoft\Windows\SystemData" /inheritance:d /C
icacls "C:\ProgramData\Microsoft\Windows\SystemData" /setowner "BUILTIN\Administrators" /T /C
icacls "C:\ProgramData\Microsoft\Windows\SystemData" /grant:r Administrators':'"(CI)(OI)(F)" /T /C
icacls "C:\ProgramData\Microsoft\Windows\SystemData" /grant SYSTEM':'"(CI)(OI)(F)" /T /C
Remove-Item -Path "C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P\*" -Force

Allows me to customise the image to add announcements, etc.

 

Thanks - I'm now trying this but still struggling to get anything other than a blue background appearing on the log-in screen. Where is the wallpaper located that you point the policy to?

[Oaktech]

I've found that the stock method won't change the image upon request, it has to do it on a background refresh, although some times logging into the machine and doing Win+L will force it from the blue screen to the one it's supposed to be.

[Spence_101]

I've found that the stock method won't change the image upon request, it has to do it on a background refresh, although some times logging into the machine and doing Win+L will force it from the blue screen to the one it's supposed to be.

 

Been a few days now and nothing has changed

[Warwick_Tech]

When setting a Windows 10 (education) logon background via

 

Computer Configuration > Administrative Templates > Control Panel > Personalization > Force a specific default lock screen and logon image

 

it works absolutely fine the first time. The logon image displays.

 

However, if I then replace the image (same name but different photo, for example), the workstations then just display a blue image as the logon screen image instead. No matter what I do, I cannot get it to update from the blue image, unless I revert back to the exact original image.

 

Anyone else come across this?

 

We found windows only likes one image and to change it we had to point the image to a network share, not changing the name, filesize anything worked - except the network share; so that's now where our lock screens live.

[Spence_101]

We found windows only likes one image and to change it we had to point the image to a network share, not changing the name, filesize anything worked - except the network share; so that's now where our lock screens live.

 

So just to clarify, the filesize and the name had to be the same as the original image??

[Warwick_Tech]

No, that's what we tried but nothing worked - Only pointing the GPO to a network share image seemed to force a refresh

[Spence_101]

No, that's what we tried but nothing worked - Only pointing the GPO to a network share image seemed to force a refresh

 

Ah ok. We have ours on a network share but still it won't update to a different image. I've tried both local and network to no avail.

Edited June 6, 2019 by Spence_101

[BOOT]

I've not tried a network share, only using a local .png image.

[mproffitt1983]

We had issues before when using C:\windows\Web\Wallpaper and not using the default img0.jpg. We moved wallpapers to \\domain\netlogon\wallpaper and all works well.

[Spence_101]

We had issues before when using C:\windows\Web\Wallpaper and not using the default img0.jpg. We moved wallpapers to \\domain\netlogon\wallpaper and all works well.

 

Have you tried changing the wallpaper now? Does it update or just display a blank blue image?

 

If it works fine - do you do anything else with regards to the logon wallpaper? Permissions/registry etc.

 

We're using \\domain\netlogon\wallpaper and as I mentioned in the original post, it's fine the first time but if we change or update the image it just displays a blank blue image on the machines instead.

[sonofsanta]

You can keep the same filename, but everytime you replace it, it has to be with a file that has a newer Date Modified timestamp--to the point I have to open up Photoshop and resave it if I want to change the image. PITA, and took me ages to realise that was what was happening, but there it is. Windows: it never did make much sense.

[mproffitt1983]

Yes, we changed the wallpaper last week with no issues. We also edited the wallpaper a few days later as staff complained that it was too bright. This also updated without issue.

 

There are no special permissions or registry changes. The only other thing our Wallpaper GPO has is 'Turn off fun facts, tips, tricks, and more on lock screen' but that's not really relevant.

 

Humor me for a minute. What happens when you log in as a new user with no profile and the log off or lock screen?

[Spence_101]

You can keep the same filename, but everytime you replace it, it has to be with a file that has a newer Date Modified timestamp--to the point I have to open up Photoshop and resave it if I want to change the image. PITA, and took me ages to realise that was what was happening, but there it is. Windows: it never did make much sense.

 

Thanks for posting - I've just tried this but still it won't update!

 

Do you do anything else like removing the C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P files etc?

[Spence_101]

Yes, we changed the wallpaper last week with no issues. We also edited the wallpaper a few days later as staff complained that it was too bright. This also updated without issue.

 

There are no special permissions or registry changes. The only other thing our Wallpaper GPO has is 'Turn off fun facts, tips, tricks, and more on lock screen' but that's not really relevant.

 

Humor me for a minute. What happens when you log in as a new user with no profile and the log off or lock screen?

 

After editing the wallpaper and rebooting, if we then log on a user and go to lock, it's still the blue image background.

Edited June 7, 2019 by Spence_101

[sonofsanta]

Thanks for posting - I've just tried this but still it won't update!

 

Do you do anything else like removing the C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P files etc?

 

Nothing like that--just the GPO Force a specific default lock screen and logon image set to Enabled with a local path, and a group policy preference to push the file over (which, now I think about it, might be the source of needing the Date Modified stamp to be later... d'oh*). Only takes effect after someone has logged on & off, or restarted; it won't refresh a screen already at logon.

 

*ETA: maybe not. Already set to Replace, so idk ¯\_(ツ)_/¯

Edited June 7, 2019 by sonofsanta

[Boredguy]

We just set our lockscreen/logon wallpaper into C:\Windows\System32\oobe\info\backgrounds, called backgroundDefault.jpg and that path is set in the GPO.

 

Works fine, but does need a 2nd reboot or a logon/off for the fortnightly change to display

[Spence_101]

We just set our lockscreen/logon wallpaper into C:\Windows\System32\oobe\info\backgrounds, called backgroundDefault.jpg and that path is set in the GPO.

 

Works fine, but does need a 2nd reboot or a logon/off for the fortnightly change to display

 

Can I ask what Windows 10 version you are using? .\info\backgrounds doesn't appear to exist for us... so presume you are creating this?

[DJ-1701]

Can I ask what Windows 10 version you are using? .\info\backgrounds doesn't appear to exist for us... so presume you are creating this?

 

Windows 10 Education.

 

The folder does not exist, no, but it was the original folder documented for Windows 7 login wallpaper (https://www.askvg.com/windows-7-supports-login-screen-customization-without-3rd-party-software-how-to-instructions-inside/), so that's why we use that path still with Windows 10, historic reasons.

[Spence_101]

Now struggling to get it to display anything other than the stock caves picture!

[Spence_101]

Managed to sort it (working on both 1809 & 1903) by applying these reg keys I found on Reddit (I've added the below to our startup script):

 

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\PersonalizationCSP

 

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\PersonalizationCSP /v LockScreenImagePath /t REG_SZ /d "\\server\NETLOGON\W10LogonScreen.jpg" /f

 

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\PersonalizationCSP /v LockScreenImageUrl /t REG_SZ /d "\\server\NETLOGON\W10LogonScreen.jpg" /f

 

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\PersonalizationCSP /v LockScreenImageStatus /t REG_DWORD /d 1 /f

 

Also having Computer Configuration > Administrative Templates > Control Panel > Personalization > Force a specific default lock screen and logon image set.

 

Thought I'd share for anyone struggling. Also works fine if you update/change the image. Simply replace the file \\server\NETLOGON\W10LogonScreen.jpg

Edited June 24, 2019 by Spence_101

[5nowman]

Managed to sort it (working on both 1809 & 1903) by applying these reg keys I found on Reddit (I've added the below to our startup script):

 

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\PersonalizationCSP

 

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\PersonalizationCSP /v LockScreenImagePath /t REG_SZ /d "\\server\NETLOGON\W10LogonScreen.jpg" /f

 

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\PersonalizationCSP /v LockScreenImageUrl /t REG_SZ /d "\\server\NETLOGON\W10LogonScreen.jpg" /f

 

REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\PersonalizationCSP /v LockScreenImageStatus /t REG_DWORD /d 1 /f

 

Also having Computer Configuration > Administrative Templates > Control Panel > Personalization > Force a specific default lock screen and logon image set.

 

Thought I'd share for anyone struggling. Also works fine if you update/change the image. Simply replace the file \\server\NETLOGON\W10LogonScreen.jpg

 

This is madness.

 

what happens when the server goes off? do backgrounds show in real time?

 

I even tried setting the lock screen wallpaper to \\localhost\c$\wallpapers\MainScreen.jpg no joy.

 

The Lock Screen GPO even states c:\ ... as a path for the jpg.

 

Thank you for the information. I will set these reg fixes. setting up a clean system and now I have to dirty it by reg fixes. Everything should be doable with GPOs without reg fixes