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 : When you see the “We can’t sign into your account” dialogue, click the Close button. Open an elevated Command Prompt window. 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" Sign out. You will stop seeing the above dialog on your next sign-in. If your account is NOT an Administrator account on the affected device : When you see the “We can’t sign into your account” dialogue, click the Close button. Open a standard Command Prompt window. Enter the following command: Echo %username% (Make note of the returned username, you will use it in step 6) Close the standard Command Prompt window. Open an elevated Command Prompt window. 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" Sign out 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

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

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. I used the rollback method when I encountered this a few days ago (before seeing this post). I then reinstalled 20226 and ran into this same issue again today. This time, I used the CLI instructions, so we'll see if that works. I just wanted to highlight that the rollback and reinstall of 20226 does NOT resolve the issue for good.

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.

I had thia same login peoblem 3 days ago. I saw some videos about going into Regedit ans making Profile changes, but that disnt fix it. As it kept creating a new Temp account on boot. So I did a roll-back to the previous build, and everything worked expect my HP Laser printer, V3 drivers could not be found. Even after removing all drivers ans reinstall them, it would not work. I had to manually change it to V4 print driver. Then yesterday I did the update again to 20226 and login is working.

I have been upgrading insider builds for several months up to build 20226. I have not experienced any Sign-in problem with build 20226. Yesterday I clean-installed build 20226 from the iso which I made from the WU files I downloaded when upgrading from build 20221 to 20226. After clean-installing I did not experience any Sign-in issue, either. For a long time I have been using Windows Hello PIN. I also set up my clean-install with a Windows Hello PIN when still in installation phase before first sign-in. I wonder if those having sign-in issues are using passwords to sign in instead of Windows Hello PIN or some other methods. @SuatCini, I updated 4 machines from 20221 to 20226 and from 19041.546 to 20226 and did not have this issue either. Since MS says they have identified the cause of the bug, if they gave a better description of what they identified, perhaps we could understand better why it failed only for some users and not for others. :-(

Builds 19593 to 20226 User Profile Logon Issue - Workaround Included

Anonymous

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:

When you see the “We can’t sign into your account” dialogue, click the Close button.
Open an elevated Command Prompt window.
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"
Sign out.
You will stop seeing the above dialog on your next sign-in.

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

When you see the “We can’t sign into your account” dialogue, click the Close button.
Open a standard Command Prompt window.
Enter the following command:
- Echo %username%
- (Make note of the returned username, you will use it in step 6)
Close the standard Command Prompt window.
Open an elevated Command Prompt window.
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"
Sign out
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

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

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
Anonymous

2020-10-07T17:49:42+00:00

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.

I used the rollback method when I encountered this a few days ago (before seeing this post). I then reinstalled 20226 and ran into this same issue again today.

This time, I used the CLI instructions, so we'll see if that works. I just wanted to highlight that the rollback and reinstall of 20226 does NOT resolve the issue for good.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
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
Anonymous

2020-10-07T17:25:46+00:00

I had thia same login peoblem 3 days ago. I saw some videos about going into Regedit ans making Profile changes, but that disnt fix it. As it kept creating a new Temp account on boot. So I did a roll-back to the previous build, and everything worked expect my HP Laser printer, V3 drivers could not be found. Even after removing all drivers ans reinstall them, it would not work. I had to manually change it to V4 print driver. Then yesterday I did the update again to 20226 and login is working.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2020-10-07T00:05:02+00:00

I have been upgrading insider builds for several months up to build 20226. I have not experienced any Sign-in problem with build 20226. Yesterday I clean-installed build 20226 from the iso which I made from the WU files I downloaded when upgrading from build 20221 to 20226. After clean-installing I did not experience any Sign-in issue, either.

For a long time I have been using Windows Hello PIN. I also set up my clean-install with a Windows Hello PIN when still in installation phase before first sign-in. I wonder if those having sign-in issues are using passwords to sign in instead of Windows Hello PIN or some other methods.

@SuatCini,

I updated 4 machines from 20221 to 20226 and from 19041.546 to 20226 and did not have this issue either.

Since MS says they have identified the cause of the bug, if they gave a better description of what they identified, perhaps we could understand better why it failed only for some users and not for others. :-(
Was this answer helpful?

0 comments No comments