AutoPatcher XP x86 Hotfix Depot
_def_x_
23 Jun 2011
Cristiano said:
i can't reach the admin area anymore,
Cristiano
23 Jun 2011
mike, since yesterday, i can't eat anything solid due pain (to get rid of a few medicines that could create issues bigger than the ones that i have now, i'm being forced to do an orthodontic treatment and yesterday was the torture day. so far, so good. it's winter and i didn't knew what was breath without any kind of medicine since i was an child). in one week and shortly after that, i will be so high due pain killers that i will not be able to drive to my work (and will be the first time in several years). my wins have dropped a lot since i've quit from one of my jobs and here, if you need medical care, you need pay for it (and usually, a lot). to pay to get rid of that damm 3rd molar, i'm being forced to drop a lot of bills and i'm not sure if i will be able to keep my dsl. to update things from my job, i need bypass an proxy. so far, i didn't had any problem with that, but i may have. i can't update scripts as an regular task, but i may help with some things here and there
about someone else, for sure that it's required. the url123 issue is back and the last time that someone fixed that thing we had the worst spammer attack that i can remember. worst: i was unable to raise anyone to the rank that could help with that
[]s
about someone else, for sure that it's required. the url123 issue is back and the last time that someone fixed that thing we had the worst spammer attack that i can remember. worst: i was unable to raise anyone to the rank that could help with that
[]s
_def_x_
24 Jun 2011
@Cristiano
It looks like you can reach the ftp once again, you updated XP_SP3_Enu, the XP users will appreciate this.
I was hoping to get you before you did the update, I wasn't sure if you noticed I had moved a few files to a separate download:
In case you update Extras, I did something similar. The files that get updated the most are Flash, Shockwave, and Silverlight so I moved these 4 apm files to their own archive, again, for me it was a snap - you can change back if you want.
I have emailed Frank about the redirect issue, I'll give him some slack about not getting right back, he's recently moved, from one state to another so I'm sure he's trying to get things together in a new place. I'll try and keep an eye on the spam until Frank gets a new PM, hopefully it wont get out of control like last time.
It looks like you can reach the ftp once again, you updated XP_SP3_Enu, the XP users will appreciate this.
I was hoping to get you before you did the update, I wasn't sure if you noticed I had moved a few files to a separate download:
Spoiler
The idea was to make archiving the critical apm files a bit easier, before you needed to include KB968389 folder and .apf files, now all you need to do is select the critical apm files, add to archive - done! I wont mind if you should want to do it differently.In case you update Extras, I did something similar. The files that get updated the most are Flash, Shockwave, and Silverlight so I moved these 4 apm files to their own archive, again, for me it was a snap - you can change back if you want.
Spoiler
fss_modules.7z is simply Flash:Shockwave:Silverlight - The same principle here, these 4 are usually updated, just select - add to archive - done!I have emailed Frank about the redirect issue, I'll give him some slack about not getting right back, he's recently moved, from one state to another so I'm sure he's trying to get things together in a new place. I'll try and keep an eye on the spam until Frank gets a new PM, hopefully it wont get out of control like last time.
Cristiano
24 Jun 2011
yes, i've noticed that, because i saved the temp files. no big deal with those. in fact, this way is more easy avoid forget certain files
but the xp script seems to be lacking certain files or there's some kind of problem with certain updates. i've noticed that certain updates that i've listed are present in the script and they also show as installed when running ap. so, the problem could be related to wu not detecting that the update already is in place (what a news...) or there's an new version of those. in any case, i've downloaded each one and i will check it the file that wu downloaded is the same. but first i will wait until the pain get easy. at least, this one doesn't last for more than 3 days (usually)
[]s
but the xp script seems to be lacking certain files or there's some kind of problem with certain updates. i've noticed that certain updates that i've listed are present in the script and they also show as installed when running ap. so, the problem could be related to wu not detecting that the update already is in place (what a news...) or there's an new version of those. in any case, i've downloaded each one and i will check it the file that wu downloaded is the same. but first i will wait until the pain get easy. at least, this one doesn't last for more than 3 days (usually)
[]s
Cristiano
24 Jun 2011
just an head's up: i've downloaded the same files than wu has downloaded, just to check if some updates had an new version, but the versions that are in the script are the exact same than wu downloads for kb975558, kb954155 and kb973540. if those are in the script and are deployed ok (the detections state that, at least), then the problem may be related to the deploy order. those are opened to all wmp versions, meaning that those updates are deployed in this order:
kb973540: 20090810
kb954155: 20091012
kb975558: 20100412
wmp 11: 20100622
it may be an silly idea, but seems that all those are deployed before wmp11 and still wu is asking for those, then wmp11 may be ignoring the new files and creating again the need for those updates, that must be deployed after wmp11 be in place. the problem: those updates work for all wmp versions, including the one that arrives with xp. given so, possible solutions:
- edit the wmp11 module, to deploy those after himself, doesn't matter if those are in place or not;
- edit the wmp11 deploy date, to make wmp11 be deployed before those;
- change the detection of those modules be certain key files that are put in place with those updates. so, if any update deploy an older version, the deploy status will return to the "not in place" status and the user will be allowed to deploy them again or not
any ideas?
[]s
kb973540: 20090810
kb954155: 20091012
kb975558: 20100412
wmp 11: 20100622
it may be an silly idea, but seems that all those are deployed before wmp11 and still wu is asking for those, then wmp11 may be ignoring the new files and creating again the need for those updates, that must be deployed after wmp11 be in place. the problem: those updates work for all wmp versions, including the one that arrives with xp. given so, possible solutions:
- edit the wmp11 module, to deploy those after himself, doesn't matter if those are in place or not;
- edit the wmp11 deploy date, to make wmp11 be deployed before those;
- change the detection of those modules be certain key files that are put in place with those updates. so, if any update deploy an older version, the deploy status will return to the "not in place" status and the user will be allowed to deploy them again or not
any ideas?
[]s
Cristiano
24 Jun 2011
ok. the first idea works, the second don't, because if the user select those to be installed, but not wmp11, when wmp11 is deployed, then those will be viewed as already in place and, in fact, wmp11 had replaced certain files that make those updates needed again. the 3rd idea will not work, because there's one version of each key file to every wmp version that is updated. if one is in place, then it will be seen as already installed. so, the idea that fixes the issue is do like this (in wmp11 module):
[Installation]
"Module:\wmp11-windowsxp-x86-enu.exe" /q:A /c:"setup_wm.exe /Q /R:N /P:#e /DisallowSystemRestore /SetWMPAsDefault"
"autopatcher:\modules\Critical\__WMP_critical\KB973540_xp_x86_enu.apm_files\WindowsXP-WindowsMedia-KB973540-x86-ENU.exe" /quiet /norestart /overwriteoem
"autopatcher:\modules\Critical\__WMP_critical\KB954155_xp_x86_enu.apm_files\WindowsXP-WindowsMedia-KB954155-x86-ENU.exe" /quiet /norestart /overwriteoem
"autopatcher:\modules\Critical\__WMP_critical\WindowsXP-WindowsMedia-KB975558-x86-ENU.apm_files\WindowsXP-WindowsMedia-KB975558-x86-ENU.exe" /quiet /norestart /overwriteoem
so, it fixes 3 issues, but not 2: kb978695 and kb975562. with those, the problem goes deeper: there's at least an partial superseed with this one (at least, there's an reason for the removal set for those 2 long ago). the problem: with wmp11, those aren't fully replaced. kb975562 is about Quartz.dll. the version that is in place after wmp11 is 6.5.2600.5908, but kb975562 deploy 6.5.2600.5933. as WU looks for that version, wu will offer this one to be installed if the user have wmp11. with kb978695, it's the same. kb978695 deploys Wmvcore.dll. with wmp11, the system has 11.0.5721.5262, but kb978695 deploys 11.0.5721.5275 and wu looks for that. as those aren't in the script anymore and will happen the same thing than KB973540, there's only one fix: bring this ones back and set wmp11 module to deploy those as well
[]s
[Installation]
"Module:\wmp11-windowsxp-x86-enu.exe" /q:A /c:"setup_wm.exe /Q /R:N /P:#e /DisallowSystemRestore /SetWMPAsDefault"
"autopatcher:\modules\Critical\__WMP_critical\KB973540_xp_x86_enu.apm_files\WindowsXP-WindowsMedia-KB973540-x86-ENU.exe" /quiet /norestart /overwriteoem
"autopatcher:\modules\Critical\__WMP_critical\KB954155_xp_x86_enu.apm_files\WindowsXP-WindowsMedia-KB954155-x86-ENU.exe" /quiet /norestart /overwriteoem
"autopatcher:\modules\Critical\__WMP_critical\WindowsXP-WindowsMedia-KB975558-x86-ENU.apm_files\WindowsXP-WindowsMedia-KB975558-x86-ENU.exe" /quiet /norestart /overwriteoem
so, it fixes 3 issues, but not 2: kb978695 and kb975562. with those, the problem goes deeper: there's at least an partial superseed with this one (at least, there's an reason for the removal set for those 2 long ago). the problem: with wmp11, those aren't fully replaced. kb975562 is about Quartz.dll. the version that is in place after wmp11 is 6.5.2600.5908, but kb975562 deploy 6.5.2600.5933. as WU looks for that version, wu will offer this one to be installed if the user have wmp11. with kb978695, it's the same. kb978695 deploys Wmvcore.dll. with wmp11, the system has 11.0.5721.5262, but kb978695 deploys 11.0.5721.5275 and wu looks for that. as those aren't in the script anymore and will happen the same thing than KB973540, there's only one fix: bring this ones back and set wmp11 module to deploy those as well
[]s
Cristiano
24 Jun 2011
done. issues with kb978695 and kb975562 shall be solved. those are back in the script. to avoid issues with detections, KB978695 will look for this:
if any of those files are already in place, then this one will show as already installed. as for KB975562, this one will look for this:
also, those 2 will be deployed with wmp11, to avoid issues like wmp11 deploying old files and those still looking as already in place
still, there's a few updates to check
[]s
Edited by Cristiano, 24 June 2011 - 09:21 PM.
Spoiler
if any of those files are already in place, then this one will show as already installed. as for KB975562, this one will look for this:
Spoiler
also, those 2 will be deployed with wmp11, to avoid issues like wmp11 deploying old files and those still looking as already in place
still, there's a few updates to check
[]s
Edited by Cristiano, 24 June 2011 - 09:21 PM.
ViroMan
24 Jun 2011
lol this guy says he quit and here he is, STILL working his arse(curse you sware blocker!) off for us. We love you cristiano.
Edited by ViroMan, 24 June 2011 - 09:54 PM.
Edited by ViroMan, 24 June 2011 - 09:54 PM.
Cristiano
25 Jun 2011
done. after more research, a few more issues with the xp enu script was found and solved (at least i hope that):
kb2524375 and kb2492386-> this ones was missing. i don't remember right now with one is an critical update, but both require windows validation in order to be downloaded. so, both was added as non critical
KB2378111 is about Wmp.dll. the problem: this one updates that file to wmp9, 10 and 11. as wmp9 is the one that comes with windows, if the user select this one to be installed in a first round and then select wmp11 to be installed, wmp11 will deploy an file without that fix. i don't know if i did the best possible thing, but i've changed the detection for this one to be this:
with that, the script will detect the fixed versions. the problem: to have multiple file detections, one registry detection must be set and that key doesn't change when wmp11 is deployed and could make the user think that is safe, but isn't. worst at all: waste of bandwith downloading that update from wu with the update already downloaded. so, to fix the issue, this one will be silently deployed with wmp11
also, KB975562 isn't really required after wmp11 (but wu asks for that due some reason. so, this one stays in the script). so, the wmp11 will deploy those:
with that, the xp enu script shall now fully match wu
[]s
Edited by Cristiano, 25 June 2011 - 01:28 PM.
kb2524375 and kb2492386-> this ones was missing. i don't remember right now with one is an critical update, but both require windows validation in order to be downloaded. so, both was added as non critical
KB2378111 is about Wmp.dll. the problem: this one updates that file to wmp9, 10 and 11. as wmp9 is the one that comes with windows, if the user select this one to be installed in a first round and then select wmp11 to be installed, wmp11 will deploy an file without that fix. i don't know if i did the best possible thing, but i've changed the detection for this one to be this:
Spoiler
with that, the script will detect the fixed versions. the problem: to have multiple file detections, one registry detection must be set and that key doesn't change when wmp11 is deployed and could make the user think that is safe, but isn't. worst at all: waste of bandwith downloading that update from wu with the update already downloaded. so, to fix the issue, this one will be silently deployed with wmp11
also, KB975562 isn't really required after wmp11 (but wu asks for that due some reason. so, this one stays in the script). so, the wmp11 will deploy those:
Spoiler
with that, the xp enu script shall now fully match wu
[]s
Edited by Cristiano, 25 June 2011 - 01:28 PM.
Cristiano
26 Jun 2011
an bad night sleep and i've come with an idea to avoid updates being silently deployed with wmp11: set an bogus registry detection that autopatcher never will find. as doesn't matter if the registry key is present or not and this is only an condition to allow multiple file detections, i've tried to locate some key files that could as detections. if possible, can someone download the attached modules and uncompress it at modules\Critical\__WMP_critical replacing the ones that are in there? (don't run apup after that or the xp enu script will download the original files again)
the test is pretty simple: after replace the original files, run autopatcher and look if those updates show as installed (those work even with wmp9, 10 and 11, so doesn't matter if you have wmp11 or not). if not, try to deploy those to see if it solves the issue if you are unsure if those updates are already in place
sorry, but i can't test it today by myself
[]s
Edited by Cristiano, 26 June 2011 - 12:24 PM.
the test is pretty simple: after replace the original files, run autopatcher and look if those updates show as installed (those work even with wmp9, 10 and 11, so doesn't matter if you have wmp11 or not). if not, try to deploy those to see if it solves the issue if you are unsure if those updates are already in place
sorry, but i can't test it today by myself
[]s
Edited by Cristiano, 26 June 2011 - 12:24 PM.
Cristiano
08 Jul 2011
rootcerts was updated some time ago, but i didn't noticed someone reporting that in here. but reading the italian forum, someone noticed that. the script was fixed and sent to be uploaded, but that wasn't signed yet because there's more things to fix in this one
[]s
[]s
Cristiano
11 Jul 2011
now that the .net package is finally done, i will resume the work in the xp enu script. there's one missing removal to be set in this script, plus the issues regarding the wmp updates detections and also the monthly updates to do.
about the wmp updates, i didn't found an solution for the following problem:
- the updates aim 3 or 4 versions of wmp, basically from 9 to 11;
- to every single wmp, the file detection changes and the registry detection remains static;
- if the user deploys the wmp updates and later wmp11, the modules will show as already in place, but wmp11 replaced the fixed files. due that, the vulnerabilities are back in place;
- it's impossible set multiple detections for the same file. due that, only a few options remain: detect the wmp11 updates only, make wmp11 deploy those updates again if selected to install (will not help those that already have wmp11 deployed) or made one module for every single wmp
any ideas?
[]s
about the wmp updates, i didn't found an solution for the following problem:
- the updates aim 3 or 4 versions of wmp, basically from 9 to 11;
- to every single wmp, the file detection changes and the registry detection remains static;
- if the user deploys the wmp updates and later wmp11, the modules will show as already in place, but wmp11 replaced the fixed files. due that, the vulnerabilities are back in place;
- it's impossible set multiple detections for the same file. due that, only a few options remain: detect the wmp11 updates only, make wmp11 deploy those updates again if selected to install (will not help those that already have wmp11 deployed) or made one module for every single wmp
any ideas?
[]s
Cristiano
12 Jul 2011
Cristiano
14 Jul 2011
the enu script is online, but there's an issue with the location of the files that will make the script look as unofficial. it shall be solved soon. changelog:
# 07-13: ~mrt 3.21; +KB2555917; -KB2506223; +KB2507938; -KB2476687; -KB2121546; -KB955759 (replaced by KB2492386); preactions older than 2011 removed
i've forgot to mention in this log that yours may notice 15 modules under modules\Critical\__WMP_critical. as no one give the slight hint about how to solve the detection issue described above, instead have 5 modules, i've extracted the content of each update with that issue and did one module for each wmp version. that shall detect the proper version for each wmp and those modules will show only if the wmp that they target is present. sorry, but it's really impossible do an single module to look for the same file with only an version/md5 change for 3 wmp versions. those detections was made with the content of those updates, meaning that if yours have an non-public update in your systems, the detection set may not work. if is the case, please state that
[]s
# 07-13: ~mrt 3.21; +KB2555917; -KB2506223; +KB2507938; -KB2476687; -KB2121546; -KB955759 (replaced by KB2492386); preactions older than 2011 removed
i've forgot to mention in this log that yours may notice 15 modules under modules\Critical\__WMP_critical. as no one give the slight hint about how to solve the detection issue described above, instead have 5 modules, i've extracted the content of each update with that issue and did one module for each wmp version. that shall detect the proper version for each wmp and those modules will show only if the wmp that they target is present. sorry, but it's really impossible do an single module to look for the same file with only an version/md5 change for 3 wmp versions. those detections was made with the content of those updates, meaning that if yours have an non-public update in your systems, the detection set may not work. if is the case, please state that
[]s
click-click
14 Jul 2011
Downloaded with APUP and received verification error for XP. Ran AP after and WMP detection looks good. Three fixes need to be applied according to AP because I have not rebuilt my system yet, but everything looks promising.
BTW, does the dotNET addon replace the dotNET files in \modules\Components\__dotnet or is it only for V4?
Edited by click-click, 14 July 2011 - 06:14 PM.
BTW, does the dotNET addon replace the dotNET files in \modules\Components\__dotnet or is it only for V4?
Spoiler
Edited by click-click, 14 July 2011 - 06:14 PM.
Cristiano
14 Jul 2011
the script was fixed by adding the new files and removing a few that was obsolete. the download location didn't changed, so it shall works as an update for the old downloads. sorry, but i'm missing that part about v4. but ok, i've had an strong bad news today and i'm a little bit off
> rti_md5_enu.7z
probably an upload issue. i will check that
[]s
> rti_md5_enu.7z
probably an upload issue. i will check that
[]s
click-click
14 Jul 2011
> sorry, but i'm missing that part about v4.
Nevermind, I was confused.
I downloaded the NET Add-on and everything is clean. Good job.
Edited by click-click, 14 July 2011 - 11:02 PM.
Nevermind, I was confused.
I downloaded the NET Add-on and everything is clean. Good job.
Edited by click-click, 14 July 2011 - 11:02 PM.
Cristiano
14 Jul 2011
no problem. the issue about rti_md5_enu.7z shall be fixed tomorrow, no big deal at all, it's just an issue that happens sometimes
[]s
[]s
