Windows 10: Problems with SFC, Dism and Windows Update

Greetings!

I have the following problem in progress.
I try to update Windows and give error 0x8007025d, so when I run and SFC it stops at 57 percent.
I wanted to do an inplace to solve the problem however, MediaCreationTool1909 returns me that I have to update to 2004, but the update for 2004 is not yet available for my notebook on Windows Update, the warning that I have to wait for the update to appear is displayed. my device.
"The Windows 10 update of May 2020 is on its way.
When your device is ready you will see the update available on this page. "
I've tried to repair Windows Update in whatever way I found on the internet, so here comes my question, does anyone know how to force Windows Update to update in brute force mode, or redoing my question, how to find out exactly which files are corrupt and how reset them from a Windows installation media, since the Dism command doesn't work either?

The dialogues follow.

There were problems installing some updates, but we'll try again later.

2020-06 Cumulative Update for Windows 10 Version 1909 for x64-based Operating Systems (KB4560960) - Error 0x8007025d

Microsoft Windows [version 10.0.18363.836]
(c) 2019 Microsoft Corporation. All rights reserved.

C: \ windows \ system32> Sfc / scannow

Starting file verification. The process will take a few minutes to complete.

Starting verification phase of system verification.
57% verification completed.

Windows Resource Protection cannot perform the requested operation.

C: \ windows \ system32> Dism / Online / Cleanup-Image / RestoreHealth

Deployment Image Maintenance and Management Tool
Version: 10.0.18362.1

Image Version: 10.0.18363.836

[================= 29.6%]
Error: 605

The specified buffer contains malformed data.

The DISM log file can be found at C: \ windows \ Logs \ DISM \ dism.log

C: \ windows \ system32>

:)

 

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:
CodePlex Archive

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

 

How to get damn DISM to work?

you need to run DISM first before running SFC
SFC query's the local component stores to make repairs
DISM is targeted for rebuilding the component stores and a offline image the 'live' section is still handled by SFC in some cases
except on windows 8.1 and up because they changed it
but only for certain files and only if x part of the store is corrupt
so yea pretty confusing eh

 

How to get damn DISM to work?

Thx guys, I'll compress this data into a blog post. For all the so called guides I've read, not a single one mentioned it has to be WIM file (some listed even ESD which clearly doesn't work) or that certain ISO images don't work with DISM.

After I've done DISM thingie, SFC also managed to repair stuff. Which is what I've needed here.