Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9 Win Update

f14tomcat said:

Got a ton of them. All seemed to be hosed up Defender components having to do with Powershell v 1.0.

Code:

2019-07-10 08:25:25, Info                  CSI    00000266 [SR] Beginning Verify and Repair transaction
2019-07-10 08:25:25, Info                  CSI    00000268 [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-07-10 08:25:25, Info                  CSI    0000026a [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-07-10 08:25:25, Info                  CSI    0000026c [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-07-10 08:25:25, Info                  CSI    0000026e [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-07-10 08:25:25, Info                  CSI    00000270 [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-07-10 08:25:25, Info                  CSI    00000272 [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-07-10 08:25:25, Info                  CSI    00000274 [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-07-10 08:25:25, Info                  CSI    00000276 [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-07-10 08:25:25, Info                  CSI    00000278 [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-07-10 08:25:25, Info                  CSI    0000027a [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-07-10 08:25:25, Info                  CSI    0000027b [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
2019-07-10 08:25:25, Info                  CSI    0000027d [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-07-10 08:25:25, Info                  CSI    0000027e [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
2019-07-10 08:25:25, Info                  CSI    00000280 [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-07-10 08:25:25, Info                  CSI    00000281 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
2019-07-10 08:25:25, Info                  CSI    00000283 [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-07-10 08:25:25, Info                  CSI    00000284 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
2019-07-10 08:25:25, Info                  CSI    00000286 [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-07-10 08:25:25, Info                  CSI    00000287 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
2019-07-10 08:25:25, Info                  CSI    00000289 [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-07-10 08:25:25, Info                  CSI    0000028a [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
2019-07-10 08:25:25, Info                  CSI    0000028c [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-07-10 08:25:25, Info                  CSI    0000028d [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
2019-07-10 08:25:25, Info                  CSI    0000028f [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-07-10 08:25:25, Info                  CSI    00000290 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
2019-07-10 08:25:25, Info                  CSI    00000292 [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-07-10 08:25:25, Info                  CSI    00000293 [SR] This component was referenced by [l:122]'Windows-Defender-Management-Powershell-Group-Package~31bf3856ad364e35~amd64~~10.0.18362.1.19d7e6e595ade1abc2bd0ca651b4908a'
2019-07-10 08:25:25, Info                  CSI    00000296 [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-07-10 08:25:25, Info                  CSI    00000299 [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-07-10 08:25:25, Info                  CSI    0000029c [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-07-10 08:25:25, Info                  CSI    0000029f [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-07-10 08:25:25, Info                  CSI    000002a2 [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-07-10 08:25:25, Info                  CSI    000002a5 [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-07-10 08:25:25, Info                  CSI    000002a8 [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-07-10 08:25:25, Info                  CSI    000002ab [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-07-10 08:25:25, Info                  CSI    000002ae [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Defender\\Defender.psd1; source file in store is also corrupted
2019-07-10 08:25:25, Info                  CSI    000002af [SR] Repair complete
2019-07-10 08:25:25, Info                  CSI    000002b0 [SR] Committing transaction
2019-07-10 08:25:25, Info                  CSI    000002b5 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

Only way I could get it fixed was to get the ISO from MS servers using the "Edge Trick", faking out the server to think I was on a Blackberry! Then I could DL the full WIM version of 18362 (4.6GB) and do a DISM repair pointing to source #6, Win Pro. Cleaned it right up.

I did almost the same thing TC ...I used the Windows Repair method, didn't use DISM method. Got a recent Windows 10 iso from MS ....using MediaCreationTool. Can't remember an update causing this much trouble.

OldMike65 said:

I did almost the same thing TC ...I used the Windows Repair method, didn't use DISM method. Got a recent Windows 10 iso from MS ....using MediaCreationTool. Can't remember an update causing this much trouble.

I tried the In-Place repair. Didn't fix it. Waste of time here. But, in that process, I guess I got some benefit, not what I was looking for. You're right..... and it's not obvious you have an issue unless you stumble on it. How many Joe Homeusers run SFC?

ThrashZone said:

Hi,
Yep happened on .175 build
Same deal
VerifyOnly and boom guess only defender updated
RestoreHealth
Scannow fixed the errors same as before.

See if installing .239 changes anything.

Tighten your seat belt.

f14tomcat said:

I tried the In-Place repair. Didn't fix it. Waste of time here. But, in that process, I guess I got some benefit, not what I was looking for. You're right..... and it's not obvious you have an issue unless you stumble on it. How many Joe Homeusers run SFC?

Good point TC ....bet not many folks even know what SFC is , much less how to use it.
Of course most of OUR members do.

f14tomcat said:

Tighten your seat belt.

ThrashZone said:

Hi,
VerifyOnly worked fine after .239 install

Congrats Mike...

ThrashZone said:

Hi,
Guess I should manually check for WD updates and see if it borks again

Shouldn't now....I already did ....no issues. Also did not find any updates besides Defender, which is normal.