Hello again :)
I am really glad that it the uninstall did the trick. I am still discussing with Microsoft, and will keep you in the loop, but I am currently awaiting initial issue verification, and have nothing more to post at this time.
I shall answer your questions now and post a fix separately for clarity. Please let me know if I have missed any.
Bobster52 said:
C:\Windows\system32>7B296FBO-376B-497e-B012-9C450E1B7327-2P-0.C7483456-A289-439d-8115-601632D005A0666666666666
The honest answer is that I do not know what this refers to. I am interested, and have some vague ideas, but I do not know for sure. I do not think I am able to make much of this, unfortunately, but thank you very much for posting it (it is exclusion of the small details which means I might miss something - but from this, I cannot make much sense, I am afraid).
Bobster52 said:
Do you think there will be any consiquencises from removing the the other 2 updates???
You are losing the benefits of all three updates by uninstall this update. This is not an ideal situation, and I hope for it to be temporary only. My hope is that discussions with Microsoft will go well and they will be able to figure out a generic solution I could not, provide a Customer Support hotfix, or re-release the update. I are currently awaiting the end of this discussion before I proceed further with you.
Bobster52 said:
Do you think you still want to create a whole other version key in ..._microsoft-windows-wdf-kernellibrary-mof_... (several places in the registry), with the correct hashes, to fix what should have been there????
No, I do not. That only applies when the update is installed. It is trying to create a fix for no integrity violations + update installed. So...since we have now uninstalled the update, it does not apply. My hope is that a no integrity violations + update installed fix will now come from Microsoft.
Bobster52 said:
And lastley, What do we need to do to "Clean - Up" and "Put - Back", from the 3 fixes weve already done???
Just a little tidying. I will put this into a separate post for clarity. I aim to do get this to you tonight, if at all possible. I think it will take the form of a single SFCFix script, although I will confirm that in my next post.
Bobster52 said:
While SFC found no corrupt files the last time I ran it, when I opened the CBS log I sent you it showed that repairs had been made??? Last night I ran SFC again, and again it found no corrupt files, however when I Looked at the CBS log, It again showed repairs had been made....Can you please explain this so I can understand whats going on??? (When you have the time)
An excellent question :) Nice to see you taking a look over the logs. Fortunately, there is a nice explanation.
CBS.log stores the results of many SFC runs, including all previous SFC runs. This is why it keeps growing in size.
If you look at the dates on the left, you will see that all SFC reported corruptions originate from several days ago. Well, we know there were corruptions several days ago. This is nothing revolutionary.
What is important is whether the very final run of SFC reports errors. You can safely ignore all of these historic runs of SFC and any errors in them, as long as we have fixed them in the final run.
So slide down to the very bottom of the log, and search upwards for the term "
[SR]". This will take you to the very bottom of the final SFC run. SFC summarises errors found at the end of the log (well, simplistically). If there are no errors shown in the bottom screen of the very final log, there is nothing to worry about, only historic data. This is the important thing. No errors. :)
I hope this helps.
Richard