New Defender Antimalware Client Version

Page 4 of 4 FirstFirst ... 234

  1. Posts : 11,390
    Windows 10 Home x64 Version 21H2 Build 19044.1706
       #31

    I can't see anything that should necessarily stop you as far as the 2016 servers are concerned - see the info page Update for Windows Defender antimalware platform KB4052623 There are warnings in the known issues section that might apply to your setups but they are all items that I think you would have encountered before.

    Sorry I can't help. Perhaps you could create a thread of your own and include "Server 2016 & Server 2019" in its title.

    Best of luck,
    Denis
      My Computer


  2. Posts : 985
    Windows 10 Home 21H1
       #32

    Crizal said:
    You raise a very valid point. The MS document states the files creating the SFC issue are not flagged after the new update is installed. Therefore, even if one did not run DISM, SFC should not show integrity violations after the update went in. On the other hand, the way MS wrote the document, they refer to DISM after explaining the resolution. Kind of ambiguous and confusing because that could lead some to think they need to run DISM after installing the update. Now, if that's the case, then the next antimalware update should not have any issues with SFC. Fingers crossed.
    First thing this morning I restarted my PC. Ran sfc /scannow...again errors in CBS.log that couldn't be fixed.
    So I ran DISM with checkhealth...no component store corruption!!
    Then I ran DISM with Scanhealth...it said there was corruption and it could be repaired!!
    So to my way of understanding things the Scanhealth result contradicts the Checkhealth results so I don't really understand why anybody runs DISM with checkhealth. It seems a bit pointless. For that matter, so does DISM with scanhealth really.
    Anyway... I then ran DISM with Restorehealth. It said that the corruption was fixed.
    I ran sfc /scannow and it was able to fix the corruption. Just to confirm I ran sfc /scannow again. All OK now.
    Just for information to other users I didn't do any restarts in between DISM commands or SFC scans. Everything was all done from the one Administrator Command Prompt screen. Im not sure if that is the recommended method but it worked. Some users on the forum seem to do it without any restarts but Ive also seen other users talk about performing a restart after doing the DISM restorehealth. Im not sure which method is technically correct or if both are OK.
      My Computer


  3. Posts : 11,390
    Windows 10 Home x64 Version 21H2 Build 19044.1706
       #33

    First thing this morning I restarted my PC. Ran sfc /scannow...again errors in CBS.log that couldn't be fixed
    Did you extract a list of what the unrepairable entries were? Perhaps it's something else? My computers are now at v4.18.1908.7 and they all run SFC without any errors.

    Denis
      My Computer


  4. Posts : 985
    Windows 10 Home 21H1
       #34

    Try3 said:
    Did you extract a list of what the unrepairable entries were? Perhaps it's something else? My computers are now at v4.18.1908.7 and they all run SFC without any errors.

    Denis
    Hi Denis. Yeah the errors were the same as before ...the Windows Defender Powershell issue. Im guessing that on your systems you had fixed the CBS log corruptions with DISM prior to the antimalware update being installed. It seems that in my case the problem was that I hadn't performed the DISM repair prior to the new Antimalware v4.18.1908.7 update being installed by Windows Update. It seems that the update doesn't fix any existing corruptions. A DISM repair still has to be done to sort those corruptions out. Apparently then everything will be OK going forward (hopefully) lol
    Out of curiosity, do you restart your PC after executing Dism restorehealth...and then run sfc scannow after the reboot? Some seem to reboot after DISM restorehealth but others just continue in the same Command Prompt window with sfc scannow without restarting the PC after performing DISM restorehealth. Is either method OK?
    In my case I didn't restart my PC in between DISM restorehealth and SFC scannow. I did everything in the same Administrator Command Prompt window
      My Computer


  5. Posts : 11,390
    Windows 10 Home x64 Version 21H2 Build 19044.1706
       #35

    In my case I didn't restart my PC in between DISM restorehealth and SFC scannow. I did everything in the same Administrator Command Prompt window
    Yes, I did the same [last month, was it? or last year? It feels like it's been going on forever].

    Denis
      My Computer


 

  Related Discussions
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 16:33.
Find Us




Windows 10 Forums