Emrys Davies wrote:


Paul,

My first thought is to leave well alone because my computer is serving
me well without hassle. It is relatively old and will diminish
gradually as Windows fail to support it. Eventually I might decide to
buy a new one which will do the job. In the meantime I will fiddle
about and try to solve this problem. Today I ran sfc/scannow and it
looked very promising until I checked Windows Updates. It said:
'Windows Resource Protection found corrupt files but was unable to fix
some of them' a familiar story. Details are included in the CBS.Log
windir\Logs\CBS.log.

My very sincere greetings for the festive season.

The problem likely starts with something in WinSXS, rather than
in System32 say.

The CheckSUR run was supposed to do the equivalent of a
DISM /restorehealth run and fix up WinSXS. Or at least
identify what needs to be fixed in there. That's why checking
the associated logfile would be important.

You don't have to read the entire article here, just note the
path of where the output went.

https://support.microsoft.com/en-us/...e-checksur-log

%WinDir%\Logs\CBS\CheckSUR.log == C:\Windows\Logs\CBS\CheckSUR.log

echo %WinDir% # that's how you check an environment variable

notepad C:\Windows\Logs\CBS\CheckSUR.log # may be permissions problems...

Once WinSXS is healthy, then it would likely be safe to
run SFC /scannow and verify the files the OS is actually
using at the moment.

Paul