Sir, I found the solution to find the repaired files by using this formula.I found this in a forum thread which helped me to find the file repaired.
the command prompt at elevated level is
cmd.exe /c "%windir%\system32\findstr.exe /c:"[SR] Repair" %windir%\Logs\CBS\CBS.log >"F:\Users\%UserName%\Desktop\%ComputerName%-SFCResults-Repairs.Log""In my case it is corrupted explorerframe.dll
The resulti in mycase is given below
2024-07-18 09:38:33, Info CSI 0000036c [SR] Repairing 0 components
2024-07-18 09:38:33, Info CSI 0000036f [SR] Repair complete
2024-07-20 06:58:17, Info CSI 00000254 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:34{17}]"ExplorerFrame.dll" by copying from backup
2024-07-20 06:58:17, Info CSI 00000256 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:34{17}]"ExplorerFrame.dll" from store
2024-07-20 07:02:15, Info CSI 00000371 [SR] Repairing 1 components
2024-07-20 07:02:16, Info CSI 00000375 [SR] Repaired file \SystemRoot\WinSxS\Manifests\\[l:34{17}]"ExplorerFrame.dll" by copying from backup
2024-07-20 07:02:16, Info CSI 00000377 [SR] Repairing corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:34{17}]"ExplorerFrame.dll" from store
2024-07-20 07:02:16, Info CSI 00000379 [SR] Repair complete
if anything comes up I will ask in theforum. Thanks for your reply
can we see the progress when the scan runs,by using extra arguments in sfc/scannow
