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

CountMike · 15 Jul 2019

sportsfan148 said:

Hi Mike, Im the same as you. I always run an sfc scan after Windows Updates. Thats why I immediately ran sfc scannow after the clean OS installation because quite a few windows updates were installed. . That's how I stumbled across the issue.
The only dism command Ive run in the past is dism /online /cleanup-image /restorehealth to fix sfc scan problems.
What is dism /online /cleanup-image /startcomponentcleanup /ResetBase? Im unfamiliar with that.
Is it a necessary command or is dism /online /cleanup-image /restorehealth sufficient?
I know dism also has the /checkhealth and /scanhealth switches...but in my experience they seem to be a bit of a waste of time. Ive always just used the /restorehealth switch straight away.
Any feedback/advice on the best way to use DISM would be much appreciated

That DISM line cleans up whatever is left from Disk Cleanup, that's why I use it after updates and before backup to make backup at least bit smaller.

sportsfan148 · 15 Jul 2019

You seem to use SFC scan quite regularly as I do. What system do you use when accessing the CBS log file? ...because every additional time I run an SFC scan the log file keeps getting added to so the file gets bigger and bigger. I have to use "Find" and then type in "cannot repair" in the text box in order to locate any errors without reading through the entire log. So when trying to find what the SR errors are it obviously also finds older errors that you've already fixed.
I also have a CBSpersist log file in logs. I haven't a clue what that is? Is that anything to do with SFC?

CountMike · 15 Jul 2019

sportsfan148 said:

You seem to use SFC scan quite regularly as I do. What system do you use when accessing the CBS log file? ...because every additional time I run an SFC scan the log file keeps getting added to so the file gets bigger and bigger. I have to use "Find" and then type in "cannot repair" in the text box in order to locate any errors without reading through the entire log. So when trying to find what the SR errors are it obviously also finds older errors that you've already fixed.
I also have a CBSpersist log file in logs. I haven't a clue what that is? Is that anything to do with SFC?

Haven't had to read log file in long time, it usually fixes itself automagically. Didn't understand much of it anyway.

er557 · 15 Jul 2019

after running sfc /verifyonly, or /scannow for that matter,
this command in admin command prompt will create a file on the desktop with easy to read and scroll view of exact places with errors inluding the time of the scan so you can sift through the irrelevant previous scans.

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt

CountMike · 15 Jul 2019

This is what was reported as repaired

Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9-image.png

f14tomcat · 15 Jul 2019

CountMike said:

This is what was reported as repaired

Those are the culprits.

FYI, a batch file exists to do that command string. sfc /scannow found corrupted file that could not be corrected.

CountMike · 15 Jul 2019

f14tomcat said:

Those are the culprits.

FYI, a batch file exists to do that command string. sfc /scannow found corrupted file that could not be corrected.

Third consecutive sfc /scannow after reboots in between fixed it, it's clear now.

ThrashZone · 15 Jul 2019

Hi,
Yeah windows defender
I finally had to just use Brinks reg to turn it off it's such a bloody pest now dismiss is a over and over ordeal that has to be repeated after every freaking restart or cold start

CountMike · 15 Jul 2019

ThrashZone said:

Hi,
Yeah windows defender
I finally had to just use Brinks reg to turn it off it's such a bloody pest now dismiss is a over and over ordeal that has to be repeated after every freaking restart or cold start

Did you replace it with some other AV ?

Anak · 15 Jul 2019

sportsfan148 said:

You seem to use SFC scan quite regularly as I do. What system do you use when accessing the CBS log file? ...because every additional time I run an SFC scan the log file keeps getting added to so the file gets bigger and bigger. I have to use "Find" and then type in "cannot repair" in the text box in order to locate any errors without reading through the entire log. So when trying to find what the SR errors are it obviously also finds older errors that you've already fixed.
I also have a CBSpersist log file in logs. I haven't a clue what that is? Is that anything to do with SFC?

I also have a CBSpersist log file in logs. I haven't a clue what that is? Is that anything to do with SFC?

Yes, it does relate to SFC:

What is CBS.log?

CBS stands for component based servicing. CBS.log is a file which include logs about components when they get installed or uninstalled during updates.

If you want to check these files, they are located at %windir%\Logs\CBS\

You will see two files in CBS folder, one is CBS.log and the other is CBS.persist.log. CBS.persist.log is the older of these two and is generated when the CBS.log is around 35-40 MB. Persist log folder can easily be dumped.

You need administrator rights to open these log files.

Reference:
CBS is not the television network, rather it’s your new Patch logs
What is CBS.LOG? The Component-Based Servicing log for Vista. - Aaron Tiensivu's Blog

Source

The CBS.persist.log gives a longer timeline of the past performance of your machine and should only be 'dumped' if you are sure that your machine is working okay.

sportsfan148 said:

Any feedback/advice on the best way to use DISM would be much appreciated

So far since this Defender problem has been discovered I've seen one or three or more ways that consistently fix the problem:

Run SFC then DISM
RUn SFC, DISM, then SFC again
Run DISM, then SFC
With or without reboots in the beginning of running these scans or in between SFC or DISM but it looks like one needs to at least do a reboot after DISM
Here's one by bastet that Try3 likes. From Try3's Post#99

And there are a few more combinations that will work, it's a tossup of what will work because of the different permutations that each machine carries. If one doesn't work try another. Yeah it's a crapshoot.