The procedure to set up automatic sign-in is easy:
Run control userpasswords2
or netplwiz
to open a special "User Accounts" dialog. Find the option "Users must enter a user name and password to use this computer". Uncheck this, then click OK and you will be prompted to enter credentials.
Windows 10 2004 has hidden this checkbox by default. To fix that, disable the "Require Windows Hello sign-in for Microsoft accounts" feature in the Settings app. If you can't find that (Windows 10 2009 a.k.a. 20H2), there are several ways forward. I'm documenting them all here for completeness:
reg ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\PasswordLess\Device" /v DevicePasswordLessBuildVersion /t REG_DWORD /d 0 /f
- Go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\PasswordLess\Device
- Find the
DevicePasswordLessBuildVersion
of typeREG_DWORD
. It is expected to have a value of2
. Set it to0
.
The checkbox should be restored, and the normal automatic sign-in procedure should be available.
This tool evidently sets up automatic sign-in without having to change the DevicePasswordLessBuildVersion
flag: https://docs.microsoft.com/en-us/sysinternals/downloads/autologon
If none of the above works, this probably won't either. But you can try editing the registry manually to configure automatic sign-in. This is the least secure option, because it puts your password into the registry in plain text whereas the previous options encrypt your password and store it elsewhere (I don't know where).
- Run
regedit
- Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
- Add string key
AutoAdminLogon
with value1
. - Add string key
DefaultDomainName
with value matching the computer's name. - Add string key
DefaultUserName
with value matching the user name you want to log in with automatically. - Add string key
DefaultPassword
with value matching the user's password.
If Resource Monitor tells you that System (often PID 4) is listening on the port you want, run netsh http show servicestate
to learn more about what is actually listening on your port. netstat -abn
is also supposed to be helpful, but not in my experience so far.
You can also look in the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters\UrlAclInfo
.
Access Current User's certificate store via certmgr.msc
or Local Machine's certificate store via certlm.msc
.
If the Windows GUI is not letting you change a public network to private, you can use Powershell.
Run PS as administrator.
Run Get-NetConnectionProfile
Run Set-NetConnectionProfile -Name "NetworkName" -NetworkCategory Private
(Replace NetworkName
with the value of the Name field shared by the previous command.)
-
Discover Interface Names:
netsh interface ipv4 show interface
-
Enable
dhcpstaticipcoexistence
:netsh interface ipv4 set interface interface="INTERFACE NAME" dhcpstaticipcoexistence=enabled
-
Add a static ip address:
netsh interface ipv4 add address "INTERFACE NAME" 192.168.x.xxx 255.255.255.0
Addresses added via this method are not expected to appear in the GUI. Instead, use ipconfig
or ipconfig /all
to see them.