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

Page 11 of 21 FirstFirst ... 910111213 ... LastLast
  1. hTconeM9user's Avatar
    Posts : 2,765
    Windows 10x64 Home Version 1909 (Build 18363) 836
       #100

    All installed and working ok laptop very fast startup and shut down also working very well with office insider latest build
      My Computer

  2. EdTittel's Avatar
    Posts : 3,753
    Windows 10
       #101

    @Try3: thanks Denis! I'll keep my eye out for that. Much-appreciated.
    --Ed--
      My Computers

  3. sportsfan148's Avatar
    Posts : 839
    Windows 10 Home
       #102

    EdTittel said:
    @Try3: thanks Denis! I'll keep my eye out for that. Much-appreciated.
    --Ed--
    Hi Ed, Ive just completed a full clean install, deleted all partitions etc. After setting things up, getting all windows updates and latest drivers etc. I ran sfc scannow and those errors related to Windows Defender are there for me too in the CBS logs file. Im undecided whether to fix it or leave well alone and wait and hope that Microsoft produces a fix for it
      My Computer

  4. EdTittel's Avatar
    Posts : 3,753
    Windows 10
       #103

    I'm not getting those errors on any of my 6 1903 PCs. Methinks it may therefore be driver (or driver framework) related.
    --Ed--
    Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9-image.png
      My Computers

  5. slicendice's Avatar
    Posts : 4,515
    Windows 10 Pro x64 v2004 Build 19041.264 (Branch: Release Preview)
       #104

    EdTittel said:
    I'm not getting those errors on any of my 6 1903 PCs. Methinks it may therefore be driver (or driver framework) related.
    --Ed--
    Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9-image.png
    Have you recently ran dism and sfc?
      My Computers

  6. Try3's Avatar
    Posts : 4,390
    Windows 10 Home x64 Version 1909 Build 18363.778
       #105

    EdTittel said:
    I'm not getting those errors on any of my 6 1903 PCs. Methinks it may therefore be driver (or driver framework) related.

    Ed,

    If your Windows defender, Settings, About shows Antimalware client version 4.18.1906.3 or greater then you have avoided the SFC problem.

    [For those of use who were afflicted, the problem appeared after updating from 4.18.1905.4 to 4.18.1906.3]

    Denis
      My Computer

  7. galileo's Avatar
    Posts : 264
    Windows 10 Pro
       #106

    WEKJR said:
    I installed 18362.239 and ran SFC /scannow and got the error message. Than I ran dism.exe /online /cleanup-image /restorehealth and reran SFC /scannow with no errors.

    WEK
    ...same here...no issues after cleanup
      My Computer


  8. Farvatten's Avatar
    Posts : 341
    Windows 10 Pro 64bit 2004 19041.264
       #107

    EdTittel said:
    I'm not getting those errors on any of my 6 1903 PCs.
    Try3 said:
    If your Windows defender, Settings, About shows Antimalware client version 4.18.1906.3 or greater then you have avoided the SFC problem.


    I hadn't though of that, avoiding the problem if your latest Defender Platform updated from 4.18.1905.4-0 to 4.18.1906.3-0 AFTER .this 239 CU

    Ed, I first saw the Defender Powershell hash problem appear in my sfc /scannow checks the night BEFORE this .239 CU when my Defender Platform updated from 4.18.1905.4-0 to 4.18.1906.3-0.


    sfc /scannow failing after this latest Defender Platfom update.
      My Computers

  9. Try3's Avatar
    Posts : 4,390
    Windows 10 Home x64 Version 1909 Build 18363.778
       #108

    Yes, the CU is not the cause of the SFC problem. It's the WD platform update that causes it.

    Denis
      My Computer

  10. ThrashZone's Avatar
    Posts : 6,013
    3-Win-7Prox64 2-Win10Prox64
       #109

    EdTittel said:
    I'm not getting those errors on any of my 6 1903 PCs. Methinks it may therefore be driver (or driver framework) related.
    --Ed--
    Hi,
    Nope you just came back in time to miss the fun
      My Computers


 

Related Threads
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