New
#21
If the corruption is significant, then the SP1, or any other update, installation will fail so technically, you shouldn't need to run a sfc /scannow command prior to installing an update. I don't think there's a risk of the update partially installing, or installing wrong, if there are corrupt files on the system at the time of installation, the worst that will happen is that the update downloads and fails, at which point a sfc /scannow would be a good troubleshooting step. SFC by itself is pretty lousy at fixing corruption, as you've probably noticed by the number of times Noel and I have had to intervene, so just running a scan wouldn't help you all that much unless you're prepared to go down the manual route.
Another thing to note, if SFC ever reports that corrupt files were found blah blah blah, then be sure to check the CBS log before you worry. If settings.ini (of Windows Sidebar) or tcpmon.ini is ever found to be corrupt then you can safely ignore these.
It's absurd that MS have included settings.ini in the list of components scanned by SFC and they openly admit to the problem, yet no fix:
The SFC.exe command reports Settings.ini file errors in the CBS.log file after you add gadgets to the Windows Vista Sidebar by using the Sysprep tool and an Autounattend.xml file
As for tcpmon.ini, this is likely a customisation made by one of your programs so I always leave it. If you do experience networking issues, or the error code translates to something network related, then go ahead with the fix but as a general rule of thumb, leave it be.
Hope this explains a little :)
Tom