There are two open issues with Lock screen setting on Windows 10 Enterprise build 1703 (Creator’s Update)
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 will be rolled into a monthly cumulative update soon.
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.
Which means if it still fails to apply after “Prevent” is Not Enabled, we need to investigate that behavior.
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.
I’ll post updates once new information is available.
If you do see issues with lock screen please confirm you’re not running into these two and let us know by filing an issue with exact repro steps through Feedback Hub.
Hope that helps!