New
#31
Option 1
then Option 2
then option 3
You inserted setup media for windows 10 (10586)
?????????????
You have a corrupt Journal file and shortcut - hash mismatch
Error DISM restorehealth
-
-
New #32
winver - 1511-10586.3
YES =1,2,3,4,5,6 is OK 7-error 8-ok,9-find this corupt file
what is solution ?
i run now again Dism /Online /Cleanup-Image /RestoreHealth
and now sfc/scannow ...
-
-
New #34
option 1 -succes
finish now sfc/scannow-still corupt file found
-
New #35
I give up... Never asked YET about option 8...
And the results are not success
run option and post pic of cmd windowsThe preferred method of use would be to select
Option 1 ScanHealth > if shows as repairable,
then
Option 2 RestoreHealth > if shows as needing source file,
then
Option 3 RestoreHealth /source
-
New #36
option1- no component store corruption detected
the operation completed successfully
..
option2- idem
-
New #37
then the issue with SFC is a mis-matched file hash..
then the issue is most likely caused by a windows update...
The mis-match is not a cause for alarm - just an annoyance
-
-
-
New #39
The mis-match is not a cause for alarm - just an annoyance
Write MS and ask them to fix the security Hash for the journal files
-
New #40
Hey OP, the this fix actually works, but one thing to clarify, I used the Windows 10 ISO as a source but what is actually being mounted? I assume its the install.wim BUT step 4 still returned an error unable to find at source or somethng even though the folder was in the install.wim.
I manually opened install.wim with 7zip found the file and copied to Winsxs which fixed the issue but as I say your script was unable to do this automatically.
My problem was that amd64_microsoft-windows-wusa_31bf3856ad364e35_10.0.10240.16384_none_b501032bb34a25d0\wusa.exe was missing (not corrupt)
Thanks you were vital to resolving my problem.
Quote
Related Discussions
