[SOLVED] Help with booting, DISM, and "the component store cannot be repaired"

Yes, I tried the startup repair and it said it couldn't fix the problem. The thing is, it's starting up...but if you saw in the video....just couldn't get off that time and date page. Let me see if I can grab the log file.
 
OK, the srttrail.txt file all looks normal, at the bottom it even says "Boot status indicates that the OS booted successfully"
 
I'm not sure...because safe mode is not working either. Just a black screen, but I can see the mouse moving around.

It's getting stuck on the screensaver, and it tries to come out of it but gets put right back in a split second later.

Could this be a display driver issue?
 
OK, I switched to my old monitor to make sure it's not monitor drivers causing the issue. No luck.

I removed the nvidia geforce driver I could find with dism. No luck.

dism and sfc now seem to be running OK and they think there's no problems....



I seriously want to smash things.... I feel like we're so close but now another dead end :( This is extremely discouraging.
 
could I just remove every single oemX.inf driver with DISM until they're all gone? And then when Windows started up it would look for default ones again?
 
Or, should I just take the entire \Windows directory from the 11/29 shadowexplorer and then put that onto the C:\ partition?
 
All the drivers are loaded before login screen is displayed if it was driver you will get BSoD error.

I think its corrupted registry that is why Safe Mode wont work.
 
OMG! I was so ready to give up (I've been at this for over a week) and ready to just start over fresh. But I decided to try one last crazy thing.... I took the entire \Windows directory from the 11/29 backup via shadowexplorer and copied it over to C partition.

I got 2 BSOD's complaining about .sys files (drivers) so I went onto my surface book pro, copied them to USB and put them in system32 folder AND IT WORKED! I got to login screen and logged in and there's my stuff! WTF WINDOWS! OMG

Man thank you so much for trying to help me through this. I hope nothing bad happens from here....I'm going to take an image and try to see if I can restore it... Or try to do an upgrade install.
 
FreeBooter said:
I'm glad to know problem resolved.
Click to expand...

I cannot believe moving the ShadowExplorer entire Windows directory over is what fixed it. I have no idea what in the world caused all of these issues ughhh :(

Anyways man seriously I cannot thank you enough for helping me try to troubleshoot this. It's almost Christmas, PM me your paypal :)
 
Code: 
dism /mount-wim /wimfile:WIM:X:\Sources\Install.wim /index:1 /mountdir:C:\Mount
this command doesn't work now. it appears me "error code 123 the filename directory name or volume label syntax is incorrect"
then i seach the google, eventually i found this doc: Modify a Windows Image Using DISM
seems like the command has changed
Code: 
DISM /Mount-image /imagefile:<path_to_Image_file> {/Index:<image_index> | /Name:<image_name>} /MountDir:<target_mount_directory> [/readonly] /[optimize]}
i use the command as the doc says, it works for me, mount the .wim file suessfully
 
Sorry for bumping this old thread, but it has been very useful to me. I was in the same boat: corrupted registry which causes Windows not to boot, SFC /scannow and DISM not be able to restore anything. System Restore wasn't able to succesfully put back an older version of the system files. After restoring an older registry using Shadow Explorer the system is up and running. Took me several hours, but I really wanted to avoid a complete reinstall.

The cause for this mess was a broken GPU, which caused Windows to go into recovery and the user apparantly started a System Restore. Which for some reason broke the Windows installation completely, wouldn't be the first time I see Windows ruin itself in a repair attempt. Nowadays I disable the automatic recovery process using bcdedit.
 
pr0ton said:
Sorry for bumping this old thread, but it has been very useful to me. I was in the same boat: corrupted registry which causes Windows not to boot, SFC /scannow and DISM not be able to restore anything. System Restore wasn't able to succesfully put back an older version of the system files. After restoring an older registry using Shadow Explorer the system is up and running. Took me several hours, but I really wanted to avoid a complete reinstall.

The cause for this mess was a broken GPU, which caused Windows to go into recovery and the user apparantly started a System Restore. Which for some reason broke the Windows installation completely, wouldn't be the first time I see Windows ruin itself in a repair attempt. Nowadays I disable the automatic recovery process using bcdedit.
Click to expand...
I'm a little late, but I have a similar problem. Where did you locate the old system registry and then where did you copy it?
 
Back
Top