New
#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.
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.
@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
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.
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.
@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.