Builds 19593 to 20226 User Profile Logon Issue - Workaround Included

Anonymous
2020-10-06T04:41:28+00:00

If you'd like to share a link to this post, we've created a short URL to assist:https://aka.ms/20226profile

*Edit*  This scenario could impact users in the Dev Channel (only) on builds 19593 through 20226.  The same workaround applies to any user in this build range in the Dev Channel who experiences this scenario.

Hello Windows Insiders,

After the launch of build 20226 to the Dev channel, a small number of users have reported not being able to log into their user profile(s) as expected.  This post covers this scenario, including a workaround for those affected who see the following message:

Note: this workaround ONLY applies to builds 19593 through 20226 on the Dev channel.  It does not apply to Retail users, or users in the Beta or Release Preview Channels..

Note:  the included steps assume your Windows installation is defaulted to the C: drive.  If you have installed Windows on a different drive letter, please replace c: with the proper drive letter for your installation.

To bypass this issue, please complete the following steps:

If your account is an Administrator account on the affected device:

  1. When you see the “We can’t sign into your account” dialogue, click the Close button.
  2. Open an elevated Command Prompt window.
  3. Enter and submit the following commands one line at a time:
    • cd c:\users%username%
    • takeown /F ntuser.dat*
    • icacls ntuser.dat* /reset
    • icacls ntuser.dat* /setowner "SYSTEM"
  4. Sign out.
  5. You will stop seeing the above dialog on your next sign-in.

If your account is NOT an Administrator account on the affected device:

  1. When you see the “We can’t sign into your account” dialogue, click the Close button.
  2. Open a standard Command Prompt window.
  3. Enter the following command:
    • Echo %username%
    • (Make note of the returned username, you will use it in step 6)
  4. Close the standard Command Prompt window.
  5. Open an elevated Command Prompt window.
  6. Enter and submit the following commands one line at a time:
    • cd c:\users\username
    • takeown /F ntuser.dat*
    • icacls ntuser.dat* /reset
    • icacls ntuser.dat* /setowner "SYSTEM"
  7. Sign out
  8. You will stop seeing the above dialog on your next sign-in

If these steps don’t resolve the issue for you on build 20226, you may also complete a rollback to your previous build to bypass.  You may then reinstall build 20226 and you will not encounter the issue a second time.

We’ve identified the cause of the bug and a fix is under development thanks to the swift feedback and insights from the Windows Insider community.

Thank you and keep the feedback coming!

  • The Windows Insider Team
Windows Insider program | Windows Insider preview | Security, privacy, and accounts

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

47 answers

Sort by: Most helpful
  1. Anonymous
    2020-10-07T17:51:00+00:00

    Got this on 20226

    Tried permission fix, nope.

    Tried setting RefCount = 0 on s-1-5-18, nope.

    Tried removing .bak profile files and reg, nope.

    Lost all hope.

    In temporary profile, in safe mode, went to real profile dir,

    noticed all transaction files are duplicated many times,

    deleted ALL these files:

    ntuser.dat.log1

    ntuser.dat.log2

    ntuser.dat{****}.TM.blf

    ntuser.dat{****}.TMContainer*****.regtrans-ms

    Login normal all is good xD

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-10-07T17:29:24+00:00

    Thanks for the fix!

    I'd suggest pasting the error from the event viewer when this happens so google can index this. I tried many alternatives and none worked, what worked was resetting to the previous build of insiders.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-10-06T13:28:03+00:00

    This doesn't solve all of the problems with my profile. I had the logon issue described above, reset my device, and that issue went away, but now I'm unable to use my account for any apps. So I can log on correctly, but I can't connect outlook, edge, etc. to my user account. I tried submitting this through the feedback hub, but that (among other apps) crashes and won't open anymore. Any workarounds or solutions for this?

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-10-06T06:58:10+00:00

    With me the problem occurred after about 3 days. An Inplace Upgrade helped me.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. BryceSor 5,510 Reputation points Volunteer Moderator
    2020-10-06T05:13:15+00:00

    Hi Sumit, 

    Now you need to re-install 20226 and test 😊

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments