[German]A few days ago, a German blog reader sent me a mail about an issue he was facing. After migrating from Windows 7 clients to Windows 10 V1809, the clients could not logon to a domain because the user profile service could not be loaded.
Advertising
The error description
Blog reader Holger K. wrote that he has switched for one of his customers some clients from Windows 7 to Windows 10 1809. Afterward he wasn't able to log in the Windows 10 clients to a domain controller (DC) running with Windows 2016. He received the following message on the clients:
"Error logging in with the user profile service. The user profile cannot be loaded"
He checked the clients, but all upgraded Windows 10 1809 systems are providing this message for the user account selected. Microsoft has already posted this article, but for Windows Vista and Windows 7 and for local clients.
The solution (workaround)
While searching the net for the root cause, blog reader Holger came across this Technet forum post. There a user describes the same scenario outlined above:
Some domain users get "user profile service failed" when trying to login after October Windows update
Some of my domain users can't logon on any upgraded Win10 pro machine, whilst other users can logon to the upgraded machine fine. they see the error – windows couldn't connect to the user profile service service.
There accounts can also not logon to other upgraded machines – they see the same error on other machines too.
The 'fix' seem to be rebuild their machine then stop the update happening – but what is the rel cause and proper fix?
i also on one occasion on one machine saw windows couldn't connect to the System Event notification Service service
A user confirmed the issues with Windows 10 V1809 and rolled his clients back to Windows 10 version 1803. But user Gov PC Guy also provided a solution for a workaround:
found something, clearing the home drive path on the active directory user object. It allowed me to login. I then home drive mapping back on the object (it complains that the directory already exists, but I said ok) logged user off and back on again and it seems fine.
Blog reader Holger wrote, that user Gov PC Guy has reset the profile in the server's AD to local and back again immediately. Windows will informed you, that the directory already exists. But then it asks, if you want to grant the user full access to the profile path. If this is confirmed, the profile path is set again.
Advertising
According to blog reader Holger, afterward the user can then log in on any Win10 1809 client again. When comparing what's different about this and another user profile, Holger noticed that the other user profiles have no "full access" for the user. The newly assigned user, on the other hand, already has this full access.
Holger suspects that Windows 10 intents to write new entries that did not exist before. He doesn't know why the DC is acting now this differently, because he doesn't know the history of this customer environment. Possibly the Domain Controller (DC) was migrated in the past. Maybe it has something to do with the issue I describe within my blog post Windows 10 V1803: Roaming profile not fully synchronized – I don't know. Holger says: "It can be assumed that this problem will occur more frequently in the near future". At this point thanks for the information, maybe the info will help others.
Similar articles:
Windows 10 V1809: Continous Warnings (Event ID 1534)
Windows 10 V1803: Roaming profile not fully synchronized
Temporary profile in Windows caused by Windows Defender?
Windows: Yes button in user account controls is disabled
Windows 10 V1607: Update KB4467684 kills Outlook search in Terminal Server
Advertising
