How do I analyse the dism log file , a huge file and fix the errors

[jraju]

HI, when usually run the script, the script if it contains invoking dism, it works .
The log of the file is stored in windows main folder, windows logs dism dism.log
If i open the dism.log , it is huge and cannot be read which went wrong and which went right while executing the program.
If the script contain, so much invoking of the dism, how do one find out , which lines there were error and which lines which went smooth.
Is there any quick way to find out , if all went well or not when invoking dism commands thro script.
sfc scannow, has some command line to look in to the error part .
Does any command work for dism

 

[torchwood]

Hi

DISM was never set up to run on W7, usually get error code 70.

Its W7 equivalent is SURT, kb947821, use that.

 

[jraju]

Hi touchwood, But you could use dism of later versions for windows . Is it not correct.
If suppose, we use software that uses dism, then how to analyse the log. In sfc scan log, there is a tutorial of how to find the errors or missings using substr command.
Likewise, how do we analyse and fix the errors.
Dism is used to integrate , say windows updates, and if window updates failed on some Kbs , then how do we find it in a huge dism.logs
I tried to browse and did not find satisfactory materials in intrepreting dism logs

 

[torchwood]

Hi,

Were both right, Dism can be used to install updates, but it is not a system repair tool for w7.

the dism Restore health option on w7 is kb947821. it creates its own log -- SURT
when you run it post the log, it lists repaired operations whether they worked/failed and missing cab/mum files.

 

[jraju]

Hi, I did not get alert about your answer to my email. Today I saw your last replyl and I wish to state that, what you say is correct for the dism commands.
But what I am telling is about the execution of some script using dism usage.
those failed and all logs are stored only in dism.log file.
the log is such a huge pile of texts,
There is a substr function to filter error logs in sfc scannow.
But what I ask is , how do I get the logs where It went wrong , so that I could get a fix.
The query is when you are integrating or slipstreaming the windows Os with updates and not on running windows