I've done this before w/o any issue (I've several family members which use my PC.) I'm a fairly knowledgeable individual when it comes to PCs (I'd say moderate level.)Īnd the initial trigger for all of this was somehow the Start Menu became stupid. Somewhere in the " smarter than me" mode of Windows 10, it decided all the pieces weren't aligned properly, and not only linked my admin account to my email account, it corrupted the NTUSER.DAT file in the Default folder. I didn't ask it to, did not expect it to, and sure as heck didn't want it to. Since my profile was physical name was the same as a Hotmail account I have, it suddenly figured I should be using that account for my local system admin too. When the profile was created, the system somehow got confused. I went through the process to create a new profile, selecting no MS Account, and choosing to make it local. Of course, not sure I'm on the right track either.Īny one have any idea how to get my system capable of creating a new local profile without triggering a system error that prevents if from being used? Yet, can't seem to find/figure out how to get the core Default folder back from there. I have the most current version of the Win 10 Pro 圆4. The new profile, when logged on after re-creating the Default folder, still can't launch (and keep launched) the System Settings. Several steps have been taken to try corrective action, and they work somewhat. Well, the real culprit appears to be the C:\Users\Default\NTUSER.DAT file was somehow corrupted. Current admin and standard profiles continue to work (though more about this later.) The error occurs only during the creation/log on attempt for a new profile. After reading the 7Forums link I cannot find a similar instruction set w/in Win 10 yet I know that this forum is far better than the 'like' Microsoft forum since people responding on the MS Forum seem incapable of actually answering the question and provide real-life solutions.īottom line: I'm suffering from the dreaded " The User Profile Service failed the logon" message.
0 Comments
Leave a Reply. |