cbs.log from Sfc /scannow reveals hundreds of Duplicate Ownership entries

DKO

Well-known member
Joined
Jul 17, 2016
Posts
54
My O/S is Windows 10 Pro (x64). Original Release upgraded by Windows update to TH2. Version is currently 1511 (OS Build 10586.494)

Although my sfc /scannow reports a no integrity issues nor repairs having been fixed there are hundreds of Duplicate Ownership entries which do not cause any issues are far as I can tell however I have not been able to find anything online explaining what these are or how to fix them (if they should be fixed).

I deleted the existing cbs.log immediately prior to running sfc /scannow. Go The Power suggested I submit my cbs.log and I have attached it to this post and it covers ONLY the Sfc /scannow run

View attachment DKO CBS.zip

I am hoping these can be easily fixed or are normal and should be ignored by me.

Many Thanks
 
Hello again DKO :)

The CBS log looks fine, there are no errors to worry about.


:smile9: Wonderful GTP (is it OK with you to abbreviate your alias)/. Thanks for looking.

IF its a quick one to answer, may I ask what exactly are duplicate ownership errors and why does SFC report them if a non issue?

A secondary enquiry (once again only if quick and simple to answer) is I note every Sfc /scannow generated cbs.log has hundreds of Primitive Installers committed for repair. I assume these are not repaired by sfc as they all appear again next time sfc /scannow is run. What does sfc think is the need to repair and why doesn't it do so.

Are both the above entries "sort of false/positives" that maybe MS should filter out from sfc scans, so viewers of the cbs.log can "sort the wood from the trees" or do the add important information to professionals like yourself, even if not no concern to the average User.

Thanks, Dave
 
Wonderful GTP (is it OK with you to abbreviate your alias)

That's fine, a lot of members do it, Go The Power was a user name I choose with I was 17 and have stuck with it for the past 8 years. It is after an AFL team: http://www.portadelaidefc.com.au/

IF its a quick one to answer, may I ask what exactly are duplicate ownership errors and why does SFC report them if a non issue?

I can't give you a definite answer here, but it has something I have been meaning to look into a while. I know that they are not a concern for us, I personally haven't seen a WU/SFC issue relating to this error. I believe it has something to do with SDDL and the owner information inside each manifest file, there might be a slight miss match between what is present in the manifest file and what is on the actual folder itself. If I get some time tonight I will have a look on my machine and see if I can pin this issue down some more.

A secondary enquiry (once again only if quick and simple to answer) is I note every Sfc /scannow generated cbs.log has hundreds of Primitive Installers committed for repair. I assume these are not repaired by sfc as they all appear again next time sfc /scannow is run. What does sfc think is the need to repair and why doesn't it do so.

The really tricky, and I mean really tricky thing about SFC and CBS log is that MS has not released any documentation on it. Everything which we know here at Sysnative has been 'self discovered' then later self taught in our Windows Update Academy. I don't knwo the answer to your question sorry, I would say that it has something to do with committing something to the Kernel but that is all I can really say about it.

Are both the above entries "sort of false/positives" that maybe MS should filter out from sfc scans, so viewers of the cbs.log can "sort the wood from the trees" or do the add important information to professionals like yourself, even if not no concern to the average User.

This would make it easier, but the original intent of the CBS log is not for anyone to read, except for staff at MS. If they intended for other people or 3rd parties to analyse there would be some documentation online about them.
 
Thanks again GTP :thumbsup2:.

Please don't go to any great effort on my part due to my curiosity (when not an issue to be concerned about), unless you are curious to know as well.

Regards, Dave

Aside: Hmmm my Firefox 48.0b7 doesn't seem to like this Forum if trying to add attachments to a post or selecting from [more] icons.
It would not respond when I clicked on a attachments to insert in two different posts earlier (I had to redo both via IE 11), and now, I have found it will not respond after clicking on [more] icons when I click on the one I want (does nothing).

So far, I have found IE 11 works perfectly and as expected and that, Firefox 48.0b7 still does not work as expected with all my Add-ons disabled. I will experiment with
a new clean profile next. Its pprobably some change Mozilla has done to Firefox causing the issue (but it just might be due to some tweak I did LOL).
 
EXTRACT of my last post regarding an "Aside" comment (as too late to edit original post)

Aside: Hmmm my Firefox 48.0b7 doesn't seem to like this Forum if trying to add attachments to a post or selecting from [more] icons.
It would not respond when I clicked on a attachments to insert in two different posts earlier (I had to redo both via IE 11), and now, I have found it will not respond after clicking on [more] icons when I click on the one I want (does nothing).

So far, I have found IE 11 works perfectly and as expected and that, Firefox 48.0b7 still does not work as expected with all my Add-ons disabled. I will experiment with
a new clean profile next. Its pprobably some change Mozilla has done to Firefox causing the issue (but it just might be due to some tweak I did LOL).


Just to clean up this mystery. I turned out to be related to a Firefox Add-on "Tab Mix Plus" setting. I suppose just disabling all my add-ons did not restore some settings made my add-ons to firefox defaults.

Just for info In Tabmix Plus I had (in its Links tab) section "Open Links that open in a new window in:" set to "Current tab" which caused the issue.
Had I chosen one of the other two options "New window" I would have got the small window ,or if I had chosen"New Tab" I would have got a New tab instead of a small window but BOTH worked as intended for "Manage attachments" and more icons.

I somehow (in my ignorance) managed to choose the only option of the three that did not work (I wonder how many others issues this caused where i though a website was misbehaving).
I suppose the golden rule is "unless you are sure what you are doing/changing and you know all the ramifications, then don't change them from their defaults".
Sooooo Mozilla NOT Guilty. but DKO VERY GUILTY :lol:
 
EXTRACT of my last post regarding an "Aside" comment (as too late to edit original post)

Aside: Hmmm my Firefox 48.0b7 doesn't seem to like this Forum if trying to add attachments to a post or selecting from [more] icons.
It would not respond when I clicked on a attachments to insert in two different posts earlier (I had to redo both via IE 11), and now, I have found it will not respond after clicking on [more] icons when I click on the one I want (does nothing).

So far, I have found IE 11 works perfectly and as expected and that, Firefox 48.0b7 still does not work as expected with all my Add-ons disabled. I will experiment with
a new clean profile next. Its pprobably some change Mozilla has done to Firefox causing the issue (but it just might be due to some tweak I did LOL).


Just to clean up this mystery. I turned out to be related to a Firefox Add-on "Tab Mix Plus" setting. I suppose just disabling all my add-ons did not restore some settings made my add-ons to firefox defaults.

Just for info In Tabmix Plus I had (in its Links tab) section "Open Links that open in a new window in:" set to "Current tab" which caused the issue.
Had I chosen one of the other two options "New window" I would have got the small window ,or if I had chosen"New Tab" I would have got a New tab instead of a small window but BOTH worked as intended for "Manage attachments" and more icons.

I somehow (in my ignorance) managed to choose the only option of the three that did not work (I wonder how many others issues this caused where i though a website was misbehaving).
I suppose the golden rule is "unless you are sure what you are doing/changing and you know all the ramifications, then don't change them from their defaults".
Sooooo Mozilla NOT Guilty. but DKO VERY GUILTY :lol:

LOL I do this all the time as well, thinking I dont need a setting/find a cool add on then later find out that it broke half of the functions I use in FF :P
 
I only made the mistake of that setting because I do not want Firefox to be able to open in more than one instance with same profile, which can easily happen if forgetfully double clicking a "single click" shortcut in the Task bar. I had searched everywhere via Google for a Firefox setting that permits only one instance of Firefox to run at a time, but found nothing (only how to open multiple instances with different profiles). I expected to find an about:config setting but cannot find one. The Tab Mix Plus "Single window only mode" solved the issue but (as stated in my last post) had unexpected side affects that my posting in Sysnative Forums thankfully exposed. I have now been forced to a "sledge hammer to crack nut" approach and place an AutoHotkeys script (.ahk) in my Firefox shortcuts which tests for an existing open firefox window and if found goes to that rather than opening a second and if not found then run Firefox.

(ASIDE) Whist messing around with the above I noticed (as happens occasionally) that the icon shown in my Taskbar for a running Firefox was wrong. As usual cleaning up Desktop Icon caches failed to solve and and usual I had to uninstall Firefox and reinstall (which solved) Unfortunately however, this time instead of the issue not happening again for weeks/months it happened only an hour later. So I decided to investigate. It seems Task bar icons for running apps are not got from the Desktop icon caches OR the caches are occasionally being loaded incorrectly occasionally from another source (which I checked, was not the registry).

To cut a long story short, amazingly the source in my case was actually another Firefox shortcut which I set up for running Firefox in Private Mode. I had used a different Icon for that shortcut and placed it in the Start Menu> Programs>list. Immediately below it was a normal Firefox shortcut with default icon. Whether I opened a NORMAL instance of Firefox from that normal shortcut or from the Firefox shortcut I have in a Taskbar toolbar, the icon shown in the Taskbar for the running Firefox was picking up the icon I had chosen to use for the ONLY Firefox (Private Mode) shortcut I had . GO FIGURE! . Why that icon would be picked up in preference I have NO IDEA. I moved that shortcut to of a sub folder Start Menu> Programs but that made no difference. Finally I stumbled upon the only answers 1) Deleting the (Private mode) shortcut OR 2) changing its icon to the firefox default icons. Both methods IMMEDIATELY resolved the issue.

What a weird issue and surprising solution.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top