Before following the steps described in this article, make sure that the basic autologin settings are in place:
After following the above steps, test the auto-login functionality - check How to troubleshoot Autologin
Only in case auto-login does not work, go on with the rest.
In case the CTRL+ALT+DEL keyboard combination is normally required for a user to manually log in, then make the following changes.
- Open Local Group Policy Editor and go to "Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Interactive logon: Do not require CTRL+ALT+DEL".
- Set the option to ENABLED.
- Open Local Group Policy Editor and go to "Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment > Allow log on locally".
- Both the specific User that performs the autologin and the user’s Group should be added into the "Allow log on locally" policy.
For Windows Servers
In case you are working on a Windows Server machine and the option to "Add User or Group" is unavailable:
- Launch the Server Manager
- Navigate to "Tools>Group Policy Management".
- In the Group Policy Management window, navigate to "Forest: > Current Domain > Domains > CurrentDomain.loc > Domain Controllers > Default Domain Controllers Policy"
- Right-click Default Domain Controller Policy and select “Edit”. This will bring up the Group Policy Management Editor, with “Default Domain Controller Policy” tree loaded.
- Navigate to "Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > User Rights Assignment > Allow log on locally"
- Add both the specific User that performs the autologin and the user’s Group.
- Open Local Group Policy Editor and go to "Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Windows Logon Options > Disable or enable software Secure Attention Sequence".
- Enable the “Secure Attention Sequence” Policy” setting the “Services” as the Option
In case the machine is registered in an Active Directory, there is the chance that the machine lost trust with the AD - the AD does not recognize the machine. In order to resolve the issue, remove the computer from the AD and register it back again.
Manually log in to the console session of the machine once. You can see the session that you are currently working on by running the CMD command "query session".
If you normally log in through RDP to your VM, then you would need to log in through the Hypervisor of the VM in order to access the console session.
- Go to "C:\Windows\System32" and check if the "WACP.dll" for WinAutomation or "PRCP.dll" for ProcessRobot exists.
In case it is absent, it should be
- Copied to the aforementioned directory.
- Registered in the Windows Registry.
Contact email@example.com to assist you with the last step.