If you’re a Windows 10 user, you probably have the familiar login screen with your username and password. If you’re a Windows 11 user, there’s a new way to log in automatically. To do this, open the Start menu and type “netlogon” into the search bar. Once you’ve found it, click on it. You’ll now be taken to a new window that looks like this: You’ll need to enter your username and password for both accounts. After you’ve done that, your login screen should look like this: Now that you’re logged in automatically, all of your settings and preferences will be preserved from previous versions of Windows 10 or Windows 11.


If your PC never leaves your home and you don’t really need a password, automatically logging in will save you the trouble of typing in your password every single time you turn on or restart your PC. Here’s everything you need to know to enable auto login.

You Generally Shouldn’t Use Auto Login

Automatically signing in potentially exposes your sensitive data to anyone that has physical access to your PC. It isn’t as bad as completely removing your Windows 11 password, but it still presents an unnecessary risk.

RELATED: How to Remove Your Windows 10 Password

Anyone with physical access to your PC will likely have full administrative control, which means they can recover your Microsoft password if they really want to. From there, it is a simple matter to gain access to your Microsoft account and everything stored there.

RELATED: Why You Shouldn’t Automatically Log Into Your Windows PC

If you’re going to use automatic login, we recommend you use a local account instead.

If you just don’t like having to type a password, consider using Windows Hello webcam sign-in instead.

Enable the Option to Bypass Sign-in

Windows 11 still supports automatic sign-in — the option is just disabled by default. We’ll need to use the Registry Editor (Regedit) to tweak a few things to enable it again. Alternatively, you can just download and use the registry key we provide, “Enable_Automatic_Login_Option.zip,” in the next section. It’ll handle everything automatically.

Click the Start button, type “regedit” into the search bar, then hit Enter or click “Open.”

Navigate to the following address by pasting it into Regedit’s address bar:

Double-click the DWORD named “DevicePasswordLessBuildVersion,” change the Value Data from “2” to “0”, then click “OK.”

Changing the value from 2 to 0 is what enables automatic login. Our work on the registry is done, and you can close Regedit.

Use Our Registry Hack to Enable the Option Instead

If you don’t want to mess with the registry manually, you can use our pre-made REG file to apply the change automatically. Just download “Enable_Automatic_Login_Option.zip,” open it up in your favorite file archiving program, and double-click “Enable_Automatic_Login_Option.reg.” There is also a “Disable” file included in the ZIP file to undo the change in case you change your mind.

Download Enable_Automatic_Login_Option.zip

You’ll get a popup warning you that REG files can be harmful to your PC — that is true. A malicious REG file could cause a ton of problems. You can always audit a REG file to determine what it does by opening it up in a plain text editor, like Visual Studio Code, Atom, Notepad, Notepad++, or countless others.

In this case, however, the REG file does only what we outlined above, so just click “Yes.”

Enable Automatic Sign-in

Modifying the registry was the hard part of this job. Now you just need to enable local login. Hit Windows+R to open the run window, type “netplwiz” into the field, then hit Enter or click “OK.”

Select your account, untick the box next to “Users Must Enter A User Name and Password To Use This Computer,” and then click “Apply.”

You need to enter your username and password on the next screen. If you’re using a Microsoft account to log in to Windows, the password you need to provide is your Microsoft password.

That is it — you’re done. The next time you restart your computer, you’ll automatically log directly into your chosen account. Just keep in mind the security implications.