Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have Windows 2008R2 with Exchange 2010. A user logged in and they receive a message The User Profile Service Failed the Logon. User Profile Cannot Be Loaded.

I can currently remote in as I have had a profile on there for a while now, but it is stopping anyone creating a new profile.

I have checked the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList but there does not seem anything out of the norm, not .bak file etc.

I have also restarted the Server and applied updates.

share|improve this question
Why are users logging on to the Exchange server? – joeqwerty May 11 '12 at 13:43
Two Admin's need access for any server maintenance etc, why else? – Matt May 11 '12 at 13:51
up vote 2 down vote accepted

I have found a solution to my problem - the default user profile (C:\Users\Default) seemed to lack necessary ACEs. After resetting ACLs and re-enabling inheritance, creation of new profiles worked as expected. See this link for details.

Text of the above link:

I think the problem caused by some security permission changes to the default user account in the path C:\Users.

The solution, unhide Default user by doing (Computer -> Tools -> Folder options -> ) ,

The right click over the Default user -> Properties -> Security -> Advanced then tick the "replace all child object permission entries with inheritable permission from this object" fixes the issue. Basically you are replacing all child object permissions for Default user.

Now you should be able to login.

share|improve this answer

Have you tried restoring ? Not sure if it would work on a server if it is recommended for a server but it did work on a Windows 7 machine. Fixing The User Profile Service failed the logon

share|improve this answer

Somehow folder C:\Users\Default was deleted from the server, so copying Default folder from another server solved my problem.

share|improve this answer
Not sure if it was the root cause in the OP's case though. – Deer Hunter Nov 16 '15 at 23:41

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.