[Cristiano]

from WU, today:
KB890830;
KB969898-> replaces KB960715;
KB961501;
KB968537 -> replaces 958690
KB970238;
KB969897-all IE versions -> replaces 963027

also, there's:
- 963093, that is an update for Windows Search 4.0. this update seems to be multilang. this one requires an system component to install
- 970483, that is for Internet Information Services (IIS) 5.1. i don't know if this one is multilang, because right now, only the enu download page is loading. this one isn't multilanguage
- KB970437, that is an update for Active Directory. it replaces KB949269

also i'm updating xp enu, ptb and ptg, this means something like 28 downloads, 28 modules to do, etc etc etc and i'm talking about xp only, because there's some updates for vista x64 and i'm holding this one too. i'm only one. each script will be updated, one by one, but due the amount of job that is required, i will be unable to finish it today. i will do xp first. i hope that every one be online in 2 days, tops. in meantime, if someone wishes add some advise about any of those or even some updates that aren't listed in here, be free to do it. just remember: autopatcher only works because of people that report issues/findings. so, autopatcher is you

thanks for your patience and understanding

[]s

edit: KB969898-> replaces KB960715;

[Cristiano]

script updated. more details in first post

[]s

[Munna]

thanks

[Cristiano]

oh well... i was rebuilding the wmp modules to better organize it and i've realized that KB945381 is now obsolete. in a quick search over internet, i've realized that some people say that KB959199 (ap doesn't have it) supersedes KB945381. that is true, in fact. but what those guys don't know that KB959199 is also obsolete. it was replaced by KB959772. doubts about? try install KB959199 or KB945381 after install KB959772. this is the log that yours will got:

[KB959199.log]
0.047: ================================================================================
0.047: 2009/06/29 21:51:09.343 (local)
0.047: d:\faafa47ae638703c2b4350\update\update.exe (version 6.3.13.0)
0.063: Hotfix started with following command line: 
0.063: In Function GetReleaseSet, line 1240, RegQueryValueEx failed with error 0x2
0.219:  C:\WINDOWS\system32\wmp.dll is Present
0.219: FileVersion of C:\WINDOWS\system32\wmp.dll is Greater or Equal To 11.0.5721.5145
0.219: Condition succeeded for section Test.Exist.WM11.Section.wmp in Line 1 of PreRequisite 
0.219: FileVersion of C:\WINDOWS\system32\wmp.dll is Greater Than 11.0.5721.5259
0.219: Condition Check for Line 2 of PreRequisite returned FALSE 
0.219: KB959199 Setup encountered an error:  This software update cannot complete because it is already included with the version of Windows Media Player 11 installed on your system.
0.234: This software update cannot complete because it is already included with the version of Windows Media Player 11 installed on your system.
11.484: Message displayed to the user: This software update cannot complete because it is already included with the version of Windows Media Player 11 installed on your system.
11.484: User Input: OK
11.484: Update.exe extended error code = 0xf0f4
11.484: Update.exe return code was masked to 0x643 for MSI custom action compliance.

so, this one will be removed soon. the remain wmp11 updates also will be checked for the same issue

edit1: kb929399 has to be replaced in some releases. some scripts has v1 and this one is now v2. new download link, for those that have some urge for that is this one

edit2: KB935957 is included at xp enu and i've realized in this post that this one is not needed anymore. this one also was superseeded by KB959772

[]s

[Cristiano]

checking the modules for xp enu, i've realized that KB949269 is still present. this one was replaced by KB970437. it will be set to be removed when the new organization for the modules be done. it will allows the user have an better control over the updates, by allowing him find quickly the updates for each wmp version (by instance, there's no need to install any wmp 10 update if you are going to install wmp 11). the same thing for ie6, 7 and 8 updates

[]s

[Cristiano]

great. another obsolete update found. KB941569 was replaced by windows xp sp3. doubts about? this shall be useful (it shall works in msie only)

[]s

[Cristiano]

missing update found: KB967715. this one replaces KB950582, that never aimed xp. according to this, windows xp was not affected by the issue covered by kb900582. but KB967715 aims xp. details about can be found in here

[]s

[Cristiano]

done. it toke me several days, but the re-organization of the modules is now complete (i hope). all the language-shared modules was re-written, to add other languages and allow the original idea about mix releases (no dupe files). but please keep in mind that some changes has to be done in other scripts too and due that, this problem can remain for some time. also, an complete search about obsolete modules was done and several modules that are no longer required due another update was removed. some mislabeled critical modules was re-done. the idea was mimic WU too. due that, you now can install all the WU-required updates by running autopatcher with some arguments (the updates that are required to WU was labeled as "Recommended=True". the status of "Recommended" for MSIE7 was removed, because WU offers IE8 instead. of course, the choice to install it or not remain yours, because this change will have some effect only when you run autopatcher with certain arguments. some may not like it, but Windows Search 4.0 is recommended by WU and, due that, "Recommended=True".

the main change that yours may notice is that now the WMP and IE now have his own section. the most noticeable change that yours will notice is at the non-critical updates (looks empty now, isn't?). by doing that change, yours will be able to quickly find those updates and select them or not, according to your wishes. of course, yours was able to do that before too, but now looks more easy to find it.

also, an long time mistake was fixed. i don't know why ms did it and why they keep doing this, but the detection for Windows Installer 4.5 had to be re-written. reason: the download link is the same for all, because there's not an localized version to this one. the md5 check for the update to this one works like a charm for any country, but inside the file, it's another story. according to your country, when you extract the content of this one (just run the update with an /x and choose an location for it), you will got another kb942288-v3.cat file, breaking our detection. yours wanna an example? in my country (Brazil), for this .cat file, we get AD7C4890876B9562BD526C9C83EB2E14 as md5. at Italy, yours will get B1EBF5A8518DDAF6E8844C56AA290B51 as md5. and, at US and UK, yours will got 3910C17A28E118D0AE5C8B6977C87C32 as md5. all this inside the same file, that has the exact same md5. God knows how many countries have the same issue with this one. because of this, the install detection to this one no longer will look for the md5 to the kb942288-v3.cat, just for the presence of it. it isn't the most reliable detection, but it works for all countries.

well, i hope that this is all. any ideas about the new organization are welcome

[]s

[gUiTaR_mIkE]

Minor script edit needed...

Download Error: L:\AP\XP.SP3\temp_bin\xp_sp3_enu.7z
File size does NOT match. Expecting 31045, but found 30707

It looks as if the rti 7z file size is wrong.

It looks as if the wrong rti has been uploaded. Extraction of the rti from windows_xp_sp3_enu_20090624 produces
a failed md5 for the rti, Unofficial status of the release, as well xp_sp3_enu.7z size error.

[Cristiano]

done. the right file was in our server, but the name for the file was wrong and it was downloading the old version. it shall be fixed now.

thanks

by the way: looks more organized now?

[]s

[Cristiano]

xp enu script script updated. details in the first post

[]s

[Cristiano]

from ms security bulletins, today:
973346. this one replaces KB969898 and KB950760

961371. this one replaces KB908519

971633. this one replaces KB961373

and, of course, malicious software removal tool.

[]s

[Cristiano]

script updated. more details in first post

[]s

[Cristiano]

one issue was found at MSXML3_enu.apm. by mistake, this module is asking for ModuleFolder=msxml4_sp3_files. also an quick fix, yours may just remove that line that the module will work, but the release will be tagged also unofficial. this issue will be fixed tonight

[]s

[gUiTaR_mIkE]

This is what I was trying to tell you in This Thread! back on June 28 and you said it was not an error.

I wasn't sure why you thought looking for MSXML 3 in a folder labeled "4_sp3_files" was correct. I have had difficulty trying to convey other
important details that get remarked as I don't understand and it is getting frustrating to say the least. We have essentially argued back and
forth at times, in other threads, but I finally shut up to avoid getting really angry or starting a fight.

This is all I said - short and to the point.

me said:

I wasn't sure if this was an error in the apm for XML 3 for XP SP3.

Re: MSXML3_enu.apm

[behavior]
ModuleFolder=msxml4_sp3_files

And the final response...

Quote

the unique id isn't related to the folder name.

And now it is a problem, this is getting old, very old.

[Cristiano]

easy. one step at a time. the unique id isn't related to the folder name, but ModuleFolder=msxml4_sp3_files is and that wasn't even supposed to be in there. i didn't saw that 4 in the module folder name, just that. i've just noticed that now by pure accident, because i wasn't even looking for that. you made your point, i see now that i was wrong, my mistake and i ask for your forgiveness about that issue. but to begin the story, set an ModuleFolder was supposed to be an exception, that was made an rule to avoid the very first rule: no double files. all that is being reviewed and ancient mistakes will be fixed, soon or later

[]s

[Cristiano]

done. fixed the mistake into MSXML3_enu.apm module. just an remind: there's implicit and explicit modules. they are implicit when ModuleFolder isn't included at [behavior] into the module or in any part of the module himself. due that, autopatcher will look for an folder that has the exact same name than the module, plus _files. given so, if you do an international module with all the proper descriptions included, you don't need anything else. but, if you avoid the first rule about "no dupe files", then you may have folders with the name of the module. but if you avoid that rule, then you may set an folder with any name, by choosing the function ModuleFolder under [behavior]. given so, your module can have any name, because you already had set the module folder. by doing that, if you have a dozen of translations, you will have a dozen of modules for it, when you could have just one. why do that? easy: to not talk about anything and do the module anyway. those issues will be fixed, soon or later, one at a time.

[]s

[Cristiano]

i don't believe in this... WU is wrong again!!!!

http://support.micro....com/kb/967715/

Quote

Note Updates 950582, 967715, and 953252 provide the same functionality for Autorun

and yet, even after you install the newer kb, that aims xp, KB967715 is delivered through automatic updates in a clean install of wxp forget it. i've forgot to add this one in the release that i've tested

plus, according to ms, KB941569 was replaced by windows xp sp3, also anyone can see in here, and yet, this one is delivered through automatic updates in a clean install of wxp.

those will be re-added by tomorrow, despite not be needed anymore according to ms himself, just to match WU

[]s

[Cristiano]

done. script updated to re-add the update that WU claims to be needed, despite MS documentation saying otherwise.

[]s

[Cristiano]

kb972260 (cumulative update for ie8) was released yesterday. due an DDoS attack at several DNS providers, i was unable to update the script last night. if possible, i will do it tonight

update: this one fits for all IE

[]s