Hi Andrey,pro,
sorry for being real slow
http://forum.avast.com/Smileys/default/tongue.gif but it took an eternity to get all things done (carrying them out through a painfully slow cdless netbook..).
Anyway I executed both your commands and I got the same reply I got earlier: "... Windows Resource Protection found corrupt files but was unable to fix some of them.Details are included in the CBS.log...".
It appears that files cannot be restored as "source file in store is also corrupted".
I also noticed that sfc didn't log anything as my CBS.log remained the same, with old details.
Googling I found that I had to set an environmental variable (set WINDOWS_TRACING_LOGFILE=H:\TEMP\CBS.log where H is my pendrive) so I have been able at least to get a relevant log to analyze.
Further, as I'm still not sure to have understood what I exactly had to do with all that image extracting part, I've run the sfc command twice, with the following syntaxes:
1) sfc /scannow /offbootdir=H:\3 /offwindir=C:\windows
(where H:\3 stands for the name of the directory on my pendrive that is a copy of what came out to be index number and directory name for "Vista Home Premium 32 bit" files from install.wim file on my recovery dvd)
2) sfc /scannow /offbootdir=C:\ /offwindir=C:\windows
These commands were both run booting from my recovery dvd and going to the command prompt. Had I used the pendrive to boot I'd have used "D:" for windows directory path on system path instead of "C:".
I cannot anyway understand why of this system drive recognition difference booting from the pendrive (with "Vista32 rc.iso" in English) or from my recovery dvd in Italian, but I don't expect I can have any different final result booting from the pendrive.
I tried to attach a zip file of the obtained CBS.log (about 2,5 Mb) but it's not an allowed format, so I don't know how to let you have the log, given size limits enforced
Thanks a million
P.S. There is no dism.exe file in my system32 (or other) directory