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

47 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-10-06T06:44:19+00:00

    This worked. Thanks 👍

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-10-06T06:41:00+00:00

    Actually, this issue seems to be associated with the account or the profile that is enrolled in the Insider program. My sister is facing this issue right now. Her PC is running build 20221. For the time being, we decided to transfer the data to another system running a stable May release (build 19041.546). However, after a while, the issue reappeared on this other system as well. Not sure if you have seen this as well. We are still in the process of transferring the data and setting everything up again, so needs some more testing to see what is happening with the profile. I'll try this solution in that system as well.

    EDIT: tried this fix on Build 20221 system, it seems to have worked. She is able to log into her profile now. Will keep updating this post if anything else comes up.

    Was this answer helpful?

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

    Fixed! Thanks a lot!

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  4. Sumit 44,436 Reputation points Volunteer Moderator
    2020-10-06T05:38:04+00:00

    Haha yes, Bryce. Doing it right now. I don't remember when I had rolled back to the earlier build last time. Says a lot about quality - Dev Builds are very solid lately.

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-10-06T05:14:27+00:00

    Thank you, Jason! I will translate your solution into Chinese and pass it on to the Windows insiders in China as soon as possible. I sincerely wish you success in your work and happy life!

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments