Unable to log in to Windows following a BSOD event.
Unable to log in to Windows following a BSOD event.
I attempted to set up a new account using safe mode and moved my data over, but the newly created account still doesn’t function properly. It behaves the same as other accounts—works in safe mode but not outside of it. Once the account is fresh, the start menu fails to open. I’ve also noticed varying error messages; sometimes it says “The User Profile Service failed the sign-in,” and other times it reports “The ProfSvc ailed the sign-in.”
I attempted to set up a new account as described, yet the same issue persists during login for the newly created account.
I understand the situation. In Safe Mode, navigate to your account settings and open the registry editor (regedit). Go to the path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Look for folders labeled S-1-5... and ensure each has a valid "ProfileImagePath" value pointing to a correct location, such as C:\Users\Ante.Kunick1990\. Verify the entries are complete and not empty or corrupted. For RefCount, set its value to 0 and double-click if needed. If you find any backup folders ending with ".bak" under ProfileList, let me know.
Verification confirmed. chkdsk typically works well and assists in fixing data issues. For drives with severe file corruption or bad sectors, it may not resolve the problem. It’s still wise to inspect the registry if you haven’t already. Clear evidence of corrupted profiles often appears as files ending in .bak.
Begin by launching the Registry Editor (regedit.exe). Navigate to the path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Within the registry structure, you’ll find multiple branches labeled with lengthy names starting from S-1-5. Each branch represents a distinct user profile. To identify the correct profile for a specific user, examine the ProfileImagePath value. In this case, the entry S-1-5-21-3650440056-3766451173-3310994491-1001 points to the root account (C:\Users\root). Ensure the corresponding folder is present on your disk. If the registry key name doesn’t end with .bak, reset the DWORD 32-bit fields State and RefCount to zero—create them manually if absent. For profiles with two sections, rename the main section to .bak and the .bak to the main section. If only one .bak exists, delete that extension. Confirm RefCount and State are both zero. Restart your system. This should resolve issues related to corrupted user profiles. If problems persist, Microsoft advises generating a new account and transferring the profile data.