User Profile Service failed the sign-in

[IAMCloud_Curt]

Hi,

 

Random error but bugging me. No matter what or where we try to log onto certain users they are getting "The User Profile Service service failed the sign-in"

 

attached a screenshot from test machine

 

The account is an AD account with profile path to our FS - even if you give it another profile path same issue, or remove the profile path same issue.

 

Tried delprof and my powershell script but the user doesn't even exist in the C:\users or registry

 

I have even deleted the account, and remade the same username and that didn't fix.

 

Other users are fine, just 3-4 dodgy accounts with no explanation

 

[Mark182]

Is the happening on one device or multiple devices with those 3/4 users?

[IAMCloud_Curt]

Is the happening on one device or multiple devices with those 3/4 users?

 

Multiple devices on those users.

[Davit2005]

I've seen similar errors on Citrix with redirected profiles, years back. To be honest I have not used redirected profiles for years, brings back too many bad memories.

 

It would be the first place to check out though.

[Mark182]

If the users are not in C:\users\ and they have logged in previously I'd check their permissions or check the default profile’s NTUSER.DAT file

[Jaan]

just started getting some of these...... even with my login.

 

Did anybody find a fix before i just reimage?

[BOOT]

Just out of curiosity... have you used delprof2 on any of those?

[Jaan]

No we don't use it.

[meakjoe]

Check HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList for entries. We find the affected users SID in there as a key, and the 'State' reg entry under there is the one which messes it up we think. Deleting the entire key resolves the logon issue.

[IAMCloud_Curt]

Full fix that works for us is to.

 

Restart the PC to begin with when you get hit with user profile failed the logon error.. It's important you restart, otherwise the profile remains open by SYSTEM service and you can't delete ntuser.dat

 

Once restarted logon as domain admin or local admin

 

Go to C:\Users delete the affected profile. If it's not there, not to worry. Skip to the below step

 

Open regedit when the profile has been deleted

 

HKLM\SOFTWARE\MICROSOFT\WINDOWS_NT\CURRENTVERSION\PROFILELIST

 

Find the affect subkey S-I-512 etc and delete it

 

Restart the pc and logon on to the affected user again should work

 

I experienced this alot with Windows 10 v1909 or v2004. Scraped roaming profiles, and we just use folder redirection via GP and local profiles. Works a treat now [emoji3]

[timbo343]

We have been having this issue

 

We use mandatory profiles and the local profile is removed at logoff and then deleted by delprof too at shutdown and power on.

 

As others have mentioned, the profile reg key is still listed in the registry.

 

I too would like to know what it causing this and why the reg key is not being deleted.

 

Its not all machines, it's very random, doesnt happen on the same machine but annoying when it happens.

[Jaan]

We don't delete our profiles with delprof, not sure what's caused this either.

[IAMCloud_Curt]

We have been having this issue

 

We use mandatory profiles and the local profile is removed at logoff and then deleted by delprof too at shutdown and power on.

 

As others have mentioned, the profile reg key is still listed in the registry.

 

I too would like to know what it causing this and why the reg key is not being deleted.

 

Its not all machines, it's very random, doesnt happen on the same machine but annoying when it happens.

Are you running a delprof script at logoff or using the GPO profile deletion method?

[meakjoe]

We find this issue mainly on laptops, and our thinking behind it is that they lose connectivity to the WIFI on logoff, or roam between APs as they're taking them back to the trollies and they haven't finished logging off and shutting down.

 

This then doesn't finish the log off procedure properly leaving remains of the profile including the affected registry keys. We very very rarely have this issue on desktops which are hard wired.