User Profile Service failed the logon - FIX

[JNStiles]

Just in case anyone has had this error recently, I thought I'd share a fix we found. The issue is to do with clients not being able to logon and displaying this error...

 

We found various explanations online, but the most recent suggestions were that this was due to a January 2014 update. However, we recently upgraded IE in our suites to version 11, so who knows?

 

Anyway, the error can be fixed by altering the NTFS permissions on C:\users\default (You'll need to show all hidden drives in order to see this folder) and select the "Replace all child objects permissions with inheritable permissions from this object" so that it is enabled

 

 

This will allow users to login from then on. I can't explain why, as before making this change all subfolders and files have permissions that reflect the default user's.

Anyway this can be done through GPO, under Computer Configuration > Policies > Windows Settings > Security Settings > File System.

 

 

Hopefully this gets someone out of trouble!

[ThatBoringBloke]

You need to clear out the profiles from the registry. the path below is where you will find them.

 

remove them from here and all will be well.

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

[JNStiles]

Doesn't work. Even when you use accounts that have never been logged on to the machine and have no profile in the registry, the same error occurs.

[Jamman960]

I've also had this recently, in my case once logged in locally I found that the eventlog, netlogon and many other services wouldn't start due to dependencys etc

 

My solution so far after a ton of googling has been to reset winsock - netsh winsock reset (elevated cmd needed)

 

I figured it was a fluke but I've been told this morning a couple of other machines have come up with the same issue so I'll give the above fix a go also

 

James

[Garacesh]

You need to clear out the profiles from the registry. the path below is where you will find them.

 

remove them from here and all will be well.

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

 

Deleting these, and the contents of C:\Users (besides Default) always seemed to sort this error out for me.

I have had some instances where Netlogon wouldn't start - I usually just reimaged the machine, but I'll keep that winsock in mind. Thanks!

[jonnykewell1]

just out of curiosity have you got ab tutor installed? I found at my old place when re installing ab tutor on machines netlogon would stop running and we had to do the reset winsock as mentioned above.

[Max_Power]

Struggling with this issue at the moment on a number of Windows 8 machines.

 

In my case it appears to be caused by an update which ironically is supposed to resolve the roaming profile issue Incompatibility between Windows 8 roaming user profiles and roaming profiles in other versions of Windows

 

Remove the update and it allows users to log on again - but screws up their roaming profile if they go back to a windows 7 machine. Install the update again and it prevents them from logging in.

 

Notice there is a rollup for windows 8.1 which includes this hotfix and others so starting to look at reinstalling all windows 8 machines with 8.1 and the rollup to see if it resolves the issue.

 

Non of the default user permission suggestions worked for me.

[RowlandoGloom]

I did notice in the MS article - there is a registry setting to make the change manually should you not wish to actually install the update itself:

 

'HKEY_LOCAL_MACHINE\System\CurrentControlset\Services\ProfSvc\Parameters'

 

As per the article, the value 'UseProfilePathExtensionVersion' should be set to '1', which makes the change and causes the problem.

 

If you change it to '0' instead, the setting wont be applied - making the machine work as before. If it's not there (which it probably is) create it and set it to '0'

 

You can then set this in group policy preferences, so all machines pick it up and change it back to '0' should the update ever put it back to '1'

 

Hope this helps. If you want more info, I.ve created some below:

 

Paul.

 

 

 

It's simply so profiles are the following:

user. WinXP

user.v2 Win 7

user.v3 Win 8

user.v4 Win 8.1, so they use different profiles for each version.

 

If you manually create the respective .v3 folder for a test user for example, it will let the user log on a Win 8 machine if the value above in the registry is set to 1.

 

Changing that value above to 0 stops it (trying to) using .v3 and .v4 profiles, sharing the .v2 with Win7, 8 and 8.1

 

Probably a .v5 for 8.2 or Win9!

Edited March 26, 2014 by RowlandoGloom

[mrbios]

Anyway, the error can be fixed by altering the NTFS permissions on C:\users\default (You'll need to show all hidden drives in order to see this folder) and select the "Replace all child objects permissions with inheritable permissions from this object" so that it is enabled

 

This particular issue only effects people using local profiles rather than mandatory or roaming from what i've seen but an alternative solution is to find the individual file (it's always the same one, with the same name) within the default profile appdata folder (it's in the internet explorer folder somewhere, you can find it in the event log anyway which one you need) and set up a GPP to delete that file from all computers, then you'll never get that problem again.

 

EDIT: i should mention, deleting it appears to have no negative side effects.

Edited March 25, 2014 by mrbios

[Norphy]

I had this problem today.

 

The problem turned out to be a load of SQM files sitting in the default user profile. Removing those fixed the issue.

 

The SQM files belonged to Windows Live and a removed instance of Visual Studio.

[Hawkeyez]

We seem to have this alot. Reset profiles (CC4) resolves most, but a real PITA to manage. On CC3 on pupil laptops we had scripts to delete profiles on startup excluding ones that needed to stay. Wondering if could do a similar thing on CC4.

[dsilva]

This topic is old and sorry to bring it back, just wanted to say I did what JNStiles and Jamman960 said and problem solved. Can't be sure which one fixed, but did both and worked for me. Thanks guys!

[jcubbin]

We had a very similar issue here after a number of updates had been combined to push out IE11 using Internet Explorer Administration Kit

 

The problem didn't start until a week or two later and happened if a user had never logged on at that machine before. If the user had logged on at the machine before there was no problem.

 

The file causing the issue was "C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary Internet Files\SQM\iesqmdata_setup0.sqm". New users where being denied access to this file which in turn was stopping it from creating a new profile on the machine.

 

 

 

 

The solution was to create a computer configuration GPO which deleted this file on all machines. This worked a treat.

 

[TechMonkey]

We had a very similar issue here after a number of updates had been combined to push out IE11 using Internet Explorer Administration Kit

 

The problem didn't start until a week or two later and happened if a user had never logged on at that machine before. If the user had logged on at the machine before there was no problem.

 

The file causing the issue was "C:\Users\Default\AppData\Local\Microsoft\Windows\Temporary Internet Files\SQM\iesqmdata_setup0.sqm". New users where being denied access to this file which in turn was stopping it from creating a new profile on the machine.

 

 

[ATTACH=CONFIG]34329[/ATTACH]

 

 

The solution was to create a computer configuration GPO which deleted this file on all machines. This worked a treat.

 

[ATTACH=CONFIG]34330[/ATTACH]

 

This. Exactly the same for us. IE11 going out and then users unable to login to a machine they hadn't previously. Did the same trick with the GPO and mostly all fine. Finding the odd machine that it hasn't cleared but that could just be bad timing.