RECOMMENDED: Click here to fix Windows errors and optimize system performance
Windows 10 Enterprise Build 1703, which is the upgrade version of the Creator, is an improvement over previous versions. It has added many more features to the operating system. However, some users of this version have reported two major problems with the lock screen.
- Windows 10 lock screen is grayed out
- Windows 10 lock screen displays a black background.
If you are one of those facing this problem, this workstation provides some workarounds.
Windows 10 Lock Screen grayed
There is a Group Policy parameter, forcing a specific default lock screen under :
Computer ConfigurationAdministrative TemplatesControl PanelCustomization.
Many users cannot change settings.
This is due to the fact that another group policy setting can also enable Prevent changes to the lock screen and login screen . When this policy is enabled, the controls are grayed out below the Lock screen. You can see the lock screen and the screen, but you cannot make any changes. Look at the image below.
If the option Prevent lock screen and connection image policy change was not enabled, the lock screen would look like this.
A workaround would be to disable the group policy prevent changing the lock screen and login screen and set the updates to Force.
The Windows 10 Lock screen displays a black background
In this situation, the lock screen screen would be obscured without any difference from the other lock screen functions. Time, text, controls etc. would work as usual.
To verify and resolve the problem, search for performance options in the Windows search bar and search for the option Animate windows when you minimize and maximize.
Make sure this option is not checked.
You can also run gpedit.msc and navigate to the next setting :
Windows ComponentsDesktop Windows Manager Windows computer configuration management models.
If policy Do not allow Windows animations is enabled, disable it.
I hope this will help you.
Microsoft is aware of this problem and explained the problems in detail in a blog entry and published these workarounds. In fact, they issued an update on May 24, 2017 to correct these problems, but some still face this problem.