Root Certificates update confusion
magicfrizbees
16 Oct 2011
There seems to be an issue with the Root Certificates update - Autopatcher and Windows Update keep wanting to apply different versions.
Autopatcher downloads (from Microsoft?) a 358,312 byte version with a Digital Signature dated September 1, 2011.
Windows Update (and the Microsoft download site) have a 358,304 byte version with a Digital Signature dated May 25, 2001. There WAS a newer September update on their site a month ago, but it's gone now.
How does Autopatcher manage to get a different/newer version of this file than Microsoft claims is available? Is there some other download location?
I posed the question about the most current Root Certificates on the Microsoft Answers Site and didn't really get a clear answer.
Thanks for any input!
Autopatcher downloads (from Microsoft?) a 358,312 byte version with a Digital Signature dated September 1, 2011.
Windows Update (and the Microsoft download site) have a 358,304 byte version with a Digital Signature dated May 25, 2001. There WAS a newer September update on their site a month ago, but it's gone now.
How does Autopatcher manage to get a different/newer version of this file than Microsoft claims is available? Is there some other download location?
I posed the question about the most current Root Certificates on the Microsoft Answers Site and didn't really get a clear answer.
Thanks for any input!
Cristiano
17 Oct 2011
very often, that issue happen and the reason for that is very simple: ms has an static always up-to-date download link for rootcerts and autopatcher takes that one. so, every single time that this link is updated, autopatcher users us to notice, but ms doesn't update windows update settings very often and due that they take an download link for an specific version, that a lot of times is out of sync with the version that has an static link to an specific version. due that, for an certain time (sometimes, for months or even years) the users that run WU face an outdated version of something. enu users doesn't see that, but the non-english users can notice an interesting thing: since 3 or 4 years ago (i don't recall right now), WU offers a few language packs for the .nets. the problem: those updates can't be deployed since .net 3 sp1 and no one at microsoft bothered to remove those obsolete things yet
the funny thing is that you may check for this registry key:
RegistryPath=HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{EF289A85-8E57-408d-BE47-73B55609861A}
KeyName=Version
KeyValue=30,0,2195,0
when this issue happen, if you deploy the version from wu, you can check that registry key and you will notice that the version that you have is at least 1 version out of date. if you wish, you can check that again after deploy the version that is downloaded by apup
i'm not sure about other users, but there's some time already that i only have one option under w7: check ok or not for the updates that are deployed, because the update list has gone, from the pcs at my job and at my home and so far, ms didn't cared enough to solve that
[]s
the funny thing is that you may check for this registry key:
RegistryPath=HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{EF289A85-8E57-408d-BE47-73B55609861A}
KeyName=Version
KeyValue=30,0,2195,0
when this issue happen, if you deploy the version from wu, you can check that registry key and you will notice that the version that you have is at least 1 version out of date. if you wish, you can check that again after deploy the version that is downloaded by apup
i'm not sure about other users, but there's some time already that i only have one option under w7: check ok or not for the updates that are deployed, because the update list has gone, from the pcs at my job and at my home and so far, ms didn't cared enough to solve that
[]s
_def_x_
20 Oct 2011
@magicfrizbees
It looks like rootcerts has been updated once again, pretty common.
I had to fix this issue maybe a week ago for someone else, I asked if they could email me their log file, you may also want to post your log file here next time, it is much easier to see what's going on.
... http://www.autopatch...-apup-log-file/
... http://www.autopatch...es-please-read/
It looks like rootcerts has been updated once again, pretty common.
TimeStamp: Monday, September 19, 2011 2:56:02 PM Version= 31,0,2195,0 Size: 370592 Hash: 0E85AB7F7965FE3B4ACD4AE07BD63D92
I had to fix this issue maybe a week ago for someone else, I asked if they could email me their log file, you may also want to post your log file here next time, it is much easier to see what's going on.
... http://www.autopatch...-apup-log-file/
... http://www.autopatch...es-please-read/
ViroMan
20 Oct 2011
I need to talk to frank about maby getting a wiki set up on the server and getting the main page removed so there is only a forum.
_def_x_
20 Oct 2011
ViroMan said:
I need to talk to frank about maby getting a wiki set up...
I started a thread in the Admin forums suggesting a wiki. A wiki would be nice, registered users could contribute content. I listed 2 that are free, there's probably more choices. Domenico liked the idea at the time.
Encourage Frank to install it and have you manage it, shouldn't be too difficult to maintain, the dev is usually the one who knows how to fix the broke things
ViroMan
20 Oct 2011
Ha, I just noticed the user reputation system is not working. when I saw your +1 I was thinking to my self..."why didn't he just +1 me instead of saying it?" So I tried it on you and it didn't work.
ViroMan
20 Oct 2011
Frank says he was planning to get the main page taken down this weekend already.
If there is an update for the forum he says he will get that done too.
Cristiano
20 Oct 2011
please remember him about that hijacked page. that it's present since long ago and i don't think that he tested that after say "fixed" last time
[]s
[]s
magicfrizbees
22 Nov 2011
rootsupd.exe updated by microsoft again ... digital signature now dated 10/20/2011 ... and it's causing a verification failure when running the updater



