Windows 10: SFC, DISM nor Bootable USB repairs corrupted Windows 10

Hello,


sorry for my bad english and incorrect names, I am not a native speaker and I have Windows in Czech

I have recently experienced a short blackout in my area, which has probably corrupted some part of the WIndows Update or some similar programme.

After the power went back on, the computer went into an unsuccessful recovery, which put me in the troubleshooting options.


What I have tried so far:

Startup Repair
System Restore

Go back to previous build

Command dism /online /cleanup-image /restorehealth logs

Command sfc /scannow


Weirdly enough dism ... /checkhealth, dism ... /scanhealth and sfc /verifyonly logsall report a healthy image.


Then I have tried creating a bootable USB with Your MediaCreationTool and tried:

System image recovery

Booting to it and doing Startup Repair

Command dism /online /cleanup-image /restorehealth /source:esd:<usb-letter>:\sources\install.esd with and without /limitaccess


Then I have resigned and decided to go with a Factory reset, hoping to save at least my personal files.

Lo and behold, I cannot do that either. I allways get the same, non-descript error: "We have encountered a problem during <insert-action-here>. No changes were made." I do not get any error code or logs for this message.


I am sorry if I sound mean btw., it is just very frustrating


My actual last resort is to just backup as much as I can, reformat my drive and create a fresh install, but I feel I will lose so much data not necesarilly in my documents, but in apps that I really do not want to do that.


Is there anything else that I can do?

:)

 

Windows 10: sfc and dism cannot repair corruption

I was finally able to repair my Windows installation such that SFC returned a normal result.

Using a freshly downloaded USB image of W10, I did an inplace upgrade as suggested in magicandre1981's comments.

After that, there was a different file that was corrupt and could not be repaired.

Again, DISM did not initially repair this. However, I was able to determine that the file in question was located in the C:\windows\winsxs and also the C:\windows\system32 folders.

Since the previous installation did not flag that file as corrupt, I figured I could use the previous installations copy of that file as a good file.

Before running DISM again, I executed the following from an elevated command prompt and then re-booted the machine, as per instructions in an article at thewindowsclub.com which is not presently accessible. I'm not sure if the reboot is necessary, as that is not mentioned in another article.

By running DISM, and using c:\windows.old\windows\winsxs as the Source, I was able to repair the store. And then running SFC resulted in the original file being repaired.

Why this is happening, I have no idea. On a different machine, (and different internet connection/ISP) the upgraded (from W7) W10 installation also showed a corrupt file when running SFC. On that machine, DISM was able to repair it using the default Windows Update as a source.

 

Multi-bootable USB

Hey guys from TPU, couldn't find any specific thread pertaining to the question asked on title. As mentioned, I'm trying to create a bootable USB, but with many specifics boots available.

I've been trying to create one with multiple boot device including one that enables me to run Windows 10 directly on the USB Thumb Drive but to no avail.

The list of bootable images i'm trying to create are

1. Windows 10 (A full OS running from thumb drive)
2. Windows 10 ISO (Bootable disk image for fresh install)
3. MemTest86+

Have tried YUMI or UUI from the website USB PenDrive Linux but as this is my first time, i don't know how am i screwing up or am doing it right.. Anyone got a rough idea on a step by step guide? Thanks!

 

Repair Windows 7/8/10

This guide I made some time ago can also be helpful for system repairing...
Windows 10 system integrity check (SFC & DISM)