Updated to Win 20H2 but can not sign in to my local account

Page 1 of 3 123 LastLast
  1. happyheart's Avatar
    Posts : 21
    Win 10 Home x64 v. 1903 (Build 18362.1440)
       #1

    Updated to Win 20H2 but can not sign in to my local account


    Just updated through Windows Update to 20H2. I have only two accounts, both local. My primary login picture, name and sign-in screen come up as normal, but whether I enter my pin or password - it starts with 'Welcome' but immediately signs out. The other local account works just fine. But all my stuff is in my primary login. Please, how can I fix this?
      My Computer

  2. dalchina's Avatar
    Posts : 32,541
    Win 10 Pro (1903) (2nd PC is 21H1)
       #2

    Hi, this suggests there was some corruption before you upgraded, or that affected the upgrade.

    Please run the following basic checks:
    a. Download, install and run Hard Disk Sentinel (functional trial) - valid for SSDs too. Instand appraisal of disks right on its GUI.
    b. If ok, from an admin command or Powershell prompt run
    chkdsk c: /scan

    Report whether this passes.

    If ok, you might try this:
    Windows 10 signing me out immediately after logging in
      My Computers

  3. happyheart's Avatar
    Posts : 21
    Win 10 Home x64 v. 1903 (Build 18362.1440)
    Thread Starter
       #3

    Thank you very much for getting back to me on this. I appreciate it!

    dalchina said:
    Hi, this suggests there was some corruption before you upgraded, or that affected the upgrade.
    Please run the following basic checks:
    a. Download, install and run Hard Disk Sentinel (functional trial) - valid for SSDs too. Instand appraisal of disks right on its GUI.
    b. If ok, from an admin command or Powershell prompt run
    chkdsk c: /scan
    Report whether this passes.

    All the scans & tests came out perfect. No problems shown. I attached the results of each, plus I ran a sfc/ scannow just for good measure, which is also attached.

    dalchina said:
    The article you referred to above says it is a 'new user' sign-in problem. My user was the first user created many years ago. So I'm uncertain as to whether I should try the solution

    Also, in that article it says, "Here we need to check on the values of two values—Shell and Userinit. It should be as following.
    • Shell = explorer.exe
    • Userinit = C:\WINDOWS\system32\userinit.exe

    Double click on them to open in edit mode, and then add these values.
    Restart the computer in normal mode, and try to login with a new user account."

    Well, "...then add these values.", it doesn't show what values to add...

    Please let me know your thoughts. Thank you again for your help. :)

    - - - Updated - - -

    Just for kicks, I booted into safe mode and I was able to sign in perfectly. What does that mean?
      My Computer

  4. Try3's Avatar
    Posts : 9,153
    Windows 10 Home x64 Version 21H2 Build 19044.1237
       #4

    happyheart said:
    … in that article it says, "Here we need to check on the values of two values—Shell and Userinit. It should be as following.
    •Shell = explorer.exe
    •Userinit = C:\WINDOWS\system32\userinit.exe
    Double click on them to open in edit mode, and then add these values.
    Restart the computer in normal mode, and try to login with a new user account."
    Well, "...then add these values.", it doesn't show what values to add ...
    They just mean if the entries are not
    Shell = explorer.exe
    Userinit = C:\WINDOWS\system32\userinit.exe

    then change them to those values.

    What are your current entries then?

    When something works in Safe mode but not in normal Windows it means that third-party software is affecting the situation.

    Denis
      My Computer


  5. Posts : 1,750
    Windows 10 Home
       #5

    Just for kicks, I booted into safe mode and I was able to sign in perfectly. What does that mean?
    When something works in Safe mode but not in normal Windows it means that third-party software is affecting the situation. Denis

    To decypher which it is, referring to attached screenshot, un-check services one-by-one and restart until sign-in issue is resolved (example shows bluetooth disabled). Date disabled column will help you keep track of what you've tried before trying another service. I would start with the obvious ones that could be blocking your login, like 3rd party antivirus, vpn's, or tweak programs like O&O, etc. Could also, in Task Manager, Startup, disable items one-by-one but that may not be as effective. Good Luck
    Updated to Win 20H2 but can not sign in to my local account-screenshot_1.jpg
      My Computer

  6. happyheart's Avatar
    Posts : 21
    Win 10 Home x64 v. 1903 (Build 18362.1440)
    Thread Starter
       #6

    Try3 said:
    They just mean if the entries are not
    Shell = explorer.exe
    Userinit = C:\WINDOWS\system32\userinit.exe

    then change them to those values.

    What are your current entries then?

    When something works in Safe mode but not in normal Windows it means that third-party software is affecting the situation.

    Denis

    Thank you for that clarification. The entries are correct on my computer. Is it weird that everything was working fine before the upgrade? I did not install any third-party software just before the upgrade. So can the upgrade do something to one of the third-party software programs?

    Actually, I do remember something strange the same day as I upgraded. I was rearranging some music in folders using file explorer and the program would not let me create a new folder - no matter how many different ways I tried. I ran 'sfc /scannow' and all was fine. No errors found. Also, I had just uninstalled Foobar2000.

    - - - Updated - - -

    mrgeek said:
    Just for kicks, I booted into safe mode and I was able to sign in perfectly. What does that mean?
    When something works in Safe mode but not in normal Windows it means that third-party software is affecting the situation. Denis

    To decypher which it is, referring to attached screenshot, un-check services one-by-one and restart until sign-in issue is resolved (example shows bluetooth disabled). Date disabled column will help you keep track of what you've tried before trying another service. I would start with the obvious ones that could be blocking your login, like 3rd party antivirus, vpn's, or tweak programs like O&O, etc. Could also, in Task Manager, Startup, disable items one-by-one but that may not be as effective. Good Luck
    Updated to Win 20H2 but can not sign in to my local account-screenshot_1.jpg

    Great suggestion! It seems like I'll have a very longggggggggggg night ahead of me. I'll let you know what happens. Thank you!
      My Computer

  7. Try3's Avatar
    Posts : 9,153
    Windows 10 Home x64 Version 21H2 Build 19044.1237
       #7

    happyheart said:
    It seems like I'll have a very longggggggggggg night ahead of me.
    This procedure is called a Clean boot.
    Perform a Clean Boot to Troubleshoot Software Conflicts - TenForumsTutorials

    Clean boots drive me up the wall. Given that you have already seen that Foobar utility affected Windows [folder creation], I'd be tempted to give a Repair install [aka In-place upgrade] a shot in the hope that whatever Foobar [or something else] has done to Windows can be corrected by giving Windows another chance to sort itself out.
    Repair Install - TenForumsTutorials
    Logic might not be on my side here but it is what I would do.


    Denis
      My Computer

  8. happyheart's Avatar
    Posts : 21
    Win 10 Home x64 v. 1903 (Build 18362.1440)
    Thread Starter
       #8

    Try3,

    I noticed that you run Win 10 Home Edition like I do, but you have a higher version of Windows than I just upgraded to. Would upgrading to the newest version possibly fix my problem? Or should all problems be fixed before you do upgrades? I don't want to create nightmare city...
      My Computer

  9. Try3's Avatar
    Posts : 9,153
    Windows 10 Home x64 Version 21H2 Build 19044.1237
       #9

    Given that you know that Windows has not been behaving correctly [creating folders, login issues], the Repair install procedure is the most thorough repair you can do and, by using the latest ISO for it, you will update to Version 21H1 at the same time.

    I would go ahead & do it if it was my computer.

    Only if problems remained afterwards would I do the tedious job of running Clean boots [even though they are the most appropriate course of action since Safe mode was OK].

    Denis
      My Computer

  10. happyheart's Avatar
    Posts : 21
    Win 10 Home x64 v. 1903 (Build 18362.1440)
    Thread Starter
       #10

    Hi again.

    1. I did the 'How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts - TenForumsTutorials' (BTW, how can I put the red links that show on others posts?).
    2. I did through 'Part Two - #10 - B'. 'B' meaning that the problem still existed with everything being disabled.
    3. I've rebooted and turned everything back to being enabled.
    4. I've backed-up with Macrium
    5. Now I guess I'll bite the bullet and try the 'Repair Install - TenForumsTutorials'. Honestly, this makes me a bit nervous. I've never done this before...

    Any other input before I begin? Thanks again. I'll let you know.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:13.
Find Us




Windows 10 Forums