How to Enable or Disable the Require Sign-in on Wakeup Setting in Windows 11

IT environments have strict policies when it comes to device log-in and other related actions. For example, it’s common in corporate setups to have employees confirm their credentials every now and again, especially if they’ve been away from their workstation for an extended period.

If you’d like to implement this within your own network, this guide offers several options on how to require a PC login after waking from sleep.

Methods for changing sign-in on wakeup preferences

Use the table to choose and quickly navigate to your preferred activation steps.

💡 Tip: Check out the Things to look out for section to optimize your action plan and manage risks.

Method 1: Configure Sign-in options via Settings

This method is best for self-service or Remote Desktop Protocol configuration.

📌 Use cases: For remote activation and self-service.

📌 Prerequisites: Requires system access.

1. Open Settings from Search 🔎 or press Win + I.
2. Navigate to Accounts → Sign-in options.
3. Under Additional settings, find If you’ve been away, when should Windows require you to sign in again? to manage your preferences.
4. Choose Everytime or Never from the drop-down list.

This setting applies to the current user only and takes effect immediately.

Method 2: Configure Sign-in options via GPO

GPO management tools are commonly used for enterprise-level deployments.

📌 Use cases: For enterprise and system-wide deployments.

📌 Prerequisites: Requires GPO access (Windows 11 Pro, Enterprise, or Education).

1. Press Win + R, type gpedit.msc, and tap OK to open Local Group Policy Editor.
2. Navigate to Computer Configuration → Administrative Templates → System → Power Management → Sleep Settings.
3. Double-click Require a password when a computer wakes (on battery).
4. Set to Enabled or Disabled based on your preference. Repeat for (on AC power) if applicable.

You can run the gpupdate /force command to apply the changes immediately. Otherwise, the new settings will be applied on the next interval.

💡 Tip: Looking for a guide? Check out this GPUpdate video demonstration.

Method 3: Configure Sign-in options via Registry Editor

These steps can be used by advanced users to configure personal and managed devices. It’s also an excellent alternative for systems without GPO access.

📌 Use cases: For personal and system-wide deployments; RMM distribution.

📌 Prerequisite: This setting only applies if the device supports Modern Standby.

1. Press Win + R, type regedit, and tap OK to open the Registry Editor.
2. Navigate to or copy and paste the following path to the Registry address bar.

HKEY_CURRENT_USER\Control Panel\Desktop

Create the required key if the path is incomplete.

3. Modify or create the DelayLockInterval DWORD (32-bit) value.
4. Open it and set its Value data according to your preferences.
   • ffffffff = Do not require password.
   • 00000000 = Require password every time.
5. Restart the system or use powercfg /setactive to apply the active plan settings.

⚠️ Warning: Editing the registry can cause system issues. Create a backup before proceeding. Check out the video demonstration here.

Method 4: Set Configure Sign-in options via PowerShell script

PowerShell scripts are often used for task automation and software deployment.

📌 Use case: For automation and RMM scripting.

📌 Prerequisite: Requires network and system access.

(A) PowerShell script to disable sign-in on wake for all users

1. Open PowerShell from Search 🔎 and select Run as administrator.
2. Use the following command:

powercfg /SETDCVALUEINDEX SCHEME_CURRENT SUB_NONE CONSOLELOCK 0

powercfg /SETACVALUEINDEX SCHEME_CURRENT SUB_NONE CONSOLELOCK 0

powercfg /SETACTIVE SCHEME_CURRENT

(B) PowerShell script to enable sign-in on wake for all users

1. Open PowerShell from Search 🔎 and select Run as administrator.
2. Use the following command:

powercfg /SETDCVALUEINDEX SCHEME_CURRENT SUB_NONE CONSOLELOCK 0

powercfg /SETACVALUEINDEX SCHEME_CURRENT SUB_NONE CONSOLELOCK 0

powercfg /SETACTIVE SCHEME_CURRENT

💡 Note: This script may run or fail without displaying any confirmation or prompt. To verify that changes have been applied successfully, please check the corresponding Registry keys or system settings.

Things to look out for when you remove the login requirement on wake up

Missing something? Consider these scenarios and tips for handling errors, preventing system issues, and reinforcing policies.

💡 Tip: When Fingerprint or facial recognition is enabled via Windows Hello, the If you’ve been away, when should Windows require you to sign in again? will be greyed out. A security policy may also prevent users from changing preferences.

Best practices for managing the require sign-in on wakeup setting

Configuring devices to require a username at login or wake from sleep adds a simple but crucial layer of security. On the other hand, switching off this spontaneous access, while convenient, is a security risk in high-risk and shared environments.

It’s highly recommended to have this option enabled in shared devices, training environments, kiosks, and business settings. This feature improves data security by default and limits unauthorized access. In lieu of passwords, you can encourage users to use PINs or biometrics to speed up device log-in without compromising security.

Related topics:

• How To Force Password Change at Next Sign-in in Windows 10 and Windows 11
• How to Add or Remove the Sign Out Option from the Start Menu in Windows 10/11
• Enable or Disable Sign in with Picture Password in Windows 10
• How to Change System Unattended Sleep Timeout in Windows
• Mastering Windows Power Management: A PowerShell Guide for IT Pros and MSPs