Disable or Enable the Windows Server 2012 Lock Screen
To disable or enable the lock screen in Windows Server 2012, configure the policy named Do not display the lock screen in Local Group Policy Editor or a domain policy. Set it to Enabled to skip the lock screen, or Disabled (or Not Configured) to allow it; the setting affects the lock screen, not whether users must sign in.
What the lock screen does
The lock screen is the screen shown before the sign-in prompt when Windows is locked or starts a session. On a server, it can appear after a user presses Ctrl+Alt+Delete and chooses Lock, after a session is disconnected, or when a configured inactivity timeout locks the session. It may show a background image and status information before the user proceeds to sign in.
Disabling this screen removes that preliminary display in the applicable cases. It does not turn off the Windows sign-in process, remove user passwords, or automatically keep a session unlocked. Those are separate controls. In particular, a policy that controls the lock screen should not be mistaken for a policy that controls whether a password is required after a screen saver or sleep state.
Disable the lock screen with Local Group Policy
Use the Local Group Policy Editor when you are changing the behavior of one server and local policy is appropriate. You need administrative rights to change the setting.
- Sign in to the server with an account that can administer its policy.
- Press Windows key + R, enter
gpedit.msc, and press Enter. - In the editor, go to Computer Configuration > Administrative Templates > Control Panel > Personalization.
- Open Do not display the lock screen.
- Select Enabled to disable the lock screen, then select Apply and OK.
- Update policy from an elevated Command Prompt with
gpupdate /force, or wait for policy to refresh. Lock and unlock the session, or sign out and back in, to check the result.
The wording can sound counterintuitive: enabling “Do not display the lock screen” means the lock screen is suppressed. If the setting is not present in the editor, confirm that you are on the expected Windows Server edition and that the administrative templates are available and current for the system.
Enable the lock screen again
To restore the lock screen through the same policy, return to Do not display the lock screen and choose Disabled. Choosing Not Configured removes the local policy preference and lets other applicable policy determine the behavior. If no higher-precedence policy disables the screen, the normal lock-screen behavior is allowed.
After changing the setting, apply policy with gpupdate /force and test a fresh lock or sign-in. A currently displayed screen may not change immediately just because a policy was edited. Also check the actual sign-in experience rather than assuming that a wallpaper or personalization change proves the policy worked.
Managing the setting with domain policy
Servers joined to a domain may receive computer settings from Group Policy Objects (GPOs). A domain policy can override a local setting, so changing Local Group Policy may appear to have no effect or may work only temporarily. For a server managed centrally, use the organization’s approved process to identify the GPO that applies to the server and change its setting there, rather than repeatedly editing the local policy.
Administrators can use gpresult /h followed by a report filename, such as gpresult /h C:\gp-report.html, from an elevated command prompt to create a Group Policy results report. Review the report to identify applied policies and their source. In a domain environment, consult the policy administrator before changing a shared GPO: it may affect multiple computers, not just one server.
Lock screen policy versus sign-in and inactivity settings
These controls solve different problems. The lock screen policy changes the preliminary screen; it does not determine the security requirements for unlocking an account. If your goal is to avoid leaving a server session accessible when unattended, keep the distinction clear and review the organization’s sign-in and session policies separately.
- Lock screen display: controlled by Do not display the lock screen under Personalization policy.
- Password after a screen saver: controlled by screen-saver settings and related password-protection policies.
- Automatic locking: can be caused by inactivity limits, screen-saver behavior, or other organization settings.
- Remote Desktop sessions: disconnection and session time limits are separate from whether the lock screen is shown.
For example, suppressing the lock screen does not necessarily prevent a server from locking after inactivity. Conversely, changing an inactivity timeout does not necessarily remove the lock screen shown when someone deliberately locks the computer. Diagnose the specific behavior before changing multiple settings.
Common problems and checks
If the lock screen remains after setting the policy to Enabled, first verify that you edited the correct computer policy path and selected the policy’s Enabled option—not Disabled. Then run gpupdate /force and check the Group Policy results report for a domain policy that takes precedence. A policy refresh does not always change a screen already in progress, so test by locking the session again.
If the setting is missing or the editor cannot be opened, confirm that you are using an account with the needed administrative permissions and that Local Group Policy Editor is available in that installation. Some Windows Server configurations are managed through domain policy instead. Avoid editing undocumented registry values as a first workaround; policy-based configuration is easier to review and reverse.
Windows Server 2012 and Windows Server 2012 R2 are older releases. Where they remain in use, follow the organization’s maintenance and security procedures; changing the lock screen is not a substitute for keeping server software supported and appropriately managed.
Frequently Asked Questions
Does disabling the lock screen disable the password?
No. The policy suppresses the lock screen display; it does not remove account passwords or by itself eliminate sign-in requirements.
Which option disables the lock screen?
Set Do not display the lock screen to Enabled under Computer Configuration > Administrative Templates > Control Panel > Personalization.
How do I turn the lock screen back on?
Set that policy to Disabled, or use Not Configured if you want local policy to stop specifying a value. A domain policy may still control the result.
Why does the setting keep changing back?
A domain GPO or other centrally managed policy may reapply its setting. Check the Group Policy results report and have the responsible administrator review the applicable policy.
Will this stop an idle server from locking?
Not necessarily. Inactivity, screen-saver, and Remote Desktop session policies are separate. Review those settings if the issue is automatic locking rather than the lock screen itself.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.