Quote: Originally Posted by EFH
As instructed I rersn SURT ans as requested here is, the CheckSUR.persist.log Attachment 170586
and also the checksur.log Attachment 170585
I reran Windows update and its down to error codes 8024200D and 80073712
Thanks for those logs! Just those two files remaining!
Unfortunately, these files have turned out to be a very slight problem!
Basically, there is never any guarantee that I can actually find a replacement .manifest file just from that log file - a .cat or .mum file, then pretty much yes, but .manifest, only 98% of the time.
Those two were not native components, and nor were they SP1 components, and nor were they part of some of the bigger .net Framework updates. I used all of the techniques which I could to find them myself, but failed.
What this means is that to find this replacement, I need to know from which update that file originates, so I can extract you a replacement.
Have a look at the file name of a .cat file:
I immediately know which update to download. Easy! .mum as well.
However, a .manifest:
No such information. (However, it looks to come from a .net Framework update.)
Basically, the information which tells me where that manifest originated is in your registry, to which I have no easy access!
This is why I need to access your registry. Fortunately, I only need to access the COMPONENTS sub-hive. This hive only contains Windows information (as far as I am aware) It isn't any of your personal hives. I won't be able to see who you are, what programs you have installed, or anything like that. I will however, be able to see:
- Which Windows updates you have installed, and if any are corrupt, only partly installed etc. etc.
- Which language packs you have installed.
However, I am not interested, and will only look at the little bit I need to.
I do take privacy very seriously, and although many people have sent me their hives before, and there is absolutely nothing to cause concern, it is important that you understand what we are asking you or anybody to do online, so that you can make your own choices.
If you are still not comfortable, please do raise any concerns you have with me. If you are not happy with this, we can look at other options, including things like non destructive re-installs, however, we are right on the brink of a repair, if you stick with me for just a little longer. However, before we get to that, there is one last option.
I actually have a nearly finished program to automate this process (basically, an automated program works out where the .manifest file originated from)
It is completely safe, however, it might not work (because it isn't quite finished yet) However, I would not be giving it to you if it wasn't safe - which it is.
You will be the first person in the world to use this tool, after my beta testers! Hopefully it will work - its maiden run!
Please download the attached .exe file, and run it.
In the "Paste scan here:" box, please paste in the following: Trace::
and press Run.
One of two things will come up. An error message, or a log file! Hopefully a log file!
Whatever happens, please leave the message box on screen. Then, hold down the Ctrl
key on your keyboard, and whilst still holding down this key, press and release the C
key. Now release the Ctrl
key. Nothing will appear to have happened, except for a possible beep.
Now please right click and paste into a new reply here.
Now please repeat for this scan: Trace::
In future versions, this will be easier!
Hopefully, you will have pasted the contents of the message!
My fingers are very crossed, but otherwise, I will show you how to upload your COMPONENTS hive, and you can PM me the link.
Thank you very much. Personally, I do not believe that there is anything to be at all concerned about, however, *please
do speak to me if there is.