Looking for a CBS.LOG interpreter

I have a rather difficult problem that may not have a solution and I would like to confirm and infirm that.

I am running version 1511 of Windows 10 that I have protected from Windows Update and that I cleaned of all bloatware and customized to the hilt. It works according to my needs and whenever I have problems I always manage to fix.

There is only one quirk: the Security and Update Settings does not open: when I click on it, it opens and closes immediately. It does not cuase me any problems, but I would like to know the cause.

I have read the online advice on fixes which involves repairing OS files via SFC -- not an option as I do not want to update Windows. I ran SFC /SCANNOW and it produced the attached CBS.LOG. I am looking for somebody who can interpret it and give me an idea on what exactly is damaged and see if there's any workaround fix. I do have the original install disc of 1511.

Thanx.

Thanx for responding.

I am familiar with the advice you linked to. Unfortunately Thatit looks like SFC did not reach the repair process that the advice covers -- it got stuck in something it could not proceed after. The online advices do not cover this problem. I need somebody ho can decipher it.

Yes, I do have thorough backups but if there is damage it happened probably very early without me being aware of it, so all the backups probably have it. That's why I would prefer to fix it, but without updating, and to know whether it's possible I need to know the damage SFC finds, but it gets stuck before it does. This requires smbdy very into Windows internals.

I certainly did not hack system files -- I do not have the knowledge to mess with that. But it is possible that updating windows 7 to 10 in place (which is what MS encouraged at that time) something was damaged. If so, will the replacement be (1) OS files of the same version 1511 and (2) only those damaged, or will there be a more recent versions and the bloatware that I got rid of (e.g., apps)?

All settings | Update & Security. I now wonder if it's because Windows Update is stopped? I dk what other settings are in there other than WU. If the price of access is enabling WU, I guess I can live without it.

I agree it's an unusual situation. When MS started to fool around with 10 and force all sorts of stuff via WU, I set my system up with the last stable version after release (1511) and never looked back. I never had the kind of problems people had with the various updates and I worked with the system instead of maintaining it. No regrets.

I only noticed the above quirk the other day (after years) because I never used that setting, and got curious why. Should have occurred to me that it's because of the stopped WU, but it has only in this exchange. If so, the matter is solved -- this exchange has helped me realize it, so thanx.

Unless somebody knows there's another reason. Incidentally, CBS.LOG indicates SFC could not do the scanning -- something got it stuck and I would not be surprised if it has to do with stopped WU too.

But

Yes, I know they are different. But when I read about fixes for the problem we're discussing, there was smtg about using DISM before SFC and for some reason my impression was it involved WU, but perhaps I misunderstood.

I stopped WU service and am using a utility called StopUpdates10.

CHKDSK does not raise any issues.

Thanks for your help.

I did and I attached the CBS.LOG file to the original message.

It got stuck on smtg and I do not understand the error -- I was hoping for somebody more technical to interpret it.