Messed with "standby list cleaner", caused some odd system behavior


  1. Guitarmageddon
    Posts : 87
    Windows 10 home
       New #1

    Messed with "standby list cleaner", caused some odd system behavior


    So a few weeks back, in the attempt at smoothing out battlefield 5 gameplay, I came across a recommendation to use the program "intelligent standby list cleaner" since the game is poorly optimized with how it parks stuff in memory apparently. I would just click the exe whenever I loaded the game. I thought "lets speed this process up" and make a system task that starts the exe on windows loading. this was my first time playing with task scheduler. I made a basic task that said to trigger the standby list cleaner on system start, and the very first startup after the fact, it caused some really odd behavior. Probably due to the standby list cleaner interfering with services loading or something. It basically caused my asus aura sync rgb settings for the motherboard/ram to go haywire, change the colors, and no longer save settings.

    I was like oh crap, so I just deleted the task I had created and figured all would be well. Nope, the behavior persisted. I could not for the life of me figure it out. So I ended up doing a system restore, and doing a registry clean which I dont usually do. But the behavior persisted. At this point I had a hunch that maybe asus aura wrote some bad settings to the motherboard or something, so I uninstalled aura sync and updated to the newest version.

    It saves the color settings now, but upon startup when I use DIFFERENT mice from my normal everyday mouse (been testing many this week) it triggers the usb connect/disconnect sounds like a dozen times before it finally idles on desktop. no odd behaviors other than this.

    So now Im curious what devices its connecting/disconnecting at startup and wondering where I can see a log for that? is there a simple program out there that can show me a log of those connects? I know this all seems really arbitrary so hopefully it makes sense. I really hate asus aura software, its so bad. And how could standby list cleaner working cause persistent issues not fixed by a simple restart. Any chance I corrupted something in the registry? System doesn't act dysfunctional in any other way.

    - - - Updated - - -

    I decided to run sfc/scannow and it gave me this result
    Messed with "standby list cleaner", caused some odd system behavior-capture.png

    And here was a snip from the log file, once it started showing errors. Probably just something unreleated I guess right? How would I fix these? Seems related to defender?

    2019-10-12 14:52:06, Info CSI 0000023e [SR] Verifying 100 components
    2019-10-12 14:52:06, Info CSI 0000023f [SR] Beginning Verify and Repair transaction
    2019-10-12 14:52:07, Info CSI 00000240 [SR] Verify complete
    2019-10-12 14:52:07, Info CSI 00000241 [SR] Verifying 14 components
    2019-10-12 14:52:07, Info CSI 00000242 [SR] Beginning Verify and Repair transaction
    2019-10-12 14:52:07, Info CSI 00000243 [SR] Verify complete
    2019-10-12 14:52:07, Info CSI 00000244 [SR] Repairing 1 components
    2019-10-12 14:52:07, Info CSI 00000245 [SR] Beginning Verify and Repair transaction
    2019-10-12 14:52:07, Info CSI 00000246 Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.
    Expected: {l:32 ml:33 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.
    Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.
    2019-10-12 14:52:07, Info CSI 00000247 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 00000248 Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.
    Expected: {l:32 ml:33 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.
    Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.
    2019-10-12 14:52:07, Info CSI 00000249 [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 0000024a Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.
    Expected: {l:32 ml:33 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.
    Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.
    2019-10-12 14:52:07, Info CSI 0000024b [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 0000024c Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.
    Expected: {l:32 ml:33 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.
    Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.
    2019-10-12 14:52:07, Info CSI 0000024d [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 0000024e Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.
    Expected: {l:32 ml:33 b:8861d55dd84b45902d2fbd8f73fd663be669f589105ce656000b77496ece0de6}.
    Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.
    2019-10-12 14:52:07, Info CSI 0000024f [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 00000250 Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.
    Expected: {l:32 ml:33 b:a27630566684ee79af41ac68dc70bbdbffc968b2489aa16be0d0fa0e0eccf0c8}.
    Actual: {l:32 b:52a143a0bcb954c7ec8b35044ef9284055c75e7e2fe316cbaa120d665c06b1a7}.
    2019-10-12 14:52:07, Info CSI 00000251 [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 00000252 Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.
    Expected: {l:32 ml:33 b:80ddeca09c6c85cde406bd9352c24cb6ca58ab17062159713f0591c46fa7b9fd}.
    Actual: {l:32 b:064d8c62e1d613524ab6f414d4906ba77d8eefc4ba2bae3ac796b3332b1681ec}.
    2019-10-12 14:52:07, Info CSI 00000253 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 00000254 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.
    Expected: {l:32 ml:33 b:dbb84a0489a5dfeecb4e850412aabb72e725e5f89319d9e158a8baa9be6470da}.
    Actual: {l:32 b:956a869d006ef2b477e146835befea9e9da6af260506389e79ce8a669906f0b3}.
    2019-10-12 14:52:07, Info CSI 00000255 [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 00000256 Hashes for file member [l:13]'Defender.psd1' do not match.
    Expected: {l:32 ml:33 b:1b1971fcbdc0abc871748d7409c696bb509c4ede12b0c748af0af96e629961b7}.
    Actual: {l:32 b:b096112fba4e3abcde87ad6dfc843c7e2d74fb469125a00404e12fbe5f054ecb}.
    2019-10-12 14:52:07, Info CSI 00000257 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 00000258 Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.
    Expected: {l:32 ml:33 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.
    Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.
    2019-10-12 14:52:07, Info CSI 00000259 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 0000025a [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-10-12 14:52:07, Info CSI 0000025b Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.
    Expected: {l:32 ml:33 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.
    Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.
    2019-10-12 14:52:07, Info CSI 0000025c [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 0000025d [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-10-12 14:52:07, Info CSI 0000025e Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.
    Expected: {l:32 ml:33 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.
    Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.
    2019-10-12 14:52:07, Info CSI 0000025f [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 00000260 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-10-12 14:52:07, Info CSI 00000261 Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.
    Expected: {l:32 ml:33 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.
    Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.
    2019-10-12 14:52:07, Info CSI 00000262 [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 00000263 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-10-12 14:52:07, Info CSI 00000264 Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.
    Expected: {l:32 ml:33 b:8861d55dd84b45902d2fbd8f73fd663be669f589105ce656000b77496ece0de6}.
    Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.
    2019-10-12 14:52:07, Info CSI 00000265 [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 00000266 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-10-12 14:52:07, Info CSI 00000267 Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.
    Expected: {l:32 ml:33 b:a27630566684ee79af41ac68dc70bbdbffc968b2489aa16be0d0fa0e0eccf0c8}.
    Actual: {l:32 b:52a143a0bcb954c7ec8b35044ef9284055c75e7e2fe316cbaa120d665c06b1a7}.
    2019-10-12 14:52:07, Info CSI 00000268 [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 00000269 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-10-12 14:52:07, Info CSI 0000026a Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.
    Expected: {l:32 ml:33 b:80ddeca09c6c85cde406bd9352c24cb6ca58ab17062159713f0591c46fa7b9fd}.
    Actual: {l:32 b:064d8c62e1d613524ab6f414d4906ba77d8eefc4ba2bae3ac796b3332b1681ec}.
    2019-10-12 14:52:07, Info CSI 0000026b [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 0000026c [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-10-12 14:52:07, Info CSI 0000026d Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.
    Expected: {l:32 ml:33 b:dbb84a0489a5dfeecb4e850412aabb72e725e5f89319d9e158a8baa9be6470da}.
    Actual: {l:32 b:956a869d006ef2b477e146835befea9e9da6af260506389e79ce8a669906f0b3}.
    2019-10-12 14:52:07, Info CSI 0000026e [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 0000026f [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-10-12 14:52:07, Info CSI 00000270 Hashes for file member [l:13]'Defender.psd1' do not match.
    Expected: {l:32 ml:33 b:1b1971fcbdc0abc871748d7409c696bb509c4ede12b0c748af0af96e629961b7}.
    Actual: {l:32 b:b096112fba4e3abcde87ad6dfc843c7e2d74fb469125a00404e12fbe5f054ecb}.
    2019-10-12 14:52:07, Info CSI 00000271 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.18362.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2019-10-12 14:52:07, Info CSI 00000272 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
    2019-10-12 14:52:07, Info CSI 00000273 Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.
    Expected: {l:32 ml:33 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.
    Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.
    2019-10-12 14:52:07, Info CSI 00000274 Hashes for file member [l:27]'MSFT_MpComputerStatus.cdxml' do not match.
    Expected: {l:32 ml:33 b:250a58b9ec6c327e7d165cecbdbae0b1fdca203cd342dba12616527b47a44486}.
    Actual: {l:32 b:cbfca6cb14b5a84f5bd30cbc9b05f008f4916e54a33a513fcedf8bff90002f5d}.
    2019-10-12 14:52:07, Info CSI 00000275 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpComputerStatus.cdxml; source file in store is also corrupted
    2019-10-12 14:52:07, Info CSI 00000276 Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.
    Expected: {l:32 ml:33 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.
    Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.
    2019-10-12 14:52:07, Info CSI 00000277 Hashes for file member [l:19]'MSFT_MpThreat.cdxml' do not match.
    Expected: {l:32 ml:33 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.
    Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.
    2019-10-12 14:52:07, Info CSI 00000278 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreat.cdxml; source file in store is also corrupted
    2019-10-12 14:52:07, Info CSI 00000279 Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.
    Expected: {l:32 ml:33 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.
    Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.
    2019-10-12 14:52:07, Info CSI 0000027a Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.
    Expected: {l:32 ml:33 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.
    Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.
    2019-10-12 14:52:07, Info CSI 0000027b [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatCatalog.cdxml; source file in store is also corrupted
    2019-10-12 14:52:07, Info CSI 0000027c Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.
    Expected: {l:32 ml:33 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.
    Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.
    2019-10-12 14:52:07, Info CSI 0000027d Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.
    Expected: {l:32 ml:33 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.
    Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.
    2019-10-12 14:52:07, Info CSI 0000027e [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpThreatDetection.cdxml; source file in store is also corrupted
    2019-10-12 14:52:07, Info CSI 0000027f Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.
    Expected: {l:32 ml:33 b:8861d55dd84b45902d2fbd8f73fd663be669f589105ce656000b77496ece0de6}.
    Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.
    2019-10-12 14:52:07, Info CSI 00000280 Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.
    Expected: {l:32 ml:33 b:8861d55dd84b45902d2fbd8f73fd663be669f589105ce656000b77496ece0de6}.
    Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.
    2019-10-12 14:52:07, Info CSI 00000281 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpPreference.cdxml; source file in store is also corrupted
    2019-10-12 14:52:07, Info CSI 00000282 Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.
    Expected: {l:32 ml:33 b:a27630566684ee79af41ac68dc70bbdbffc968b2489aa16be0d0fa0e0eccf0c8}.
    Actual: {l:32 b:52a143a0bcb954c7ec8b35044ef9284055c75e7e2fe316cbaa120d665c06b1a7}.
    2019-10-12 14:52:07, Info CSI 00000283 Hashes for file member [l:17]'MSFT_MpScan.cdxml' do not match.
    Expected: {l:32 ml:33 b:a27630566684ee79af41ac68dc70bbdbffc968b2489aa16be0d0fa0e0eccf0c8}.
    Actual: {l:32 b:52a143a0bcb954c7ec8b35044ef9284055c75e7e2fe316cbaa120d665c06b1a7}.
    2019-10-12 14:52:07, Info CSI 00000284 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpScan.cdxml; source file in store is also corrupted
    2019-10-12 14:52:07, Info CSI 00000285 Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.
    Expected: {l:32 ml:33 b:80ddeca09c6c85cde406bd9352c24cb6ca58ab17062159713f0591c46fa7b9fd}.
    Actual: {l:32 b:064d8c62e1d613524ab6f414d4906ba77d8eefc4ba2bae3ac796b3332b1681ec}.
    2019-10-12 14:52:07, Info CSI 00000286 Hashes for file member [l:20]'MSFT_MpWDOScan.cdxml' do not match.
    Expected: {l:32 ml:33 b:80ddeca09c6c85cde406bd9352c24cb6ca58ab17062159713f0591c46fa7b9fd}.
    Actual: {l:32 b:064d8c62e1d613524ab6f414d4906ba77d8eefc4ba2bae3ac796b3332b1681ec}.
    2019-10-12 14:52:07, Info CSI 00000287 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpWDOScan.cdxml; source file in store is also corrupted
    2019-10-12 14:52:07, Info CSI 00000288 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.
    Expected: {l:32 ml:33 b:dbb84a0489a5dfeecb4e850412aabb72e725e5f89319d9e158a8baa9be6470da}.
    Actual: {l:32 b:956a869d006ef2b477e146835befea9e9da6af260506389e79ce8a669906f0b3}.
    2019-10-12 14:52:07, Info CSI 00000289 Hashes for file member [l:22]'MSFT_MpSignature.cdxml' do not match.
    Expected: {l:32 ml:33 b:dbb84a0489a5dfeecb4e850412aabb72e725e5f89319d9e158a8baa9be6470da}.
    Actual: {l:32 b:956a869d006ef2b477e146835befea9e9da6af260506389e79ce8a669906f0b3}.
    2019-10-12 14:52:07, Info CSI 0000028a [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\MSFT_MpSignature.cdxml; source file in store is also corrupted
    2019-10-12 14:52:07, Info CSI 0000028b Hashes for file member [l:13]'Defender.psd1' do not match.
    Expected: {l:32 ml:33 b:1b1971fcbdc0abc871748d7409c696bb509c4ede12b0c748af0af96e629961b7}.
    Actual: {l:32 b:b096112fba4e3abcde87ad6dfc843c7e2d74fb469125a00404e12fbe5f054ecb}.
    2019-10-12 14:52:07, Info CSI 0000028c Hashes for file member [l:13]'Defender.psd1' do not match.
    Expected: {l:32 ml:33 b:1b1971fcbdc0abc871748d7409c696bb509c4ede12b0c748af0af96e629961b7}.
    Actual: {l:32 b:b096112fba4e3abcde87ad6dfc843c7e2d74fb469125a00404e12fbe5f054ecb}.
    2019-10-12 14:52:07, Info CSI 0000028d [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\Defender.psd1; source file in store is also corrupted
    2019-10-12 14:52:07, Info CSI 0000028e [SR] Repair complete
    2019-10-12 14:52:07, Info CSI 0000028f [SR] Committing transaction
    2019-10-12 14:52:07, Info CSI 00000290 Creating NT transaction (seq 1)
    2019-10-12 14:52:07, Info CSI 00000291 Created NT transaction (seq 1) result 0x00000000, handle @0x310
    2019-10-12 14:52:07, Info CSI [email protected]/10/12:18:52:07.384 Beginning NT transaction commit...
    2019-10-12 14:52:07, Info CSI [email protected]/10/12:18:52:07.386 CSI perf trace:
    CSIPERF:TXCOMMIT;2030
    2019-10-12 14:52:07, Info CSI 00000294 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
      My Computer
    Quote Quote

  3. EdTittel
    Posts : 4,224
    Windows 10
       New #2

    This PowerShell issue relates to mismatch hash values between the updates from Defender vs. what was included in the image files during a recent upgrade or update. I'm told you can fix it (and have experienced this for myself) by running DISM /online /cleanup-image /restorehealth, then SFC /scannow. However, the error is associated with an older Defender antimalware engine (4.17.x.x). Current versions should be running a 4.18.x.x version (see below) and shouldn't be subject to this problem:
    Messed with "standby list cleaner", caused some odd system behavior-image.png

    Thus, upgrading Defender may fix the problem for you (if it is indeed involved).
    HTH,
    --Ed--
      My Computers
    Quote Quote

  4. Guitarmageddon
    Posts : 87
    Windows 10 home
    Thread Starter
       New #3

    EdTittel said:
    This PowerShell issue relates to mismatch hash values between the updates from Defender vs. what was included in the image files during a recent upgrade or update. I'm told you can fix it (and have experienced this for myself) by running DISM /online /cleanup-image /restorehealth, then SFC /scannow. However, the error is associated with an older Defender antimalware engine (4.17.x.x). Current versions should be running a 4.18.x.x version (see below) and shouldn't be subject to this problem:
    Messed with "standby list cleaner", caused some odd system behavior-image.png

    Thus, upgrading Defender may fix the problem for you (if it is indeed involved).
    HTH,
    --Ed--
    Ok that seems to make sense for part of my issue. I ran DISM and it said all was fixed. Prior to this, I actually unpaused updates because in the midst of the odd behaviors when this issue presented, windows did an update and I thought it could have been from that. So I ran a system restore, and paused updates. This morning though I resumed them and got current again. Ran dism, said it was fixed, and confirmed with SFC/Scannow. Going to play around some more and see if the behavior persists.
      My Computer
    Quote Quote

  6. Bree
    Posts : 25,011
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       New #4

    EdTittel said:
    ...However, the error is associated with an older Defender antimalware engine (4.17.x.x). Current versions should be running a 4.18.x.x version (see below) and shouldn't be subject to this problem... Thus, upgrading Defender may fix the problem for you...
    As I understand it, the fix in the 4.18.x.x platform update prevents it causing the hash mismatch as it is installed, but would not cure the problem if it had already been caused by a previous update without the fix. For that you need to run DISM....
    Guitarmageddon said:
    Ok that seems to make sense for part of my issue. ... Ran dism, said it was fixed, and confirmed with SFC/Scannow.....
    SFC did a bit more than just confirm all was well. DISM just fixed the component store, SFC /Scannow could then repair the system from the (now) repaired store.
      My Computers
    Quote Quote

  7. Guitarmageddon
    Posts : 87
    Windows 10 home
    Thread Starter
       New #5

    Seems though that the usb connect/disconnect on startup is still acting...."different." Maybe a case of me just being picky and noticing some different behavior upon changing hardware? i dont know.... still looking for a way to log device connect/disconnect activity from pressing power button through to the desktop. cant find that in event viewer, or at least enough for me to decipher.
      My Computer
    Quote Quote

 

  Related Discussions
Hi all, I have been searching the web for an answer to this question since first getting Windows 10 last year. I would like my File Explorer to open using the "List" view rather than the current default of "Details". I have seen many responses...
Is it possible to change "Open" and "Save As" windows view to "List" instead of "Details" globally without having to set List view in File Explorer? I would like to use Details view in File Explorer and List view for "Open" and "Save As" windows. ...
My "User Profiles" list includes 3 entries labelled "Account Unknown". Looking at the profiles listed in the registry in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList, it seems that the accounts are three accounts with...
I can't find any information about this, but did MS, for whatever reason, remove the toggle option on the WiFi settings to turn off WiFi during modern standby? The option isn't available anymore for my laptop. I am speaking about this option: ...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 05:39.
Find Us




Windows 10 Forums