Log in Stuck Archives

Windows 10 is an operating system first released by Microsoft in 2015 which today is the most widely used system on desktops and laptops. It has several outstanding features that makes it easy to do various computing tasks. Although this is a solid performing software there are instances when certain issues can occur which we will be addressing today. In this latest installment of our troubleshooting series we will tackle the windows 10 stuck in login screen problem. https://youtu.be/2iGCN8CHJ0Q Fix Windows 10 that’s stuck or frozen in login screen Before performing any of the recommended troubleshooting steps listed below it’s best to restart your computer and router first. This action refreshes the operating system and remove any corrupt temporary data that could be causing the problem. Unplug external devices The first thing you will need to do is to unplug the external devices from your computer. Anything connected to the USB ports must be removed. Turn off the computer then only plug in the keyboard and mouse. When you turn on the computer try to check if you can get past the login screen. If the problem doesn’t occur then plug in the devices one at a time while checking if any of them is causing the problem. Boot in Safe Mode To check if the problem is caused by a driver issue you will need to start the computer in Safe Mode. Click on Start buttonSelect SettingsClick Update & SecuritySelect RecoveryGo to Advanced startupClick Restart nowSelect Troubleshoot from the Choose an Option screen, then click Advanced optionsGo to Startup Settings and click RestartOnce your computer restarts, a list of options will come up.Choose 4 or F4 to start your computer in Safe Mode If the Windows 10 can’t get past login screen issue does not occur in this mode then the problem is not caused by the drivers or basic computer settings. Since you are already in this mode you can try to run an SFC scan to fix any corrupted or missing system files that could be causing the problem. Go to the search field box and type CMDSelect Command PromptRight click and select Run as AdministratorOn the command prompt window Type "sfc/scannow" then press Enter.Restart the computer once the process is complete. You can also use the DISM tool while in Safe Mode. Go to the search field box and type CMDSelect Command PromptRight click and select Run as AdministratorType Dism /Online /Cleanup-Image /RestoreHealthOnce the repair is complete, Reboot your computer Check if the Windows 10 stuck in login screen problem still occurs. Perform a clean boot To check if a software installed in your computer is causing the problem you will have to do a clean boot. Go to the Search boxType msconfigSelect System ConfigurationFind Services tabSelect Hide all Microsoft services boxClick Disable allGo to Startup tabClick Open Task ManagerClose Task manager then click OKReboot your computer If the issue does not occur then there’s a possibility that the problem is caused by a software installed in your computer. The best way to find out what is causing the problem is to re-enable half of the services. Re-enable the top half of all non-Microsoft services then restart your computer. Test to see if the issue still occurs. If it doesn’t then re-enable the bottom half of all non-Microsoft services instead. Restart your PC, and check if the issue occurs. Start to narrow down the search. Keep unchecking services and restarting your PC. Once you find that the issue is gone, you should be able to find the culprit. Once you have found the culprit it’s time to set your computer to boot normally. Type msconfig in the search bar and open the System Configuration app that appears.Click Services.Click the checkbox next to Hide all Microsoft services.Click Enable all.Click the checkbox next to the offending startup service.Click Startup.Click Open Task Manager.Click a Startup Program.Click Enable. Repeat this for all startup programs.Click the X to close Task Manager.Click OK in the System Configuration window.Click Restart. Check if Windows 10 freezes in login screen issue still occurs.