Windows 10: Windows 10 OS -DISM & sfc

Should you run DISM BEFORE you run sfc? Where does sfc get the files from when it repairs corrupt files? And, if you run DISM Offline, what resource does it use to get files to clean image? Thank you.

:)

 

Can't get SFC and DISM to work anymore on Win10

Ok, can someone help me out because this crap is starting to piss me off. There was once a time when you could simply run SFC and DISM to check Windows files integrity and if there were any problems found with the local files, Windows repaired it automatically. The reason why I want to run this is because I'm getting stupendously huge amount of errors and warnings in Event Viewer, but I don't want to run refresh because it'll mess up tons of apps.

Commands I used:
sfc /scannow
Dism /Online /Cleanup-Image /RestoreHealth

Fast forward few years and we now have glorious Windows 10. Trying to run the same tools, they find errors but stubbornly refuse to fix ANYTHING. What's the god damn point of it then?

Sfc finds issues but can't repair them and DISM constantly bitches how it can't find the source. All this used to work directly in Windows 7, but in Win 10, nothing. This was one of the best features to get OS back in good state and they go and ruin it. Because Microsoft!

I've checked this thread:
https://social.technet.microsoft.co...sfc-failed-to-repair?forum=win10itprohardware

Nothing worked. And they keep mentioning install.wim where my Windows image downloaded from Microsoft itself! only carries install.esd which I can't seem to use with anything.

I've also tried this tool:
https://dismgui.codeplex.com/releases/view/133331

Which again wants .wim file and refuses to work with esd.

 

Download Windows 10 TH/RS

*Shadedshun :shadedshu:

Dude, please stop bashing things you don't fully understand.

SFC is the first step, System File Checker. That can fix many issues using various flags and knowing the context, and is a first step when there is doubt about system integrity. This is a simple utility and using SFC /Scannow will be the most commonly used flagged command for initial repair diagnostics. Takes a few minutes and is worth doing to resolve issues. While it can repair many issues, there's also many it cannot. That's where the next step comes in should you need it.

DISM, or Deployment Image Servicing and Management, is the big gorilla in Windows OSes for repairs and image management. It has a wide variety of uses from image capture and deploy to repair.

The common command for DISM was DISM /Online /Cleanup-Image /RestoreHealth,

Just running this can result in a system being repaired, but since the launch of Windows 10, the image check has become more complicated, requiring you have the Install.WIM file available for the OS version you're trying to repair. This is relatively, though with Microsoft's deployment of Windows 10, most ISO's you get from them have an Install.ESD that must be converted to a .WIM file. Pretty easy to do with a command in CLI or Powershell.

I typed up an article about this in the past...I'll go ahead and share it here for a series of steps a person could take to repair OS corruptions in Windows 8, 8.1 and 10. It's not hard to do, but takes some attention to detail, being able to handle command line (which is easy), and a little patience.

I've personally fixed/repaired dozens if not hundreds of systems with these utilities, because simply... THEY WORK. How do I know? Because I'm a systems and network professional that has to manage 100s of Windows PCs ranging from XP to 10, and where we can use these utilities to repair corruption, we save a ton of time. My technicians, bench guys and engineers all know and use the hell out of these utilities.

I find it hard to accept your statement above as something acceptable to even say here, it clearly shows your lack of experience with using the repair utilities SFC and DISM correctly or looking into what the failures were and how to fix them appropriately. Nor is that kind of crap even what TPU is or has ever really been about, and being such a long time member I would have expected you know that...though you've always been that way so maybe it's just habitual...surely not helpful to anyone else participating in this thread, or even yourself.

The OS is literally telling you what is wrong and where it's keeping the information so you can look into it further, that's not whining, that's stating facts. Nice try though. If you don't want to learn how to fix OS corruption, don't blame the OS or tools, blame yourself and shut up about it, and don't bitch about the OS utilities whining...LOL, because in reality wouldn't your bitching mean you're whining??? *Slap :slap:

So knock that shit off and let's fix the issues instead k? *Wink

 

Eternal safe mode (windows 10)

Yea, but if something corrupts it won't detect anything. I would use the DISM command to check the health and then restore it. I usually just skip the health check and just do a Health restore. Then after the Health restore then I do the sfc /scannow command.

Check Health
Code: DISM /Online /Cleanup-Image /CheckHealth[/quote] Scan Health
Code: DISM /Online /Cleanup-Image /ScanHealth[/quote] Restore Health
Code: DISM /Online /Cleanup-Image /RestoreHealth[/quote] sfc
Code: sfc /scannow[/quote] first I would do what @Solaris17 said to check his boot record. *Toast :toast: Also, a fresh start and keep his files like you suggested is a good option as well. *Toast :toast: Maybe even check to see if he has any restore points.