There are a few open issues with Lock screen setting on Windows 10 Enterprise build 1703 (Creator's Update)
Resolved: The first is with the Group Policy setting "Force a specific default lock screen image" under
Computer Configuration\Administrative Templates\Control Panel\Personalization
In many cases trying to enabled, change or update this doesnâ€™t appear to work for new or existing users in the environment.
This will happen if "Prevent changing lock screen and logon image" policy is also enabled.
One of the key indicators of this is when you see the desired lock screen image in Settings under Lock screen as the preview but the controls to change are greyed out.
Many people have sent me that screen shot and said - "See, that's the image I want to appear!" not noting that since its greyed out it also means the "Prevent" lock screen is in play. When Prevent is disabled it should look like this:
This issue is fixed in beta builds and an update released last week in May KB4020102
The workaround is to set "Prevent" to Disabled or Not Configured, apply that change and then make the desired updates to "Force". If there are still issues with Force at this point, test applying it in an OU that blocks inheritance for all other polices to confirm there isn't something else in play.
The "Force" policy does work by default, with no other policies enabled.
The second issue is when Animate settings are changed on the system, the Lock Screen will be black. The time and other text will appear normally, the lock screen with work normally, users will just see black instead of the desired picture.
The setting specifically, under Advance System Settings, Settings under Performance - Animate window minimizing and maximizing is unchecked.
Or when the policy "Do not allow Windows animations" is enabled under
Computer Configuration\Windows Components\Desktop Windows Manager
The workaround for this one is to not enable the policy or uncheck the setting.
This issue was present in 1607 and fixed with the last February Cumulative update but the issue seems to have returned in 1703 and we're currently investigating it.
Additional issues 7/7/2017:
The fix for the first issue implemented new image cache and algorithm. Initially, when "Prevent..." was applied it would block any changes made to "Force..." policy. After the May update this has changed and may have some side effects. Some reports I'm seeing are:
- This is not reproducible 100% of the time.
- Some machines will work and some will not with the same settings.
- Resetting the policies to Not Configured and reenabling does not resolve the behavior
- Some users report this issue without any Group Policies, users not able to change it via Settings
- Changing the location of the lock screen image on the system may work
- Lock screen reverts/changes to Cave after resolution change
- Lock screen behavior is inconsistent when Docked vs Undocked
These symptoms are not all a result of the May update and are not necessarily all the same issue but one issue that we are working on is with the new image cache implementation. The workaround for this issue is:
- Copy the image you want to a second path and update the policy with the new path.
- Update the Last Modify Timestamp of the image referenced in the policy.
- Backup and delete the folder C:\ProgramData\Microsoft\Windows\SystemData\S-1-5-18\ReadOnly\LockScreen_P
Just got word this secondary issue to the custom image is in RS3 builds now which means it should be in the Fall release (barring any last minute issues)
Hope that helps!