Logon / Lock Screen Background Not Applying

[rls2k5]

Hi,

 

I've been following Edugeek for years, but this is my first post.

 

We are using Windows 10 LTSB enterprise 1607 for the bulk of our PCs and are greeted with a blue screen at login on recently deployed computers.

 

We have recently updated our deployment image (just the standard image with updates embedded in the WIM file from WSUS to speed up deployment for MDT).

 

The PCs this image has been deployed on show the blue login screen, the PCs with the old image (all the same updates from the same WSUS server applied over time) show the correct logon background. We also have a couple of office PCs on enterprise 1803 with all updates from WSUS in the WIM file and these also show the login background correctly.

 

The new image PCs show the correct location for the logon background in rsop and the registry but for some reason it doesn't apply. We have tried things posted elsewhere on here such as taking ownership of folders to change permissions and we have tried copying the windows.login.ui.pri file from a pc with the old image to no avail. We don't think the issue relates to group policy as it successfully applies on all other images but have tried both UNC and local paths for the image.

 

Does anyone know a fix for this issue? The school colours aren't blue (and don't want to open the logon colour can of worms as that appears even worse than the logon background) Any hints would be greatly appreciated.

[FN-GM]

We have the same issue. I haven't found a proper fix but a dirty fix is:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Personalization

NoChangingLockScreen = 0

 

Reboot after this.

 

Sometimes takes more than 1 attempt.

 

I need a proper fix really.

[BuckyBadger]

We ran into a similar issue with our old 1607 machines and if I remember right, the problem was introduced by a patch. I want to say it was the March or April rollup. One of my co-workers came up with a workaround by tossing the image into the cache or something with SCCM. Thankfully, the problem isn't there in 1803.

[BuckyBadger]

We ran into a similar issue with our old 1607 machines and if I remember right, the problem was introduced by a patch. I want to say it was the March or April rollup. One of my co-workers came up with a workaround by tossing the image into the cache or something with SCCM. Thankfully, the problem isn't there in 1803.

I think it was this one:

 

https://support.microsoft.com/en-us/help/4088889

 

In particular:

 

Addresses issue where customers can't change the lock screen image from the Settings app. This occurs if the "Force a specific default lock screen and logon image" Group Policy is turned on and the "Prevent changing lock screen and logon image" Group Policy is turned off.

[ADMaster]

I replace the image during OSD no permission changes needed then as it's done as system.

I think it was 1703 that changed it. I used to replace img100.jpg but aslo need to replace img103.png in 1703+.

Don't quote me on exact numbers but hopefully that gets you in the right place. I can verify when I'm back in work if someone else hasn't before then.

[supportman]

I replace the image during OSD no permission changes needed then as it's done as system.

I think it was 1703 that changed it. I used to replace img100.jpg but aslo need to replace img103.png in 1703+.

Don't quote me on exact numbers but hopefully that gets you in the right place. I can verify when I'm back in work if someone else hasn't before then.

This is driving me a bit crazy, i've changed the img100.jpg files in c:\windows\web but always get the cave image. Any ideas which file you actually changed?

I'm trying to change the lock screen on our basic image, no group policies or regedits. Using build 1803

Edited July 11, 2018 by supportman

[Oaktech]

I've had to remove the group policy cache on some machines to make it update - delete the contents of c:\windows\system32\grouppolicy folder and then reboot.

[supportman]

I've had to remove the group policy cache on some machines to make it update - delete the contents of c:\windows\system32\grouppolicy folder and then reboot.

 

Thanks tried that but didn't work, I still get a blue empty screen, seems like Microsoft broke it in their most recent 1803 build! Unbelievable!!

 

https://social.technet.microsoft.com/Forums/en-US/1664b0ab-f1d8-4e60-8337-13f079a33752/windows-10-1803-custom-loginlock-screen-image-is-not-applied-until-a-user-logs-in?forum=win10itprosetup