Windows 10 won't start after updates

[Markverhyden]

SSD wouldn't affect dism and other file repair would it?

SSD technology at a hardware level is completely different than spindles. Personally if I have a problem like your's I'd just move to a new drive.

 

[BT Computers]

SSD technology at a hardware level is completely different than spindles. Personally if I have a problem like your's I'd just move to a new drive.

So you think the SSD is bad?

 

[AlexCa]

Maybe give this a go: https://www.lazesoft.com/
It contains a Windows Recovery functionality. In my experience it works well, maybe you're lucky.

 

[alexsmith2709]

As far as im aware the command "Dism.exe /image:c:\ /cleanup-image" is not the complete command which would be why you're getting the error, try running "Dism.exe /image:c:\ /cleanup-image /revertpendingactions" This will remove any pending updates and hopefully allow you to boot.

Also make sure C:\ is the windows drive

 

[BT Computers]

Tried Lazesoft recovery already.
Used the whole "Dism.exe /image:c:\ /cleanup-image /revertpendingactions" command, was just lazy and didn't type it all here.
That was one of the 1st commands I tried. C:\ is the windows drive.
Imaging to a new spinner drive now, but not very confident that will help any.

 

[Markverhyden]

So you think the SSD is bad?

Entirely possible. When we run CLI commands those are actually much less than the regular GUI layer. So if you getting errors on properly syntaxed commands you're missing things like libraries, etc.

I seem to remember several of the data reco pro's on here commenting that when SDD's fail it's usually much worse than spindles.

After you finish the image maybe try booting from a W10 PE and try dism from there? Not sure of the situation but if it was me I'd already be leaning towards re-imaging on a new SSD. It's still under warranty so shouldn't be an issue getting it swapped.

 

[BT Computers]

Booted up to my W10 flash drive with spinner image of SSD. "Dism.exe /image:c:\ /cleanup-image /revertpendingactions"
Still says: The cleanup-image option is unknown.

 

[BT Computers]

Update. I slaved drive to my computer. Dism.exe /image:J:\ /cleanup-image /revertpendingactions
fails with the option is unknown.
Dism /Online /Cleanup-Image /RestoreHealth works fine checking my computer.
How can I get Dism to run properly on the external drive?

 

[Markverhyden]

I just did a test on my W10 laptop with the Gandalf PE as boot and dism worked on the target.

 

[AlexCa]

Avast CloudCare

Since you're already working on a clone and so risking nothing, maybe you can try to access the file system and delele all Avast related files you can find... If it happens to work and you're able to enter the OS, then you can work from there and run the Avast Uninstall Utility and re-install Avast.

 

[BT Computers]

I gave up and N&P. Even with Gandalf PE I couldn't get dism to work. I think during the update Windows file permissions got messed up.
WinSxS folder had files that were 0kb

 

[Markverhyden]

I gave up and N&P. Even with Gandalf PE I couldn't get dism to work. I think during the update Windows file permissions got messed up.
WinSxS folder had files that were 0kb

I was going to say that the error was probably because dism was looking for certain targets and couldn't find them due to drive problems.

 

[RetiredGuy1000]

I had a similar situation occur with me today. I just woke up and went into the office and the screen was blue with a ‘fail to boot’ type of message. Pressing f8 did nothing. Nor anything else.

I booted to the Win10 CD and couldn’t get anything to work either. And slaving the drive proved the drive was not the problem.

When no software utility solution works, I was forced to N&P. It’s my bench computer do it’s fine. One thing I forgot to do when I slaved the drive was to clone the disk. Missed that step but won’t forget in the future.

 

[nerd2u]

Use that as a learning experience to build a checklist to go off of.

Sent from my SM-G870W using Tapatalk

 

[MudRock]

You could try a manual registry restore. I've had that work in the past. https://theitbros.com/restore-windows-10-registry-from-backup-or-restore-point/

Doesn't really work since Microsoft broke RegBack usually. Most of these instances appear to be caused by a broken registry.