A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

SFC /scannow Defender coruption?



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old July 31st 19, 04:15 PM posted to alt.comp.os.windows-10
Terry Pinnell[_3_]
external usenet poster
 
Posts: 732
Default SFC /scannow Defender coruption?

A run today of sfc /scannow reported errors, with this message:.

"Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log."

CBS.log was largely unreadable but after research I found that this command

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log "%userprofile%\Desktop\sfcdetails.txt"

delivered a readable file.

There were thousands of apparently successful lines (I've left a few in at the top)
but here are its last 46 entries. They all seem to implicate Defender

Can anyone help me to interpret this and proceed to fix please?




2019-07-31 12:52:10, Info CSI 00005821 [SR] Verify complete
2019-07-31 12:52:10, Info CSI 00005822 [SR] Verifying 93
components
2019-07-31 12:52:10, Info CSI 00005823 [SR] Beginning Verify and
Repair transaction
2019-07-31 12:52:11, Info CSI 00005881 [SR] Verify complete

2019-07-31 12:52:11, Info CSI 00005882 [SR] Repairing 1
components
2019-07-31 12:52:11, Info CSI 00005883 [SR] Beginning Verify and
Repair transaction
2019-07-31 12:52:11, Info CSI 00005885 [SR] Cannot repair member
file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005887 [SR] Cannot repair member
file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 00005889 [SR] Cannot repair member
file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000588b [SR] Cannot repair member
file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 0000588d [SR] Cannot repair member
file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000588f [SR] Cannot repair member
file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005891 [SR] Cannot repair member
file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 00005893 [SR] Cannot repair member
file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005895 [SR] Cannot repair member
file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005898 [SR] Cannot repair member
file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005899 [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 0000589b [SR] Cannot repair member
file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000589c [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 0000589e [SR] Cannot repair member
file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000589f [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058a1 [SR] Cannot repair member
file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058a2 [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058a4 [SR] Cannot repair member
file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 000058a5 [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058a7 [SR] Cannot repair member
file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058a8 [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058aa [SR] Cannot repair member
file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 000058ab [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058ad [SR] Cannot repair member
file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058ae [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058b0 [SR] Cannot repair member
file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058b1 [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058b4 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpComputerStatus.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058b7 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpThreat.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058ba [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpThreatCatalog.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058bd [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpThreatDetection.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c0 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpPreference.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c3 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpScan.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c6 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpWDOScan.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c9 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpSignature.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058cc [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\Defender.psd1;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058ce [SR] Repair complete
2019-07-31 12:52:11, Info CSI 000058cf [SR] Committing
transaction
2019-07-31 12:52:11, Info CSI 000058d4 [SR] Verify and Repair
Transaction completed. All files and registry keys listed in this transaction have
been successfully repaired

Terry, East Grinstead, UK

Ads
  #2  
Old July 31st 19, 05:03 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default SFC /scannow Defender coruption?

Terry Pinnell wrote:
A run today of sfc /scannow reported errors, with this message:.

"Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log."

CBS.log was largely unreadable but after research I found that this command

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log "%userprofile%\Desktop\sfcdetails.txt"

delivered a readable file.

There were thousands of apparently successful lines (I've left a few in at the top)
but here are its last 46 entries. They all seem to implicate Defender

Can anyone help me to interpret this and proceed to fix please?




2019-07-31 12:52:10, Info CSI 00005821 [SR] Verify complete
2019-07-31 12:52:10, Info CSI 00005822 [SR] Verifying 93
components
2019-07-31 12:52:10, Info CSI 00005823 [SR] Beginning Verify and
Repair transaction
2019-07-31 12:52:11, Info CSI 00005881 [SR] Verify complete

2019-07-31 12:52:11, Info CSI 00005882 [SR] Repairing 1
components
2019-07-31 12:52:11, Info CSI 00005883 [SR] Beginning Verify and
Repair transaction
2019-07-31 12:52:11, Info CSI 00005885 [SR] Cannot repair member
file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005887 [SR] Cannot repair member
file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 00005889 [SR] Cannot repair member
file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000588b [SR] Cannot repair member
file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 0000588d [SR] Cannot repair member
file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000588f [SR] Cannot repair member
file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005891 [SR] Cannot repair member
file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 00005893 [SR] Cannot repair member
file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005895 [SR] Cannot repair member
file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005898 [SR] Cannot repair member
file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005899 [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 0000589b [SR] Cannot repair member
file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000589c [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 0000589e [SR] Cannot repair member
file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000589f [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058a1 [SR] Cannot repair member
file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058a2 [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058a4 [SR] Cannot repair member
file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 000058a5 [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058a7 [SR] Cannot repair member
file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058a8 [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058aa [SR] Cannot repair member
file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash
mismatch
2019-07-31 12:52:11, Info CSI 000058ab [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058ad [SR] Cannot repair member
file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058ae [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058b0 [SR] Cannot repair member
file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058b1 [SR] This component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058b4 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpComputerStatus.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058b7 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpThreat.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058ba [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpThreatCatalog.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058bd [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpThreatDetection.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c0 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpPreference.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c3 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpScan.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c6 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpWDOScan.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c9 [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpSignature.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058cc [SR] Could not reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\Defender.psd1;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058ce [SR] Repair complete
2019-07-31 12:52:11, Info CSI 000058cf [SR] Committing
transaction
2019-07-31 12:52:11, Info CSI 000058d4 [SR] Verify and Repair
Transaction completed. All files and registry keys listed in this transaction have
been successfully repaired

Terry, East Grinstead, UK


Well, what does common sense tell you ?

We've been here before.

Namely, SFC tripping over "non-executable" files.

You're having trouble with a .cdxml file. SFC isn't
supposed to be looking at those. It is supposed to look
at EXE or DLL or something along those lines. It's basically
making sure that the hardlinked materials from WinSXS to
System32 are robust and healthy. And that executables,
their signing or checksums are reasonable.

DISM restorehealth fixes up WinSXS as far as I know.
That's the servicing directory.

Windows File Protection keeps a primary copy of System32
content, and if that content is modified by malware, it
puts a backup copy of important stuff in its place. This
is supposed to prevent certain kinds of (easy) exploits.

SFC scans System32 to try to find stuff that is broken.

On some previous occasion, SFC was tripping over some
..htm or .html files, so it's not like this hasn't happened
before. And Microsoft insists on adding directories to
System32, that probably belong somewhere else, but the
"permissions" on System32 seemed like a good idea at
the time.

I cannot remember what the resolution of this problem is.
Removing what are possibly control files from a system
directory, is not a good idea, so I don't see that as
a viable option in this case.

As long as the named files are not *executable* files,
you can likely ignore stuff related to "Could not reproject"
..xml, .htm, and so on. Things containing binary executable code,
are more important, as their modification implies trouble
is brewing.

Paul
  #3  
Old July 31st 19, 11:42 PM posted to alt.comp.os.windows-10
Idaho Homo Joe
external usenet poster
 
Posts: 188
Default You deserve NO help!

You are a closet ******, anus-licking faggot!
  #4  
Old August 1st 19, 01:55 PM posted to alt.comp.os.windows-10
SC Tom[_3_]
external usenet poster
 
Posts: 4,089
Default SFC /scannow Defender coruption?



"Terry Pinnell" wrote in message
...
A run today of sfc /scannow reported errors, with this message:.

"Windows Resource Protection found corrupt files but was unable to fix
some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log."

CBS.log was largely unreadable but after research I found that this
command

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"


delivered a readable file.

There were thousands of apparently successful lines (I've left a few in at
the top)
but here are its last 46 entries. They all seem to implicate Defender

Can anyone help me to interpret this and proceed to fix please?




2019-07-31 12:52:10, Info CSI 00005821 [SR] Verify
complete
2019-07-31 12:52:10, Info CSI 00005822 [SR] Verifying
93
components
2019-07-31 12:52:10, Info CSI 00005823 [SR] Beginning
Verify and
Repair transaction
2019-07-31 12:52:11, Info CSI 00005881 [SR] Verify
complete

2019-07-31 12:52:11, Info CSI 00005882 [SR] Repairing
1
components
2019-07-31 12:52:11, Info CSI 00005883 [SR] Beginning
Verify and
Repair transaction
2019-07-31 12:52:11, Info CSI 00005885 [SR] Cannot
repair member
file [l:26]'MSFT_MpThreatCatalog.cdxml' of
Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005887 [SR] Cannot
repair member
file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell,
version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the
store, hash
mismatch
2019-07-31 12:52:11, Info CSI 00005889 [SR] Cannot
repair member
file [l:20]'MSFT_MpWDOScan.cdxml' of
Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the
store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000588b [SR] Cannot
repair member
file [l:22]'MSFT_MpSignature.cdxml' of
Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 0000588d [SR] Cannot
repair member
file [l:19]'MSFT_MpThreat.cdxml' of
Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the
store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000588f [SR] Cannot
repair member
file [l:27]'MSFT_MpComputerStatus.cdxml' of
Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005891 [SR] Cannot
repair member
file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell,
version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the
store, hash
mismatch
2019-07-31 12:52:11, Info CSI 00005893 [SR] Cannot
repair member
file [l:28]'MSFT_MpThreatDetection.cdxml' of
Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005895 [SR] Cannot
repair member
file [l:23]'MSFT_MpPreference.cdxml' of
Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005898 [SR] Cannot
repair member
file [l:26]'MSFT_MpThreatCatalog.cdxml' of
Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 00005899 [SR] This
component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 0000589b [SR] Cannot
repair member
file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell,
version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the
store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000589c [SR] This
component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 0000589e [SR] Cannot
repair member
file [l:20]'MSFT_MpWDOScan.cdxml' of
Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the
store, hash
mismatch
2019-07-31 12:52:11, Info CSI 0000589f [SR] This
component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058a1 [SR] Cannot
repair member
file [l:22]'MSFT_MpSignature.cdxml' of
Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058a2 [SR] This
component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058a4 [SR] Cannot
repair member
file [l:19]'MSFT_MpThreat.cdxml' of
Windows-Defender-Management-Powershell, version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the
store, hash
mismatch
2019-07-31 12:52:11, Info CSI 000058a5 [SR] This
component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058a7 [SR] Cannot
repair member
file [l:27]'MSFT_MpComputerStatus.cdxml' of
Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058a8 [SR] This
component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058aa [SR] Cannot
repair member
file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell,
version
10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the
store, hash
mismatch
2019-07-31 12:52:11, Info CSI 000058ab [SR] This
component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058ad [SR] Cannot
repair member
file [l:28]'MSFT_MpThreatDetection.cdxml' of
Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058ae [SR] This
component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058b0 [SR] Cannot
repair member
file [l:23]'MSFT_MpPreference.cdxml' of
Windows-Defender-Management-Powershell,
version 10.0.17134.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in
the store,
hash mismatch
2019-07-31 12:52:11, Info CSI 000058b1 [SR] This
component was
referenced by
[l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.17134.1.19d7e 6e595ade1abc2bd0ca651b4908a'
2019-07-31 12:52:11, Info CSI 000058b4 [SR] Could not
reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpComputerStatus.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058b7 [SR] Could not
reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpThreat.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058ba [SR] Could not
reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpThreatCatalog.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058bd [SR] Could not
reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpThreatDetection.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c0 [SR] Could not
reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpPreference.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c3 [SR] Could not
reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpScan.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c6 [SR] Could not
reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpWDOScan.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058c9 [SR] Could not
reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\MSFT_MpSignature.cdxml;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058cc [SR] Could not
reproject
corrupted file
\??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Mod ules\Defender\\Defender.psd1;
source file in store is also corrupted
2019-07-31 12:52:11, Info CSI 000058ce [SR] Repair
complete
2019-07-31 12:52:11, Info CSI 000058cf [SR] Committing
transaction
2019-07-31 12:52:11, Info CSI 000058d4 [SR] Verify and
Repair
Transaction completed. All files and registry keys listed in this
transaction have
been successfully repaired

Terry, East Grinstead, UK


Sorry, I can't help with the errors, but I changed

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"

to
findstr /c:"[SR] Cannot" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"


I made a batch file of it just to trim the output to the items that can't be
repaired. Made it a lot easier to Google for a fix (if there was one).
--

SC Tom


  #5  
Old August 1st 19, 04:58 PM posted to alt.comp.os.windows-10
Terry Pinnell[_3_]
external usenet poster
 
Posts: 732
Default SFC /scannow Defender coruption?

Paul wrote:

Terry Pinnell wrote:
A run today of sfc /scannow reported errors, with this message:.

"Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log."

CBS.log was largely unreadable but after research I found that this command

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log "%userprofile%\Desktop\sfcdetails.txt"

delivered a readable file.

There were thousands of apparently successful lines (I've left a few in at the top)
but here are its last 46 entries. They all seem to implicate Defender

Can anyone help me to interpret this and proceed to fix please?


skip

Terry, East Grinstead, UK


Well, what does common sense tell you ?

We've been here before.

Namely, SFC tripping over "non-executable" files.

You're having trouble with a .cdxml file. SFC isn't
supposed to be looking at those. It is supposed to look
at EXE or DLL or something along those lines. It's basically
making sure that the hardlinked materials from WinSXS to
System32 are robust and healthy. And that executables,
their signing or checksums are reasonable.

DISM restorehealth fixes up WinSXS as far as I know.
That's the servicing directory.

Windows File Protection keeps a primary copy of System32
content, and if that content is modified by malware, it
puts a backup copy of important stuff in its place. This
is supposed to prevent certain kinds of (easy) exploits.

SFC scans System32 to try to find stuff that is broken.

On some previous occasion, SFC was tripping over some
.htm or .html files, so it's not like this hasn't happened
before. And Microsoft insists on adding directories to
System32, that probably belong somewhere else, but the
"permissions" on System32 seemed like a good idea at
the time.

I cannot remember what the resolution of this problem is.
Removing what are possibly control files from a system
directory, is not a good idea, so I don't see that as
a viable option in this case.

As long as the named files are not *executable* files,
you can likely ignore stuff related to "Could not reproject"
.xml, .htm, and so on. Things containing binary executable code,
are more important, as their modification implies trouble
is brewing.

Paul


I found and successfully implemented the following fix:

1. From Admin command prompt:
DISM /Online /Cleanup-Image /RestoreHealth

2. Restart PC

3. From Admin command prompt:
sfc /scannow (Errors will be found and fixed.)

Terry, East Grinstead, UK
  #6  
Old August 1st 19, 05:41 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default SFC /scannow Defender coruption?

Terry Pinnell wrote:
Paul wrote:

Terry Pinnell wrote:
A run today of sfc /scannow reported errors, with this message:.

"Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log."

CBS.log was largely unreadable but after research I found that this command

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log "%userprofile%\Desktop\sfcdetails.txt"

delivered a readable file.

There were thousands of apparently successful lines (I've left a few in at the top)
but here are its last 46 entries. They all seem to implicate Defender

Can anyone help me to interpret this and proceed to fix please?


skip

Terry, East Grinstead, UK

Well, what does common sense tell you ?

We've been here before.

Namely, SFC tripping over "non-executable" files.

You're having trouble with a .cdxml file. SFC isn't
supposed to be looking at those. It is supposed to look
at EXE or DLL or something along those lines. It's basically
making sure that the hardlinked materials from WinSXS to
System32 are robust and healthy. And that executables,
their signing or checksums are reasonable.

DISM restorehealth fixes up WinSXS as far as I know.
That's the servicing directory.

Windows File Protection keeps a primary copy of System32
content, and if that content is modified by malware, it
puts a backup copy of important stuff in its place. This
is supposed to prevent certain kinds of (easy) exploits.

SFC scans System32 to try to find stuff that is broken.

On some previous occasion, SFC was tripping over some
.htm or .html files, so it's not like this hasn't happened
before. And Microsoft insists on adding directories to
System32, that probably belong somewhere else, but the
"permissions" on System32 seemed like a good idea at
the time.

I cannot remember what the resolution of this problem is.
Removing what are possibly control files from a system
directory, is not a good idea, so I don't see that as
a viable option in this case.

As long as the named files are not *executable* files,
you can likely ignore stuff related to "Could not reproject"
.xml, .htm, and so on. Things containing binary executable code,
are more important, as their modification implies trouble
is brewing.

Paul


I found and successfully implemented the following fix:

1. From Admin command prompt:
DISM /Online /Cleanup-Image /RestoreHealth

2. Restart PC

3. From Admin command prompt:
sfc /scannow (Errors will be found and fixed.)

Terry, East Grinstead, UK


I'm surprised the log for that is clean.

It's not normal for adjunct files to be ignored
like that. It implies they tried to fix it somehow.

Paul
  #7  
Old August 1st 19, 06:00 PM posted to alt.comp.os.windows-10
Terry Pinnell[_3_]
external usenet poster
 
Posts: 732
Default SFC /scannow Defender coruption?

"SC Tom" wrote:



"Terry Pinnell" wrote in message
.. .
A run today of sfc /scannow reported errors, with this message:.

"Windows Resource Protection found corrupt files but was unable to fix
some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log."

CBS.log was largely unreadable but after research I found that this
command

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"


delivered a readable file.

There were thousands of apparently successful lines (I've left a few in at
the top)
but here are its last 46 entries. They all seem to implicate Defender

Can anyone help me to interpret this and proceed to fix please?

skip?

Terry, East Grinstead, UK


Sorry, I can't help with the errors, but I changed

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"

to
findstr /c:"[SR] Cannot" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"


I made a batch file of it just to trim the output to the items that can't be
repaired. Made it a lot easier to Google for a fix (if there was one).


Thanks, neat. (I edited the original fairly quickly in my text editor.)

Re 'a fix', see my earlier reply.

Terry, East Grinstead, UK
  #8  
Old August 2nd 19, 12:12 PM posted to alt.comp.os.windows-10
SC Tom[_3_]
external usenet poster
 
Posts: 4,089
Default SFC /scannow Defender coruption?



"Terry Pinnell" wrote in message
...
"SC Tom" wrote:



"Terry Pinnell" wrote in message
. ..
A run today of sfc /scannow reported errors, with this message:.

"Windows Resource Protection found corrupt files but was unable to fix
some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log."

CBS.log was largely unreadable but after research I found that this
command

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"

delivered a readable file.

There were thousands of apparently successful lines (I've left a few in
at
the top)
but here are its last 46 entries. They all seem to implicate Defender

Can anyone help me to interpret this and proceed to fix please?

skip?

Terry, East Grinstead, UK


Sorry, I can't help with the errors, but I changed

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"

to
findstr /c:"[SR] Cannot" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"


I made a batch file of it just to trim the output to the items that can't
be
repaired. Made it a lot easier to Google for a fix (if there was one).


Thanks, neat. (I edited the original fairly quickly in my text editor.)

Re 'a fix', see my earlier reply.


Saw that this morning :-) Good deal!

Did SFC actually fix the errors, or just tell you it was going to? Sometimes
it lies :-(
--

SC Tom


  #9  
Old August 2nd 19, 03:53 PM posted to alt.comp.os.windows-10
Terry Pinnell[_3_]
external usenet poster
 
Posts: 732
Default SFC /scannow Defender coruption?

"SC Tom" wrote:



"Terry Pinnell" wrote in message
.. .
"SC Tom" wrote:



"Terry Pinnell" wrote in message
...
A run today of sfc /scannow reported errors, with this message:.

"Windows Resource Protection found corrupt files but was unable to fix
some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log."

CBS.log was largely unreadable but after research I found that this
command

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"

delivered a readable file.

There were thousands of apparently successful lines (I've left a few in
at
the top)
but here are its last 46 entries. They all seem to implicate Defender

Can anyone help me to interpret this and proceed to fix please?

skip?

Terry, East Grinstead, UK


Sorry, I can't help with the errors, but I changed

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"
to
findstr /c:"[SR] Cannot" %windir%\Logs\CBS\CBS.log
"%userprofile%\Desktop\sfcdetails.txt"

I made a batch file of it just to trim the output to the items that can't
be
repaired. Made it a lot easier to Google for a fix (if there was one).


Thanks, neat. (I edited the original fairly quickly in my text editor.)

Re 'a fix', see my earlier reply.


Saw that this morning :-) Good deal!

Did SFC actually fix the errors, or just tell you it was going to? Sometimes
it lies :-(


I gave it the benefit of the doubt on this occasion!

Here's where I got the fix:
https://www.tenforums.com/performanc...ml#post1683996

Terry, East Grinstead, UK
  #10  
Old August 3rd 19, 05:43 PM posted to alt.comp.os.windows-10
Don Kuenz, KB7RPU
external usenet poster
 
Posts: 29
Default SFC /scannow Defender coruption?

Terry Pinnell wrote:
Paul wrote:

Terry Pinnell wrote:
A run today of sfc /scannow reported errors, with this message:.

"Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log."

CBS.log was largely unreadable but after research I found that this command

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log "%userprofile%\Desktop\sfcdetails.txt"

delivered a readable file.

There were thousands of apparently successful lines (I've left a few in at the top)
but here are its last 46 entries. They all seem to implicate Defender

Can anyone help me to interpret this and proceed to fix please?


Well, what does common sense tell you ?

We've been here before.

Namely, SFC tripping over "non-executable" files.

You're having trouble with a .cdxml file. SFC isn't
supposed to be looking at those. It is supposed to look
at EXE or DLL or something along those lines. It's basically
making sure that the hardlinked materials from WinSXS to
System32 are robust and healthy. And that executables,
their signing or checksums are reasonable.

DISM restorehealth fixes up WinSXS as far as I know.
That's the servicing directory.

Windows File Protection keeps a primary copy of System32
content, and if that content is modified by malware, it
puts a backup copy of important stuff in its place. This
is supposed to prevent certain kinds of (easy) exploits.

SFC scans System32 to try to find stuff that is broken.

On some previous occasion, SFC was tripping over some
.htm or .html files, so it's not like this hasn't happened
before. And Microsoft insists on adding directories to
System32, that probably belong somewhere else, but the
"permissions" on System32 seemed like a good idea at
the time.

I cannot remember what the resolution of this problem is.
Removing what are possibly control files from a system
directory, is not a good idea, so I don't see that as
a viable option in this case.

As long as the named files are not *executable* files,
you can likely ignore stuff related to "Could not reproject"
.xml, .htm, and so on. Things containing binary executable code,
are more important, as their modification implies trouble
is brewing.


I found and successfully implemented the following fix:

1. From Admin command prompt:
DISM /Online /Cleanup-Image /RestoreHealth

2. Restart PC

3. From Admin command prompt:
sfc /scannow (Errors will be found and fixed.)


FWIW, that's close to the latest standard procedure followed by me
whenever any of the hundreds of W10P devices under my professional
purview starts to act up. The rote procedure below is followed before
any serious thought is given to further diagnostics.
Life's too short for reboots; note the absence of a reboot between
steps 3 through a. Time's precious too, so these steps are multi-tasked
with other work and periodically checked in the manner of food cooking
on a stove.

1. chkdsk c: /f

2. Reboot.

3. sfc /scannow

4. If step 3 is successful and device no longer "acts up" you're done.

5. sfc /scannow

6. If step 5 is successful and device no longer "acts up" you're done.

7. dism /Online /Cleanup-Image /RestoreHealth

8. If step 7 fails go back to step 1 but invoke chkdsk c: /r instead

9. sfc /scannow

a. If step 9 is successful and device no longer "acts up" you're done,
otherwise it's time to put on your thinking cap.

Thank you, 73,

--
Don Kuenz KB7RPU
There was a young lady named Bright Whose speed was far faster than light;
She set out one day In a relative way And returned on the previous night.


 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 11:05 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.