19 replies to this topic

[_def_x_]

It looks as if the XP SP3 English release is once again Official - Excellent work!

If you are still having problems with an Unofficial status I have provided an additional .sfv along with Cristiano's original .sfv, and a detailed
text file showing the contents of the release, for the moment these files will help trace the issue. If for some reason you run the .sfv and all files
check (549 of them) but you are still not Official this means you have extra files, in this case you need to create an .sfv of your release so we can
run it against ours and the Extra files should get flagged.

If the release should need updating in the near future these files will be for the most part void - it is to help you solve the Unofficial status Now!

Make sure you look at the notes in the .txt file - they may help a bit.

Here's a little nugget likely causing problems - an extracted .dll from an update that was in the update folder when the release was signed!

UNOFFICIAL: File 'L:\AP\XP.SP3\modules\Critical\KB974571_xp_x86_enu.apm_files\1\spmsg.dll' (mentioned by RTI 'I:\#AutoPatcher_Temp#\xp_sp3_enu.rti') does not exist!

Just in case you needed to see it to believe it XP SP3 English - is Official!

Anyway, use these tools if you see fit - or don't

[Cristiano]

> KB974571
yep. that module was made on hurry and i've forgot the extracted files that was required to take the detection. so, i had to remove that folder and sign again to solve that issue

by the way, i'm thinking about take that md5 after every update and add into the first post, as an checkup for those having issues. what yours think?

[]s

[_def_x_]

Cristiano said:

i'm thinking about take that md5 after every update and add into the first post, as an checkup for those having issues. what yours think?

I like the idea, and I will go one step further, I would create an .md5 along with each .rti and have the script extract it to the main directory
so all one will need to do is run it against their release should they have an Unofficial release that is supposed to be Official.

[Cristiano]

even better. i will add this file into this script later. right now, an lightning storm is coming and i will be forced to shutdown everything

[]s

[Softserve]

Hi,

I also have the "unofficial/unsupported" problem. I downloaded your attachment and checked it against my folders. It checks out OK but when I make a SFV of my folders I have 649 files. Can you perhaps check which files I have in addition to your listing. I have attached the SFV file. There is no rush so please do it whenever you have some spare time.

I have some questions:

If I ran AP and then do a check with Windows Upgrade (online) I get a list of high priority upgrades that I still need. ( list attached ). I did the check directly after running AP. Am I missing something?

If I run APUP directly after installing the updates with Autopatcher.exe some of the items are still ticked. Does this mean that it will redownload the ticked items (Autopatcher Updater, Autopatcher Engine and Autopatcher for Windows XP SP3(x86) )?

Thanks for all your efforts on behalf of us.

Attached Files

•  Files.zip   88.26K   9 downloads

[Cristiano]

my friend, you have an mix of old releases with outdated files in here and your list of "should not be in there" is kinda big. take a look:

Spoiler

modules\Components\journalviewer_enu_files\setup.exe
modules\Components\JournalViewer_x86_enu.apm
modules\Components\UserProfileHiveCleanup_enu.apm
modules\Components\WindowsUpdate_x86.apm
modules\Components\__msxml\MSXML4SP2_enu.apm_files\msxml4-KB954430-enu.exe
modules\Components\__msxml\MSXML4SP2_enu.apm
modules\Critical\KB890830_files\windows-kb890830-v2.4.exe
modules\Critical\KB890830_x86_204.apm
modules\Critical\KB936782_xp_wmp10_x86_enu.apm
modules\Critical\KB936782_xp_wmp10_x86_enu.apm_files\WindowsMedia10-KB936782-x86-ENU.exe
modules\Critical\KB936782_xp_wmp11_x86_enu.apm
modules\Critical\KB936782_xp_wmp11_x86_enu.apm_files\WindowsMedia11-KB936782-x86-ENU.exe
modules\Critical\KB938127_ie7_xp_x86_enu.apm
modules\Critical\KB938127_ie7_xp_x86_enu.apm_files\IE7-WindowsXP-KB938127-v2-x86-ENU.exe
modules\Critical\KB941569_xp_wmp_x86_enu.apm
modules\Critical\KB949269_xp_x86_enu.apm
modules\Critical\KB949269_xp_x86_enu.apm_files\WindowsXP-KB949269-x86-ENU.exe
modules\Critical\KB950582_xp_x86_enu.apm
modules\Critical\KB950582_xp_x86_enu.apm_files\WindowsXP-KB950582-x86-ENU.exe
modules\Critical\KB951072_xp_x86_enu.apm
modules\Critical\KB951072_xp_x86_enu.apm_files\windowsxp-kb951072-v2-x86-enu.exe
modules\Critical\KB951698_xp_x86_enu.apm
modules\Critical\KB951698_xp_x86_enu.apm_files\WindowsXP-KB951698-x86-ENU.exe
modules\Critical\KB954154_xp_wmp11_x86_enu.apm
modules\Critical\KB954154_xp_wmp11_x86_enu.apm_files\WindowsMedia11-KB954154-x86-ENU.exe
modules\Critical\KB954211_xp_x86_enu.apm
modules\Critical\KB954211_xp_x86_enu.apm_files\WindowsXP-KB954211-x86-ENU.exe
modules\Critical\KB954459_xp_sp3_x86_enu.apm
modules\Critical\KB954459_xp_sp3_x86_enu.apm_files\WindowsXP-KB954459-x86-ENU.exe
modules\Critical\KB955069_xp_x86_enu.apm
modules\Critical\KB955069_xp_x86_enu.apm_files\WindowsXP-KB955069-x86-ENU.exe
modules\Critical\KB956390_ie7_xp_x86_enu.apm
modules\Critical\KB956390_ie7_xp_x86_enu.apm_files\IE7-WindowsXP-KB956390-x86-ENU.exe
modules\Critical\KB956390_xp_x86_enu.apm
modules\Critical\KB956390_xp_x86_enu.apm_files\WindowsXP-KB956390-x86-ENU.exe
modules\Critical\KB956391_xp_x86_enu.apm
modules\Critical\KB956391_xp_x86_enu.apm_files\WindowsXP-KB956391-x86-ENU.exe
modules\Critical\KB956841_xp_x86_enu.apm
modules\Critical\KB956841_xp_x86_enu.apm_files\WindowsXP-KB956841-x86-ENU.exe
modules\Critical\KB957095_xp_x86_enu.apm
modules\Critical\KB957095_xp_x86_enu.apm_files\WindowsXP-KB957095-x86-ENU.exe
modules\Critical\RootCert_enu.apm
modules\NonCritical\euFontUpdate_enu.apm
modules\NonCritical\euFontUpdate_enu.apm_files\EUupdate.EXE
modules\NonCritical\euFontUpdate_enu.apm_files\inst.apf
modules\NonCritical\KB892313_xp_wmp10_x86.apm
modules\NonCritical\KB892313_xp_wmp10_x86.apm_files\windowsmedia10-kb892313-x86-intl.exe
modules\NonCritical\KB895181_wmp_enu.apm_files\windowsmedia-kb895181-x86-enu.exe
modules\NonCritical\KB895181_xp_wmp10_x86_enu.apm
modules\NonCritical\KB902344_xp_wmp10_x86.apm
modules\NonCritical\KB902344_xp_wmp10_x86.apm_files\windowsmedia10-kb902344-x86-intl.exe
modules\NonCritical\KB921108_xp_wmp10_x86.apm
modules\NonCritical\KB921108_xp_wmp10_x86.apm_files\windowsmedia10-kb921108-x86-intl.exe
modules\NonCritical\KB922814_xp_wmp10_x86.apm
modules\NonCritical\KB922814_xp_wmp10_x86.apm_files\windowsmedia10-kb922814-x86-intl.exe
modules\NonCritical\KB928788_xp_wmp11_x86.apm
modules\NonCritical\KB928788_xp_wmp11_x86.apm_files\windowsmedia11-kb928788-x86-intl.exe
modules\NonCritical\KB929399_xp_wmp11_x86.apm
modules\NonCritical\KB929399_xp_wmp11_x86.apm_files\windowsmedia11-kb929399-v2-x86-intl.exe
modules\NonCritical\KB929773_xp_wmp11_x86.apm
modules\NonCritical\KB929773_xp_wmp11_x86.apm_files\windowsmedia11-kb929773-x86-intl.exe
modules\NonCritical\KB932390_xp_wmp11_x86.apm
modules\NonCritical\KB932390_xp_wmp11_x86.apm_files\windowsmedia11-kb932390-x86-intl.exe
modules\NonCritical\KB933547_xp_wmp11_x86.apm
modules\NonCritical\KB933547_xp_wmp11_x86.apm_files\windowsmedia11-kb933547-x86-intl.exe
modules\NonCritical\KB935551_xp_wmp11_x86.apm
modules\NonCritical\KB935551_xp_wmp11_x86.apm_files\windowsmedia11-kb935551-x86-intl.exe
modules\NonCritical\KB935552_xp_wmp11_x86.apm
modules\NonCritical\KB935552_xp_wmp11_x86.apm_files\windowsmedia11-kb935552-x86-intl.exe
modules\NonCritical\KB935957_xp_wmp11_x86.apm
modules\NonCritical\KB935957_xp_wmp11_x86.apm_files\windowsmedia11-kb935957-x86-intl.exe
modules\NonCritical\KB939209_xp_wmp11_x86.apm
modules\NonCritical\KB939209_xp_wmp11_x86.apm_files\windowsmedia11-kb939209-x86-intl.exe
modules\NonCritical\KB939683_xp_wmp11_x86_enu.apm
modules\NonCritical\KB939683_xp_wmp11_x86_enu.apm_files\WindowsMedia11-KB939683-x86-ENU.exe
modules\NonCritical\KB944110_xp_wmp10_x86.apm
modules\NonCritical\KB944110_xp_wmp10_x86.apm_files\windowsmedia10-kb944110-x86-intl.exe
modules\NonCritical\KB944882_xp_wmp11_x86.apm
modules\NonCritical\KB944882_xp_wmp11_x86.apm_files\windowsmedia11-kb944882-x86-intl.exe
modules\NonCritical\KB945381_xp_wmp11_x86.apm
modules\NonCritical\KB945381_xp_wmp11_x86.apm_files\windowsmedia11-kb945381-x86-intl.exe
modules\NonCritical\KB946665_xp_wmp11_x86.apm
modules\NonCritical\KB946665_xp_wmp11_x86.apm_files\windowsmedia11-kb946665-x86-intl.exe
modules\NonCritical\KB949056_xp_wmp10_x86.apm
modules\NonCritical\KB949056_xp_wmp10_x86.apm_files\windowsmedia10-kb949056-x86-intl.exe
modules\NonCritical\KB950478_xp_wmp11_x86.apm
modules\NonCritical\KB950478_xp_wmp11_x86.apm_files\windowsmedia11-kb950478-x86-intl.exe
modules\NonCritical\KB954708_xp_x86_enu.apm
xp_sp3_enu.rti

of course, certain files are just outdated, like xp_sp3_enu.rti. as for the other scripts, you still have ancient versions of some releases, like this one:
modules\Components\directx.apm
modules\Components\directx_files\directx_nov2008_redist.exe

i don't have the .net package in here to be sure, but seems that you are missing files in that package too. so please, remove those "should not be there" files and folders (you must remove also the folder for things like those:
modules\NonCritical\KB950478_xp_wmp11_x86.apm_files\windowsmedia11-kb950478-x86-intl.exe ) and then run apup again and let checked the first 2 items in the list, plus: .net addon; direct x addon and xp enu script. after that, autopatcher shall run also official. if not, please take that same check again after run apup and check those releases

> Am I missing something?
well, that us to happen when:
1 - you still have sp2;
2 - when you choose the wrong options in autopatcher

to fully match WU, you shall check all critical, non critical, all the .nets, some of the msxml and some of the addons, install, reboot and check for the missing ones again. if i'm not mistaken, i've already adapted the xp enu script to fully match WU by running autopatcher with an /recommended option, but i didn't fully checked that

> Does this mean that it will redownload the ticked items (Autopatcher Updater, Autopatcher Engine and Autopatcher for Windows XP SP3(x86) )?
yes and no. apup has an detection for the updates that you already have in apup folder, so, those will not be downloaded again, unless something in the detection doesn't math. in this case, apup will download those again and will attempt to remove the obsolete modules. so, when you have an up-to-date folder with apup, you only will need download the missing ones and this will be an small amount of the total

[]s

[_def_x_]

@Softserve

Cristiano pretty much summed up your issue but if I can I will add a few things that might help.

Important: I wouldn't bother updating with your existing AutoPatcher release, there are so many outdated files you dont want to be
installing superseded patches - let's get your release Official.

First, if you notice in the image I have in post #1 it shows only XP SP3 (AutoPatcher Engine should always be present), so if you have
additional releases in the same \modules folder of course the file count will not match. The .md5 files we are posting is for that
particular release only - it would be a pain to configure every possible combination of releases and provide an .md5 for the package.

If you feel up to it you could go through your release and remove a few files and folders incrementally (see Cristiano's spoiler list) don't
forget the text file I supplied, it also has the list of needed files for XP SP3 English, anything else can be removed. You also have the
option of downloading a new release - just remember to update it regularly and I would avoid more than 1(one) OS per folder. It isn't a
problem having the NET Framework in the same folder as XP SP3. In fact, if you want more than just XP you should say so and we can
advise on how best to download the releases.

The issue with updates being selected again after you attempted to install them can be a detection issue, but since the release is unofficial
and the patch may be outdated and long since replaced, lets get the release Official and if the detection issues are still present you should
post a list (starting a new topic would be best).

You shouldn't have to download files again and again but updates get replaced, folders get rearranged, new .apm files are needed at least once
a month (remember Patch Tuesday) so you can expect to run apup.exe a few times every month - but it is more to update and clean house not
to download the same files over and over.

According to the files mentioned in the pdf document all but one update is available in either the latest XP SP3 package or the NET Framework
Addon Pack. The only update I'm not finding is KB961118 - everything else seems to be available. Beware, the NET Framework package is large
due mostly to 3.5 - more than 230MB alone.

So, which is it - start fresh (the easiest way to get Official) or do some serious housecleaning?

[_def_x_]

@Softserve

I looked closer at your supplied .sfv file and I can see you have the NET Framework and DirectX (even though it's old) Addons along with
XP SP3 so I would say unless you have a highspeed connection I wouldn't download everything again rather try to clean the mess up but,
it will take some coordination and we will have to be on the same page. Again, it is your decision and we sure hope you stay on top of
things in the future, the removal commands stay in the scripts for awhile but not forever - the script would get too large.

[Softserve]

gUiTaR_mIkE, on 26 October 2009 - 05:39 PM, said:

@Softserve

I looked closer at your supplied .sfv file and I can see you have the NET Framework and DirectX (even though it's old) Addons along with
XP SP3 so I would say unless you have a highspeed connection I wouldn't download everything again rather try to clean the mess up but,
it will take some coordination and we will have to be on the same page. Again, it is your decision and we sure hope you stay on top of
things in the future, the removal commands stay in the scripts for awhile but not forever - the script would get too large.

Hi, I deleted all the files as per the spoil list and a couple more and then had the same number of files as per your SFV. I then ran APUP again and it downloaded one extra file nl. "Mswinsck.ocx". I then ran Autopatcher.exe and it now reports "Official". Thanks a lot for the help.

By the way, which .NET addons do I really need? It is a bit confusing why the older versions are still in the download lists?

[_def_x_]

@Softserve

Glad to hear you got things sorted out - I hope you are sure, we don't mind helping. I say this because I know you needed to update
DirectX to August 2009 (from November 2008) and you didn't mention this. BTW, you can't have only 550 files, like I said you also had
the NET Framework Addon Pack and an old version of DirectX. We can be sure you have everything updated by looking at the Release
Info, the screenshot in my first post is just that - fire up AutoPatcher - when it loads the releases click About - click Release Info, and
if you could post a screenshot so we can have a look. I don't mean to question you but I did run your .sfv against my NET Framework
folder and the files checked so you would have had to delete a bunch of files from the NET Framework release as well the old DirectX
to match the .md5 I supplied - if you did that's fine - I'm just pointing this out.

If you are asking about which NET Framework you need now, I would say if you have 3.5 installed that should be good for most applications
that require the NET Framework, the older versions are there only because every now and again an application will require it. You can verify
what version(s) of the NET Framework you have installed 2 ways -

You can check the \Windows\Microsoft.NET\Framework\ folder and look for the subfolders - as an example mine shows - 1.0.xxxx, 1.1.xxxx,
2.0.xxxxx, 3.0 - yours will likely be different.

Also, you can check by running autopatcher.exe - this will prompt AutoPatcher to create a log file and it will offer some important information
regarding what NET Framework is installed. FYI, running autopatcher.exe /verbose will create a very detailed log which is very handy. The log
file can be found in the \Windows directory - autopatcher.log. When you determine what versions you have installed I would apply any updates
available using AutoPatcher. If by chance you should need to install 3.5 I would read up, it's a big install and I wouldn't try installing anything
with it, when it finishes, verify all went well and then apply the necessary patches - they are in the NET Framework Addon Pack.

[_def_x_]

gUiTaR_mIkE said:

The only update I'm not finding is KB961118

I must be blind, this one is in the NET Framework Addon Pack also!

I thought I would mention this handy tool that will display the NET Framework version(s) installed. The program is a small stand alone
executable you can run from anywhere - I like to run it from the main root drive - C:\ - Beware, the tabs on the left are for downloading
so don't click them unless you want to download either the SDK or the Framework.

....NET Version Detector

[Softserve]

Hi, I decided to download the full package (see logs for details about the selections) in order to have a complete update pack I can use to deploy to other PC's. However the download failed twice. I have attached the screenshots and logs for your info. Looks like the JAVA download is causing problems. The first session download was about 120MB and the second 469MB. I have attached a SFV as well. I started from an "Official Release" state.

Can you please advise how to proceed without having to download everything again? I don't know whether this should have been a new topic, if so please forgive me.

[Softserve]

Softserve, on 28 October 2009 - 08:44 AM, said:

Hi, I decided to download the full package (see logs for details about the selections) in order to have a complete update pack I can use to deploy to other PC's. However the download failed twice. I have attached the screenshots and logs for your info. Looks like the JAVA download is causing problems. The first session download was about 120MB and the second 469MB. I have attached a SFV as well. I started from an "Official Release" state.

Can you please advise how to proceed without having to download everything again? I don't know whether this should have been a new topic, if so please forgive me.

Sorry, here are the attachments.

Attached Files

•  Logs & SFV.zip   63.29K   4 downloads

[Cristiano]

> Looks like the JAVA download is causing problems. The first session download was about 120MB and the second 469MB
not only java:
NDP20SP2-KB974417-x86.exe: 200 Connection is aborted due to timeout or other failure
NDP35SP1-KB963707-x86.exe: Valid name, no data record of requested type
WindowsXP-KB961118-x86-ENU.exe: Valid name, no data record of requested type
NDP35SP1-KB958484-x86.exe: Valid name, no data record of requested type
NDP30SP2-KB958483-x86.exe: Valid name, no data record of requested type
NDP20SP2-KB958481-x86.exe: Valid name, no data record of requested type
directx_aug2009_redist.exe: Valid name, no data record of requested type

this us to be related with certain viruses

and this:
&filename=jre-6u16-windows-i586-s.exe: 504 HTTP/1.0 504 Gateway Time-out
&filename=jre-6u16-windows-i586-s.exe: 504 HTTP/1.0 504 Gateway Time-out
well, download ics or certain viruses. i didn't an full download of the java module, but the link is alive. do you mind if i as you to check for viruses into your machine? this us to be easy to test, by trying reach any anti-virus website, like kaspersky, symantec, mcafee, panda, etc

i don't have in here some of the packages that you have selected to download, sorry. so, i can't check the sfv file from here

[]s

Edited by Cristiano, 28 October 2009 - 10:34 AM.

[_def_x_]

Cristiano said:

this us to be related with certain viruses

I would see our Online Scanners! page (the links will take you to the respective page) and use as many or all to verify you have no viruses!

[Softserve]

Softserve, on 28 October 2009 - 08:53 AM, said:

Sorry, here are the attachments.

I managed to get the release "Official" again. I downloaded the Java release from sun.com and copied it over the file APUP downloaded (0 bytes). Autopatcher now shows "Official Release" as it should. I don't know why the Java download failed ?

I have attached the latest SFV for your info.

Thanks

Attached Files

•  Autopatcher sfv 28-10-09.zip   10.53K   5 downloads

[Cristiano]

> I don't know why the Java download failed ?
that may happen sometimes, due slowdowns, etc. but i will do an download test for this one at night, just to be sure

[]s

[_def_x_]

@Softserve

Glad you got it worked out.

You may want to either hit the Finish tab when APUP is finished (before creating a check file) or find out why the \temp_bin folder is staying
around after you close APUP, I have seen this twice now from your .sfv files -> temp_bin\___windows_extras.7z 775D2E84. The \temp_bin
folder is created when apup.exe is run (this is for the .7z, .zip, and .script files to reside temporarily) and should be deleted when apup.exe
is closed or exited.

If Windows Explorer is open when you run APUP it is good practice to either refresh, close, or both (Windows Explorer) so the window will be updated
properly.

[_def_x_]

***I just wanted to mention that I removed the attached .md5 for XP SP3 English in post #1 - it will now download using APUP,
you will find an up-to-date .md5 file in the main directory (along with apup.exe and autopatcher.exe).

[Softserve]

gUiTaR_mIkE, on 28 October 2009 - 02:06 PM, said:

@Softserve

Glad you got it worked out.

You may want to either hit the Finish tab when APUP is finished (before creating a check file) or find out why the \temp_bin folder is staying
around after you close APUP, I have seen this twice now from your .sfv files -> temp_bin\___windows_extras.7z 775D2E84. The \temp_bin
folder is created when apup.exe is run (this is for the .7z, .zip, and .script files to reside temporarily) and should be deleted when apup.exe
is closed or exited.

If Windows Explorer is open when you run APUP it is good practice to either refresh, close, or both (Windows Explorer) so the window will be updated
properly.

If I remember correctly APUP terminated by itself after I closed the error message. Maybe that's why the temp files remained. I will heed your advice though, thanks.