I came across a Windows 8 laptop (yes in February 2020) that was running Windows 8, but when I created a new user and tried to log in, I got an error that said "User profile service failed the sign in" and the profile would not load at all.
The fix was to log in with an existing user, go into the application event log and find errors during the log in process relating to a permissions error copying data from c:\users\default to the new profile and deleting the minimum amount necessary (not the default folder or c:\users\default\appdata - much more specific).
I found this info here:
https://answers.microsoft.com/en-us/windows/forum/windows_8-security/user-profile-service-failed-the-sign-in/17ad3f7c-3b2d-433f-a3d5-bf7f6a79df1a?auth=1&page=3
Here's the important text, in case that link gets removed/changed:
I have figured out what the problem is. Basically, something from the Default profile directory fails to copy (this contains the initial files that Windows uses to set up a user). The Default profile is found at:
C:\Users\Default
If you go to c:\users, you will not see the Default directory.
To determine what fails to copy, go to the event viewer (this is on the start menu - right mouse on the start icon and a list of programs will display.). Open the Application Event log - (it will take a few moments for it to load the application event log - the Event Viewer application builds the logs and indexes before it will open completely.
Scroll down the event log until you see warnings from the "User Profile General" under the Source column. EventID 1509 indicates what files are not being copied. In my case, the entry said:
"Windows cannot copy file \\?\C:\Users\Default\AppData\Local\Microsoft\VSCommon\12.0\SQM\sqmdata-13304-039-00000.sqm to location .... This error may be caused by network problems or insufficient security rights.
DETAIL - Access is denied.
^^^^^
Bingo - Access denied can be caused by a lot of things. So, instead of struggling with what is wrong, just delete the directory that is causing the problem in the first place. If it is critical, then running a repair on the application that fails should recover that information. In my case, I deleted
VSCommon from C:\Users\Default\AppData\Local\Microsoft\
(Use Windows Explorer and enter in the address bar the parent directory for the offending files - I chose to enter C:\Users\Default\AppData\Local\Microsoft because I didn't want to screw with it HA HA)
Once you do that, log in with the new account and it should work. If it doesn't go back to the event log and locate the new EventID 1509.
DO NOT DELETE C:\Users\Default\AppData\Local\Microsoft. Delete the directory that is after that is causing the problem. Deleting the Microsoft or any of the directories about it will cause you all kinds of grief with a resulting rebuild of the computer.
Good Luck and don't panic. There is a solution, just a question of your patience to find it.