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

Page 7 of 21 FirstFirst ... 5678917 ... LastLast
  1.    #60

    kado897 said: View Post
    I've just run Dism and it cleaned up about 1GB.
    Same here.
      My ComputersSystem Spec

  2.    #61

    kado897 said: View Post
    I've just run Dism and it cleaned up about 1GB.
    Well ran that and it only took about 2 sec's to run....found nothing.
      My ComputersSystem Spec

  3.    #62

    make sure you don't run dism with a servicing stack that's broken...
      My ComputerSystem Spec

  4. Bree's Avatar
    Posts : 11,955
    10 Home x64 (1903) (10 Pro on 2nd pc)
       #63

    kado897 said: View Post
    There is usually something in Windows Update Cleanup, maybe a couple of GB although it usually overestimates this. This time it scans for it but doesn't find anything.
    Of three machines, only two had something in Windows Update Cleanup. The one that didn't had recently been updated to 1903 by Windows Update so I guess, being its first CU after the upgrade, that makes sense.
      My ComputersSystem Spec

  5.    #64

    f14tomcat said: View Post
    MRT is the oddball weird one in the MS Monthly dance. It says Installing, when in fact it's already download the new standalone package and it's actually running the MRT scan. That gives the impression it's stuck on installing something. Guess they didn't have any better words.
    I agree - even though MS recommends Safety Scanner (msert.exe) as a more complete malware scanner, running msert.exe downloaded on this patch Tuesday still leaves MS Update to find a need to DL and run MS MSRT the same day! MS should decide on one antimalware scanner and stick to it.

    This update went fine on my desktop, but on my HP laptop, a post-update check for updates called for DL and installation of two updates already installed ~2 weeks ago, showing as installed successfully in Update History, but not showing as installed in the Control Panel list of installed updates (KB4501375 and KB4502584 - build 18362.207 and .NET updates, both from 6/27). The laptop had also already shown its build as .207 prior to installation of .239 .

    Just for fun, I tried to reinstall KB4501375 and KB4502584, only to have both fail with 'this update does not apply to your system' errors. Rebooted, checked for updates again, and still asked for KB4501375 and KB4502584.

    'Windows as SSDD...'


      My ComputersSystem Spec

  6. ThrashZone's Avatar
    Posts : 5,065
    3-Win-7Prox64 2-Win10Prox64
       #65

    Hi,
    Anyone else now getting sfc errors
    sfc /VERIFYONLY did for me and it was reported on oc.net too so I ran it and sure enough they used sfc /scannow though.

    Otherwise sfc has been pretty useless in the past never finds anything even if there is obvious corruption seen in just update listings.
      My ComputersSystem Spec

  7. Farvatten's Avatar
    Posts : 124
    Windows 10 Pro 64bit 1903 18362.295
       #66

    ThrashZone said: View Post
    Anyone else now getting sfc errors
    I got this yesterday just before this .239 update but after the Defender Platform change. After the update it was still there. Had to do a DISM Cleanup-Image on both my machines.

    sfc /scannow failing after this latest Defender Platfom update.

    Also this round my storage sense found nothing to clean up yet I lost 2 gb to the update. So for me it's appears to be cleaning up after every other update on both platforms that had 1903 clean installed.

    Also my right hand notification fly-out briefly jumped all the way across the screen again like did with 1809. But only under certain circumstances. This time it was after clearing Macrium backup notices. Before it was with USB Safe to Remove messages.
      My ComputersSystem Spec


  8.    #67

    The only flyout issue I have is when I'm typing in another application and it steals focus from it which is quite annoying.
      My ComputerSystem Spec

  9. ThrashZone's Avatar
    Posts : 5,065
    3-Win-7Prox64 2-Win10Prox64
       #68

    Hi,
    Yep just had a couple usb safe to remove errors too
    Seems explorer is not letting the devices go all that quickly anymore causing error message files might be lost....
    More fun with 1903 ilk.
      My ComputersSystem Spec

  10. f14tomcat's Avatar
    Posts : 42,453
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       #69

    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.
      My ComputersSystem Spec


 
Page 7 of 21 FirstFirst ... 5678917 ... LastLast

Related Threads
UPDATE 7/9: Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9 Source: https://support.microsoft.com/en-us/help/4501375 See also: New KB4506933 Servicing Stack Update for Windows 10 v1903 - June 27
UPDATE 6/27: Cumulative Update KB4501375 Windows 10 v1903 build 18362.207 - June 27 Microsoft has released a new cumulative Update KB4501375 via Windows Update for Windows 10 version 1903 build 18362.207 to Windows Insiders in the Release...
UPDATE 6/11: Cumulative Update KB4503293 Windows 10 v1903 build 18362.175 - June 11 Source: https://support.microsoft.com/en-us/help/4497935 See also: New KB4498523 Servicing Stack Update for Windows 10 v1903 - May 29
UPDATE 5/29: Cumulative Update KB4497935 Windows 10 v1903 build 18362.145 - May 29 Source: Announcing Windows 10 Insider Preview Build 18362 | Windows Experience Blog See also: New KB4498523 Servicing Stack Update for Windows 10 v1903...
UPDATE 5/29: Cumulative Update KB4497935 Windows 10 v1903 build 18362.145 - May 29 Source: https://support.microsoft.com/en-us/help/4505057/windows-10-update-kb4505057 See also: How to get the Windows 10 May 2019 Update version 1903
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 13:42.
Find Us