About to update, but found an issue with Dism

Page 2 of 2 FirstFirst 12

  1. Posts : 7,860
    Windows 11 Pro 64 bit
       #11

    I would be concerned about upgrading if the DISM scanhealth option shows problems which can't be fixed. In that situation I would first recover from the last working backup or do a repair install of the current version.
      My Computers


  2. Posts : 125
    Ten
    Thread Starter
       #12

    @Farvatten - thanks for the tip. I had internet at the time doing all this @MeAndMyComputer - Yes, followed instructions to the letter @Steve C - oh yes, I usually check and run the commands before I do an update to make sure my system is "happy". This is when I ran across this error I was getting.
    @dalchina - read post 2 and did the suggest. All is good now. Each command returns a "computer is happy". I did each step as outlined and #3 is what fixed the issue. Now all is good and I installed KB4512508. But one thing which has not changed is what I posted in #5; Windows Defender version. In the post here the member mentioned after installing KB4512508 that the platform version changed to 4.18.1908. I checked after I updated and it is still 4.18.1907.4-0. I ran Defender updates to see if that changed it and it has not.

    Maybe I will open a thread under the antivirus section and continue with that.

    Thank you everyone for the help! I am on .295
    Last edited by AirPower4ever; 21 Aug 2019 at 07:22. Reason: Additional details
      My Computer


  3. Posts : 42,634
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #13

    sounds good progress.

    Remember as soon as you reach a new stable point, update your disk image (Macrium reflect e.g.) so as to consolidate that- you can always restore that - even if your disk fails and you need a new one.
      My Computers


  4. Posts : 31,398
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #14

    AirPower4ever said:
    ... one thing which has not changed is what I posted in #5; Windows Defender version. In the post here the member mentioned after installing KB4512508 that the platform version changed to 4.18.1908. I checked after I updated and it is still 4.18.1907.4-0. I ran Defender updates to see if that changed it and it has not.
    None of my machines have seen the Platform Update to 4.18.1908 yet, even though they are fully up to date in all other respects. This is discussed in the thread:

    MS Posts Support Note About Defender SFC /Scannow Errors
      My Computers


  5. Posts : 915
    Windows 10 Pro 64bit 22H2 19045.3324
       #15

    Bree said:
    None of my machines have seen the Platform Update to 4.18.1908 yet, even though they are fully up to date in all other respects. This is discussed in the thread:

    MS Posts Support Note About Defender SFC /Scannow Errors
    Ditto...

    For others, AirPower4ever's reference to 4.18.1908 is from a post in that link.

    shockwaveriderz said:
    I'm at 18362.295 on my 3 PC's and they all have that 4.18.1908 folder and when sfc /scannow is run, there is no error conditions thrown up.
    @AirPower4ever, it's worth noting that any 'sfc /scannow' hash corruption issues regrading Powershell components you may have found are due to the Defender Platform updates starting with 4.18.1906 and not the CU's, although they may have come in at the same WU check. Once fixed they've been broken by the next Defender Platform update, but said by MS, in that same link above, to have been fixed in this next one - 4.18.1908, which shockwaveriderz post supports.
      My Computers


 

  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 01:41.
Find Us




Windows 10 Forums