Windows 11 login stuck on corrupt profile


Recommended Posts

The available space on my C (system) drive was low, so I moved the Users folder to my D drive and edited the registry accordingly.

After rebooting, I logged in to my work account and checked everything was okay. So far, so good.

Then I rebooted and tried to log in to my personal account and got the error message:

"The User Profile Service service failed to start.

User profile cannot be loaded."

I am stuck on this login screen, with no option to switch to my work account, even after a reboot.

Unfortunately, I don't have any System Restore points or any kind of backup to rely on.

Any help will be greatly appreciated.

Press the shift. Select Power then Restart.

Choose an option > Troubleshoot > Advanced Options > Startup Settings > Restart

Press 4 for Enable Safe Mode

Login to your user account as usual.

Run regedit

Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Two of the keys will be [something] and [something].bak

Rename [something] to [something].rename

Rename [something].bak to [something]

Rename [something].rename to [something].bak

Reboot

Done!

  • Like 2

Thanks for replying @Mockingbird.

I followed your instructions up to the

On 02/07/2023 at 15:39, Mockingbird said:

Login to your user account as usual.

step, where I am back at square one with the same error message. So Windows will not allow me to log in to my personal account, and there is no obvious way to log in to my work account instead.

Any further suggestions?

Following the steps provided to get into Safe Mode, I'd suggest moving your profile back to the C drive.

I gotta say... I am 0 days old hearing someone move their profile to a new drive to save space. I know when I uninstall programs or whatnot, I clean out the profiles manually as the AppData folders have a tendency to get left behind from some uninstallers or portable apps that don't remove files from them like game saves etc.

Is there anything else from C you can get rid of?

Long way around, if the C drive is removable, it may be possible to put it in another computer and move those files back. 

Last ditch effort... using the same steps as above, repair your installation of Windows.. but you may lose data. Afterwards you shouldn't have any issues moving your custom user data back.

Also, this:

https://www.makeuseof.com/fix-the-user-profile-service-failed-the-logon-windows-10/

  • Like 1
On 02/07/2023 at 09:35, Soap-dodger said:

Thanks for replying @Mockingbird.

I followed your instructions up to the

step, where I am back at square one with the same error message. So Windows will not allow me to log in to my personal account, and there is no obvious way to log in to my work account instead.

Any further suggestions?

Are you saying that you are unable to log in even in safe mode?

  • Like 1
On 02/07/2023 at 18:31, xMorpheousx416 said:

Following the steps provided to get into Safe Mode, I'd suggest moving your profile back to the C drive.

I gotta say... I am 0 days old hearing someone move their profile to a new drive to save space. I know when I uninstall programs or whatnot, I clean out the profiles manually as the AppData folders have a tendency to get left behind from some uninstallers or portable apps that don't remove files from them like game saves etc.

Is there anything else from C you can get rid of?

Long way around, if the C drive is removable, it may be possible to put it in another computer and move those files back. 

Last ditch effort... using the same steps as above, repair your installation of Windows.. but you may lose data. Afterwards you shouldn't have any issues moving your custom user data back.

Also, this:

https://www.makeuseof.com/fix-the-user-profile-service-failed-the-logon-windows-10/

 

On 02/07/2023 at 18:33, Mockingbird said:

Are you saying that you are unable to log in even in safe mode?

As I cannot log in to my personal account, even in Safe Mode, I was wondering if there is a text file on my C drive that could be edited to ensure the next login after a reboot would default to my work account.  Any idea?

On 02/07/2023 at 11:25, JammyDodger said:

Yes.

Trying using the built-in administrator account, then create a new user account

1. On the Windows sign-in screen, press and hold the Shift key, then select Power > Restart
2. After your machine reboots, click on "Troubleshoot" under Choose an option
3. Click on "Advanced options" > select "command prompt"
4. On the command prompt window, type net user administrator /active:yes and press Enter
5. Reboot your machine, and see if you'll be able to log in to the built-in administrator account
6. Create a new user account and copy your files to the new account(go through the steps under "My computer is in a workgroup") . Please refer to this article as a guide: 
Fix a corrupted user profile in Windows - Microsoft Support

  • Like 1

Thanks again, @Mockingbird.

Steps 1 to 4 completed, though I have doubts about the efficacy of step 4 because the administrator account in the Recovery Environment is not the same administrator account as in the Windows Environment after a successful log in.

I note that WinRE runs on drive X and my C and D drives are accessible from the WinRE cmd line (though their drive letters have been swapped around).

Anyway, after reboot, the logon screen remains stuck on my personal account, with no other account displayed at bottom left of screen. So, no further forward. ☹️

On 02/07/2023 at 18:31, xMorpheousx416 said:

Following the steps provided to get into Safe Mode, I'd suggest moving your profile back to the C drive.

I gotta say... I am 0 days old hearing someone move their profile to a new drive to save space. I know when I uninstall programs or whatnot, I clean out the profiles manually as the AppData folders have a tendency to get left behind from some uninstallers or portable apps that don't remove files from them like game saves etc.

Is there anything else from C you can get rid of?

Long way around, if the C drive is removable, it may be possible to put it in another computer and move those files back. 

Last ditch effort... using the same steps as above, repair your installation of Windows.. but you may lose data. Afterwards you shouldn't have any issues moving your custom user data back.

Also, this:

https://www.makeuseof.com/fix-the-user-profile-service-failed-the-logon-windows-10/

Thanks, @xMorpheousx416.

Tried all suggestions but no further forward.

Getting the feeling that something the logonui.exe (if it's still named that) is trying to hook a file it cannot find/corrupt registry entry. But... alas, the only idea I have left.. is to place that drive in another computer and move your profile back to it.

If D is not a partition of C, using a flash drive should be quick and easy.

I checked my User folder on this PC.. she's taking up to near 20GB of data. I can see why you moved it, but from here on out.. I'd suggest trimming the fat in other ways other moving Windows' files/folders.

 

Edited by xMorpheousx416
  • Like 1

Actually had this happen to a computer at work (AD Joined) and it seems to be something to do with the profile service itself being corrupt, not the profile.

  • Like 1
On 02/07/2023 at 14:46, Mockingbird said:

Trying using the built-in administrator account, then create a new user account

1. On the Windows sign-in screen, press and hold the Shift key, then select Power > Restart
2. After your machine reboots, click on "Troubleshoot" under Choose an option
3. Click on "Advanced options" > select "command prompt"
4. On the command prompt window, type net user administrator /active:yes and press Enter
5. Reboot your machine, and see if you'll be able to log in to the built-in administrator account
6. Create a new user account and copy your files to the new account(go through the steps under "My computer is in a workgroup") . Please refer to this article as a guide: 
Fix a corrupted user profile in Windows - Microsoft Support

Jammy... can you try these steps, (the command prompt) but instead of turning on/off the admin acct, try:   sfc/scannow

?

On 02/07/2023 at 18:04, Matthew S. said:

Actually had this happen to a computer at work (AD Joined) and it seems to be something to do with the profile service itself being corrupt, not the profile.

What was the solution if we may ask?

Not too many more ways of fixing this I'm aware of... or found searching, that won't lead to installing Windows again. Heck.. might be even quicker than going thru a list of things to avoid it. Perhaps using the "save my files" method if it's an option, "should" (and I take that with a grain of salt) maintain your other settings and apps.

  • Like 1
On 02/07/2023 at 13:56, JammyDodger said:

 

As I cannot log in to my personal account, even in Safe Mode, I was wondering if there is a text file on my C drive that could be edited to ensure the next login after a reboot would default to my work account.  Any idea?

Not that I'm aware of.

I could only imagine if a simple text file could override the boot sequence or defeat TPM if it's in place. Miss the good ole days of Windows 95? 

I remember being able to use the EDIT feature at the DOS prompt before starting Windows... if there was a driver issue or something, you could just edit the boot.ini file (I think that's what it was named)... replace said wonky driver with the name of Windows' basic driver (like vga.sys)... and boom, you're back on the desktop from a failed boot.

Bout all I can think of boss... other than trying to move your profile back, you may just have to reinstall Windows. You should be able to take management of any files locked to the profile if you just used a username/password combo, or have that saved key on disk.

  • Like 1
On 02/07/2023 at 21:05, leonsk29 said:

I'm curious... what did you do in the Registry to move the entire "C:\Users" folder to another drive? Is that even safe or supported? Seems like your problems started after doing that.

EDIT: I was doing a bit of research because I wanted to make sure and no, moving the C:\Users folder isn't supported at all, even with Registry edits, so I'm sorry to say that this problem was caused by doing that. Your user profile and probably Windows itself is corrupted now, you might have to reinstall.

  • Like 1

Hello,

Have you tired copying (not moving) the user profile back to the C:\ drive?  If so, were  you then able to recover it?

Regards,

Aryeh Goretsky
 

  • Like 1

 

On 03/07/2023 at 03:53, goretsky said:

Hello,

Have you tired copying (not moving) the user profile back to the C:\ drive?  If so, were  you then able to recover it?

Regards,

Aryeh Goretsky
 

Unfortunately, in the Windows Recovery Environment (WinRE) I don't have sufficient privileges to do that.

On 03/07/2023 at 01:52, xMorpheousx416 said:

Jammy... can you try these steps, (the command prompt) but instead of turning on/off the admin acct, try:   sfc/scannow

Did this: it found corrupt files and successfully repaired them. I checked the CBS.log file and was surprised at the amount of corruption encountered.

I didn't expect any corrupt files on the X drive in WinRE. Surely WinRE gets its OS from its dedicated partition rather than my system C (D in WinRE) volume. Or am I wrong?

After the reboot required for the repairs to take effect, I went back into WinRE and ran the same command again. The result was the same: corrupted files found and repaired. Obviously, the previous reboot had no effect on the repair.

After another reboot and back at the WinRE command prompt, I changed the path environment variable so that it referenced the D volume (my C drive) rather than WinRE's X volume. Then I cd'd to D and ran the sfc command again. Again corrupt files found and repaired.

After another restart, I'm back at the "stuck" logon screen, getting the original error message.

I deliberately entered the wrong password and got the expected error message re wrong password.

So, no progress, I'm afraid

 

On 02/07/2023 at 18:51, Mockingbird said:

Follow the "Change Registry Configuration" section.

I need to be able to log in to Windows before I can edit the Registry.

On 03/07/2023 at 23:33, leonsk29 said:

Just reinstall Windows from scratch if you can, you're prolonging your pain unnecessarily...

I will.

On 03/07/2023 at 17:45, JammyDodger said:

I need to be able to log in to Windows before I can edit the Registry.

I will.

Actually

You can do a regedit from the CMD Recovery Console. Once the registry editor loads, highlight hkey_local_machine and click file load hive. Then navigate to the Windows registry hive directory (example c:\windows\system32\config), then pick the hive you wish to load.

Then once loaded give it a name. Then edit what you need to edit. Then when you are finished, highlight the loaded hive and click file / unload hive.

  • Like 2
On 03/07/2023 at 02:05, leonsk29 said:

I'm curious... what did you do in the Registry to move the entire "C:\Users" folder to another drive? Is that even safe or supported? Seems like your problems started after doing that.

Edited every reference of C:\Users to D:\Users.

On 03/07/2023 at 18:45, JammyDodger said:

I need to be able to log in to Windows before I can edit the Registry.

Not at all. The Registry exists as regular files inside the C drive. If you can boot the PC with live media, you can copy the Registry files you need, open and edit them in another system, and copy them back. I don't know if that will solve your problem, though...

On 03/07/2023 at 18:50, JammyDodger said:

Edited every reference of C:\Users to D:\Users.

That's not supported by Microsoft, hence the issue you're having now. Windows really doesn't like when someone moves the "C:\Users" folder to another location, even after editing the Registry. There are more pieces in play here.

  • Like 3

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Nobody is buying a PS5 only for playing Until Dawn 2. Their loss.
    • If you actually used it instead of responding like a petulant child you might be surprised. I switched from Google some time ago and have been very satisfied.
    • I am one of the first people to use the DXVK technology. In the channel below you can see some videos that I have made using this technology, including Assassin's Creed Odyssey. https://www.youtube.com/@nahum7995/videos Assassin's Creed Odyssey experienced several bugs and technical issues during its first months after release. It launched with its own fair share of funny but frustrating glitches. I ran it on DXVK 9 days after its release and I played it for many hours but didn't see a single significant bug on Linux. Assassin's Creed Odyssey is widely celebrated for pushing the franchise in bold new directions and specifically for nailing several elements better than any other title in the AC series: Player Choice & Branching Narrative, The Mercenary & Cultist System, Mythological Integration, Overpowered Combat Abilities, Open World Exploration But what I'm trying to point out is that this game wasn't quite playable on most windows systems, until a few months after its release when most of the bugs were fixed. However, on Linux it ran completely flawless from day one, although DXVK had seen little development and refinement at the time. What do you think the situation will be in 2026 now that most bugs and glitches of DXVK have been completely eliminated? This is information from Google about these situations that I am quoting. In many cases, using DXVK (a translation layer that converts DirectX 9, 10, or 11 into Vulkan) can result in more stable frame times and higher performance than native Windows rendering. This happens primarily by bypassing driver overhead and multithreading draw calls that were previously restricted to a single CPU core. Older APIs (like DirectX 9 and 11) are largely single-threaded on the CPU side. DXVK translates these calls to Vulkan, which is highly multi-threaded. This reduces CPU-bound stuttering on weaker processors. In certain cases, GPU manufacturers (especially AMD) have significantly better and more modern Vulkan drivers than they do for legacy DirectX. Vulkan gives developers—and in this case, the translation layer—closer control over how resources are held in VRAM. This can prevent micro-stutters and sudden frame drops during chaotic gameplay. Yes, certain games, particularly older DirectX 9 to 11 titles, can run with fewer crashes on DXVK than on native Windows. By intercepting DirectX draw calls and translating them into the modern, highly efficient Vulkan API, DXVK bypasses the limitations and poor driver support that cause instability in aging game engines. PlayStation 1, PlayStation 2 and PlayStation 3 can be easily and perfectly emulated on Linux. In fact, modern Linux emulators offer high-performance upscaling, widescreen patches, and automatic controller mapping out of the box.                                                                                                                                                                                                                                                                                                                                 PlayStation 1/2/3 games look drastically better on Linux thanks to resolution upscaling. Furthermore, it is also a fact that you cannot play many fun games on Windows either, isn't it? - The Nintendo Switch has an extensive library of exclusive games. - PlayStation has an extensive library of exclusive games - Android has "mobile-exclusive" games, meaning they are exclusive to mobile devices (iOS and Android) and aren't available on PC or consoles. And finally, it is also the case that in the next five years there will be games that millions of people will say you absolutely must play and that they want to play this specific game that released a few days ago. However, the other side of this story is that currently, absolutely no one cares that they cannot play these upcoming games right now.
    • Flameshot 14.0 RC3 by Razvan Serea Flameshot is a free and open-source, cross-platform tool to take screenshots with many built-in features to save you time. Using Flameshot is as simple as launching, dragging the selection box to cover the area you want to capture, making annotations as needed in on-screen and saving the shot to your computer, all with a very simple and straightforward interface. Flameshot allows users to simply upload their screenshots directly to the cloud in order to easily share it with others. You can upload your image directly to Imgur with a single click and share the URL with others. In-app screenshot editing - You can choose to add an arrow mark, highlight text, blur a section (blur or pixelate an area), add a text, draw something, add a rectangular/circular shaped border, add an incrementing counter number, and add a solid color box with Flameshot's built-in editing tools. Command-line interface (CLI) - Flameshot has several commands you can use in the terminal without launching the GUI via a command line interface. The command line interface lets you script Flameshot and use it as the subject of key binds. Flameshot 14.0 RC3 changelog: Translations update from Hosted Weblate by @weblate in #4612 Translations update from Hosted Weblate by @weblate in #4619 Fix pin position on Windows for scaled screen by @ElTh0r0 in #4614 Cmake Analyzers by @ElTh0r0 in #4613 Translations update from Hosted Weblate by @weblate in #4632 fix(macos): prevent config tab content from rendering behind tab bar by @Mitnitsky in #4627 fix(macos): use CGRequestScreenCaptureAccess instead of grabWindow for permission request by @Mitnitsky in #4617 Fix KDE Plasma keyboard shortcut config file by @ElTh0r0 in #4637 fix(macos): fix clipboard copy failing from tray and GUI by @Mitnitsky in #4629 feature(macos): show dock icon when config window is open by @Mitnitsky in #4628 Option to disable tray icon on Windows by @ElTh0r0 in #4634 Translations update from Hosted Weblate by @weblate in #4642 fix(macos): make fullscreen capture overlay configurable by @Mitnitsky in #4622 Update GH actions using Node.js 24 by @ElTh0r0 in #4660 fix issue with screen selection in non interactive mode by @borgmanJeremy in #4667 Uniformize both spec files + ninja build openSUSE by @QuentiumYT in #4658 screengrabber: pass non-empty parent_window to xdg-desktop-portal by @artefaktor93 in #4664 Allow multiple flameshot GUI instances (fix for #3177) by @ElTh0r0 in #4680 Unify Linux ARM CI into Linux CI (also drop QEMU) by @theofficialgman in #4702 respect system proxy settings by @borgmanJeremy in #4674 Replace ifdef LINUX with UNIX to include BSD systems by @ElTh0r0 in #4700 Download: Flameshot 14.0 RC3 | 18.1 MB (Open Source) Download: Flameshot Portable | 53.0 MB Links: Flameshot Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      490
    2. 2
      PsYcHoKiLLa
      233
    3. 3
      Skyfrog
      78
    4. 4
      FloatingFatMan
      68
    5. 5
      Michael Scrip
      58
  • Tell a friend

    Love Neowin? Tell a friend!