Microsoft Accounts Fail To Log In To Windows 10 with “User Profile Service failed the login” Error.
My kids are getting to the age where they can’t keep away from the laptop, various pads or the Smart TV to go online…time for some protection I thought.
I figured, for the Windows 10 laptops, that I’d use the Microsoft Accounts approach and use the “big brother” features there to stop the kids watching things they shouldn’t and restrict their access time.
First step was to convert my local account into a Microsoft one – simple enough and worked fine.
Next step was to create additional Microsoft accounts and then have them linked up as part of the “Family” – again, fine.
Then tell the PC to add those users – again all fine and simple to do.
All going well up until now, but then when I try to logout of my working Microsoft account on the laptop and login to one of the Family Microsoft accounts, it fails with the “User profile Service failed the login:
The best option for reducing risk of prostate diseases and for good health in general is a vegetarian diet. viagra prescription robertrobb.com It is also referred to commander levitra http://robertrobb.com/2015/03/ as a weekend pill. There was no place for frills levitra purchase robertrobb.com in their lives. It hampers the ability of enzymes PDE5 to suppress the chemicals causing erection viagra online discount problem.
After much googling and trying various things, the one which worked for me was to copy the directory C:\Users\Default from a working Windows 7 Ultimate machine onto the laptop with the problem (where the directory did not exist at all). The advice I found actually referred to copying from another Windows 10 machine, but I didn’t have one of those – only a Windows 7 one.
I then added the family Microsoft accounts back in and after logging out and trying to login as one of these added accounts then worked fine!
I can’t be certain what the issue was, but various reading suggested an issue where the machine was upgraded from Windows 7/8 to 10 and where the local profile (C:\Users\Default) was either missing or corrupted. Copying in a working one from another machine fixed the issue in my case.