Recently, I have had my harddrive begin failing to the point where I could only get to the welcome screen, but not to the desktop, after which I tried to repair it, but it begun failing faster, so I quickly used Linux Mint's GDDRescue to copy everything I could, as I didn't get an opportunity to back everything up on the cloud. (Only about 50MBs of data was lost; All previous methods such as Clonezilla and other cloning software have failed.) Now, I did manage to get everything from the D: drive and the C: drive, which is amazing, but Windows didn't seem to work even after multiple chkdsk with all kinds of handles, such as /f, /r, /x and etc. This disk holds a lot of programs, that are no longer available on the market (Older versions of Photoshop, Games, Vegas Pro and so on), so it is in my best interest to repair Windows to get back to it. After that, I could reliably get to the same point as before - lock screen (the one with time, that you need to pull up to make it display the pincode part). Although, this time, this is what happened: I would try to press buttons and pull the time/date thing up, but it would just drop back down and not allow me to do anything. I tried to enter Windows' Recovery Environment, which resulted in a restart and a blue screen saying "recovery" and that my system needs to be repaired, so I created a Windows Installation USB to enter the Recovery Environment from it. Automatic Repair was out of the question immediately, it would fail right away. I would try to use all bootrec commands (fixboot, fixmbr, scanos, rebuildbcd and so on), but every time I would get to rebuildbcd or scanos, it would ALWAYS recognize that the Windows is installed on the needed partition, but on rebuildbcd question of "Do you want to add this installation to the boot?" (Something along those lines), it would always give me an error of "The requested system device is not found". And so begun the gauntlet of troubles. Things that failed: Getting into Windows' own Recovery Mode/Running an Automatic repair. (Upon restarting, it provides yet another error on a blue screen saying "Recovery") Running chkdsk. (With any handles) Bootrec /rebuildbcd (After confirming, it gives out an error) sfc /scannow. (Yes, even specifying the directories) Bootedit/BootBCD commands. Things that are definitely not broken: -The new drive (It is a brand new Samsung 1TB SSD, checked, in perfect condition) Files system (Multiple chkdsks were run to confirm it) Registry (Files are completely intact and it boots into Windows lockscreen to begin with) I've tried almost everything and now I have two options left: Repair Windows by inputting a source image from the USB drive ( correct me if I am wrong ) or repair DISM Error Code: 2 to be able to repair the disk as many guides and posts on these forums point to. The main question is, what should I do from this point? Any details - I can provide, I have been trying for 3 days now. EDIT: I do have my hands on a harddrive, from which I am currently running another Windows instance, WITHIN the same PC, I DO have a bootable USB device and if needed, a DVD/CD.

Alright, I tried every possible combination with and without the old graphics card, as well as plugging into the motherboard with no GPU. Nothing changed. One thing that I noticed is that using Windows + Ctrl + Shift + B brings the login screen BACK from this black screen with cursor. (Obviously, still cannot access the log-in part) What should I do now? Also, there is some additional context I can provide as to what happens, but I am not sure if it is relevant. Should I write it down anyway? It has to do with the difference in cursor/Your PC couldn't shut down/start up properly screens, new things in the System.evtx file and so on.

The UserManager service is crashing. Here are some other things you can try. Download "ShadowCopyView" and see if there are shadow copies on the F drive. If available, you can restore the registry hives, especially SOFTWARE and SYSTEM registry hives, from shadow storage. Run SFC offline (via WinRE) with the logging option. Run: diskpart list vol exit Note the drive letter of your problematic Windows installation. Let's say it's F: For example: sfc /scannow /offbootdir=f:\ /offwindir=f:\windows /offlogfile=f:\sfcoffline.txt Attach f:\sfcoffline.txt.

Alright, I've ran the SFC prompt from a command prompt (from a USB) and it returned an error "Windows Resource Protection could not perform a requested operation". **** (The drive letter changed to H: in this case) Here is the sfcoffline.txt file: https://1drv.ms/t/s!Ap7bkRjaepZyggpnBErUOoEXuaD1?e=uK6Mhz I've also downloaded and ran ShadowCopyView and it did not show any shadow copies anywhere besides the current working Windows partition. However, some time ago I've made a backup of registry while using CCleaner (See the screenshot attached), could this be of any use? ![](https://learn-attachment.microsoft.com/api/attachments/00d3e005-9274-4aef-bce2-1eed94e75f6c?platform=QnA

SFC reports a .mui file is corrupt but that's not causing the user profile issue. A .REG file export of the entire registry is not helpful. The proper way to backup the complete registry is by backing up the hives. I guess a reset (with Keep my files) is the only thing I can think of. From the login screen, press and hold the Shift key and click Restart. Click the Advanced options button. Click on Troubleshoot. Click the “Reset this PC” option.

Trying to repair Windows with DISM, but running into Error Code 2.

Anonymous

Recently, I have had my harddrive begin failing to the point where I could only get to the welcome screen, but not to the desktop, after which I tried to repair it, but it begun failing faster, so I quickly used Linux Mint's GDDRescue to copy everything I could, as I didn't get an opportunity to back everything up on the cloud. (Only about 50MBs of data was lost; All previous methods such as Clonezilla and other cloning software have failed.)

Now, I did manage to get everything from the D: drive and the C: drive, which is amazing, but Windows didn't seem to work even after multiple chkdsk with all kinds of handles, such as /f, /r, /x and etc. This disk holds a lot of programs, that are no longer available on the market (Older versions of Photoshop, Games, Vegas Pro and so on), so it is in my best interest to repair Windows to get back to it.

After that, I could reliably get to the same point as before - lock screen (the one with time, that you need to pull up to make it display the pincode part). Although, this time, this is what happened:

I would try to press buttons and pull the time/date thing up, but it would just drop back down and not allow me to do anything.
I tried to enter Windows' Recovery Environment, which resulted in a restart and a blue screen saying "recovery" and that my system needs to be repaired, so I created a Windows Installation USB to enter the Recovery Environment from it.
Automatic Repair was out of the question immediately, it would fail right away.
I would try to use all bootrec commands (fixboot, fixmbr, scanos, rebuildbcd and so on), but every time I would get to rebuildbcd or scanos, it would ALWAYS recognize that the Windows is installed on the needed partition, but on rebuildbcd question of "Do you want to add this installation to the boot?" (Something along those lines), it would always give me an error of "The requested system device is not found".
And so begun the gauntlet of troubles.

Things that failed:

Getting into Windows' own Recovery Mode/Running an Automatic repair. (Upon restarting, it provides yet another error on a blue screen saying "Recovery")
Running chkdsk. (With any handles)
Bootrec /rebuildbcd (After confirming, it gives out an error)
sfc /scannow. (Yes, even specifying the directories)
Bootedit/BootBCD commands.

Things that are definitely not broken:
-The new drive (It is a brand new Samsung 1TB SSD, checked, in perfect condition)

Files system (Multiple chkdsks were run to confirm it)
Registry (Files are completely intact and it boots into Windows lockscreen to begin with)

I've tried almost everything and now I have two options left: Repair Windows by inputting a source image from the USB drive (correct me if I am wrong) or repair DISM Error Code: 2 to be able to repair the disk as many guides and posts on these forums point to.

The main question is, what should I do from this point? Any details - I can provide, I have been trying for 3 days now.

EDIT: I do have my hands on a harddrive, from which I am currently running another Windows instance, WITHIN the same PC, I DO have a bootable USB device and if needed, a DVD/CD.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Copying Program Files doesn't help. After a clean installation all the programs need to be reinstalled because there are references to the program in the registry which will be lost during clean install. You may backup AppData though.

0 comments

41 additional answers

Anonymous

2024-10-07T04:40:51+00:00

Alright, I tried every possible combination with and without the old graphics card, as well as plugging into the motherboard with no GPU. Nothing changed.

One thing that I noticed is that using Windows + Ctrl + Shift + B brings the login screen BACK from this black screen with cursor. (Obviously, still cannot access the log-in part)

What should I do now? Also, there is some additional context I can provide as to what happens, but I am not sure if it is relevant. Should I write it down anyway? It has to do with the difference in cursor/Your PC couldn't shut down/start up properly screens, new things in the System.evtx file and so on.
Was this answer helpful?

0 comments No comments
Anonymous

2024-10-07T05:45:51+00:00
The UserManager service is crashing. Here are some other things you can try.
1. Download "ShadowCopyView" and see if there are shadow copies on the F drive. If available, you can restore the registry hives, especially SOFTWARE and SYSTEM registry hives, from shadow storage.
2. Run SFC offline (via WinRE) with the logging option.
Run:
- diskpart
- list vol
- exit
Note the drive letter of your problematic Windows installation. Let's say it's F:

For example:
- sfc /scannow /offbootdir=f:\ /offwindir=f:\windows /offlogfile=f:\sfcoffline.txt
Attach f:\sfcoffline.txt.
Was this answer helpful?

0 comments No comments
Anonymous

2024-10-07T07:08:48+00:00

Alright, I've ran the SFC prompt from a command prompt (from a USB) and it returned an error "Windows Resource Protection could not perform a requested operation". **** (The drive letter changed to H: in this case)

Here is the sfcoffline.txt file: https://1drv.ms/t/s!Ap7bkRjaepZyggpnBErUOoEXuaD1?e=uK6Mhz

I've also downloaded and ran ShadowCopyView and it did not show any shadow copies anywhere besides the current working Windows partition. However, some time ago I've made a backup of registry while using CCleaner (See the screenshot attached), could this be of any use?![](https://learn-attachment.microsoft.com/api/attachments/00d3e005-9274-4aef-bce2-1eed94e75f6c?platform=QnA
Was this answer helpful?

0 comments No comments
Anonymous

2024-10-07T07:47:36+00:00

SFC reports a .mui file is corrupt but that's not causing the user profile issue.

A .REG file export of the entire registry is not helpful. The proper way to backup the complete registry is by backing up the hives.

I guess a reset (with Keep my files) is the only thing I can think of.

From the login screen, press and hold the Shift key and click Restart.

Click the Advanced options button.

Click on Troubleshoot.

Click the “Reset this PC” option.
Was this answer helpful?

0 comments No comments