windows-kb890830-v3.17.exe failed verifica...
tite
11 May 2011
APUP Has Started
Version: 1.3
Operating System: English (1033) Windows XP Professional Service Pack 3
Current Locale: Portuguese - Brazil / Non-Unicode Default: Portuguese - Brazil
Starting APUP From: C:\Documents and Settings\Administrator\My Documents\Downloads\apup131\apup
Date & Time: 11-mai-2011 07:50 UTC Offset: -3
***Starting Detection Routine Phase***
Detection error for file C:\Documents and Settings\Administrator\My Documents\Downloads\apup131\apup\modules\Critical\KB890830_files\windows-kb890830-v3.17.exe
MD5 Hashes do NOT match. Expecting 971457F015D858FD83592EA9325E359D, but found 5343c1a8b203c162a3bf3870d9f50fd4!!!
Item KB890830 x86 Update failed detection or its parts. Adding whole download for this item to the queue.
--Adding http://download.micr...830-v3.17.exe--
***Downloading Releases***
Files to be Downloaded: 1
Download queue processed. Proceeding to next phase.
Download Error: C:\Documents and Settings\Administrator\My Documents\Downloads\apup131\apup\modules\Critical\KB890830_files\windows-kb890830-v3.17.exe
File size does NOT match. Expecting 12502472, but found 1245!!!
Edited by tite, 11 May 2011 - 11:24 AM.
Version: 1.3
Operating System: English (1033) Windows XP Professional Service Pack 3
Current Locale: Portuguese - Brazil / Non-Unicode Default: Portuguese - Brazil
Starting APUP From: C:\Documents and Settings\Administrator\My Documents\Downloads\apup131\apup
Date & Time: 11-mai-2011 07:50 UTC Offset: -3
***Starting Detection Routine Phase***
Detection error for file C:\Documents and Settings\Administrator\My Documents\Downloads\apup131\apup\modules\Critical\KB890830_files\windows-kb890830-v3.17.exe
MD5 Hashes do NOT match. Expecting 971457F015D858FD83592EA9325E359D, but found 5343c1a8b203c162a3bf3870d9f50fd4!!!
Item KB890830 x86 Update failed detection or its parts. Adding whole download for this item to the queue.
--Adding http://download.micr...830-v3.17.exe--
***Downloading Releases***
Files to be Downloaded: 1
Download queue processed. Proceeding to next phase.
Download Error: C:\Documents and Settings\Administrator\My Documents\Downloads\apup131\apup\modules\Critical\KB890830_files\windows-kb890830-v3.17.exe
File size does NOT match. Expecting 12502472, but found 1245!!!
Edited by tite, 11 May 2011 - 11:24 AM.
click-click
11 May 2011
Spoiler
This stuff is not being updated anymore. IMO I would not waste my time on APUP any longer. kb890830 is currently at version 3.19
Edited by gUiTaR_mIkE, 07 June 2011 - 10:06 AM.
Reason for edit:: Put log file in Spoiler.
giantslor
12 May 2011
click-click, on 11 May 2011 - 02:29 PM, said:
This stuff is not being updated anymore. IMO I would not waste my time on APUP any longer. kb890830 is currently at version 3.19
I had the same problem. How long has this project been dead -- since March 2010, the last time APUP was updated?
click-click
12 May 2011
I can't really say it's dead, but most updates stopped beginning in April. I believe Win 7 got updated in May, but many of those fixes have already been superseded.
RobinHood
17 May 2011
_def_x_
17 May 2011
@RobinHood, there is a problem with viewing pics as an attachment, this started after the latest forum update. I have asked to have it looked at but nothing to date.
The proper way to get help is to provide an unedited log which the OP did not do, all I know is the releases that have 890830(MRT) for x86 OSes as a common update have not been updated for 2 Patch Tuesdays - it is best to look at them as no longer maintained, this includes XP, Vista, and 7.
Bottom line, right now Win7SP1(x64) is the only OS being maintained and that can change by next Patch Tuesday - the project is phasing out.
The proper way to get help is to provide an unedited log which the OP did not do, all I know is the releases that have 890830(MRT) for x86 OSes as a common update have not been updated for 2 Patch Tuesdays - it is best to look at them as no longer maintained, this includes XP, Vista, and 7.
Bottom line, right now Win7SP1(x64) is the only OS being maintained and that can change by next Patch Tuesday - the project is phasing out.
Gratefuljim73
20 May 2011
This proble can be manually fixed.
1) Complete the full Windows XP patch download, the only file that should fail verification is the windows-kb890830-v3.17.exe file because it will not download from download.microsoft.com since it has been replaced with windows-kb890830-v3.19.exe.
1.5) Download the windows-kb890830-v3.19.exe from download.microsoft.com and place it in the modules\Critical\KB890830_files directory. This can be found at: My link
2)Edit the following file in NOTEPAD.exe ( the file contains extended ascii character sets for russion characters, so you must use notepad to open and edit/save the changes or you corrupt the file ):
modules\Critical\KB890830_x86_glb.apm
Do a global find/replace for 3.17 to 3.19
There should be 8 changes made, save the file using notepad.
3) Edit the md5_checksum_for_autopatcher_xp_enu.md5, line 36:
change
971457f015d858fd83592ea9325e359d *modules\Critical\KB890830_files\windows-kb890830-v3.17.exe
to
e088952a9cdb80504b846b973dc134a7 *modules\Critical\KB890830_files\windows-kb890830-v3.19.exe
Save the file.
Your done.
Do not try to use Apup to re-download Windows XP SP3 patches again, because you will overwrite the checksum file and the install script with the old data for version 3.17.
1) Complete the full Windows XP patch download, the only file that should fail verification is the windows-kb890830-v3.17.exe file because it will not download from download.microsoft.com since it has been replaced with windows-kb890830-v3.19.exe.
1.5) Download the windows-kb890830-v3.19.exe from download.microsoft.com and place it in the modules\Critical\KB890830_files directory. This can be found at: My link
2)Edit the following file in NOTEPAD.exe ( the file contains extended ascii character sets for russion characters, so you must use notepad to open and edit/save the changes or you corrupt the file ):
modules\Critical\KB890830_x86_glb.apm
Do a global find/replace for 3.17 to 3.19
There should be 8 changes made, save the file using notepad.
3) Edit the md5_checksum_for_autopatcher_xp_enu.md5, line 36:
change
971457f015d858fd83592ea9325e359d *modules\Critical\KB890830_files\windows-kb890830-v3.17.exe
to
e088952a9cdb80504b846b973dc134a7 *modules\Critical\KB890830_files\windows-kb890830-v3.19.exe
Save the file.
Your done.
Do not try to use Apup to re-download Windows XP SP3 patches again, because you will overwrite the checksum file and the install script with the old data for version 3.17.
_def_x_
21 May 2011
Nice post Gratefuljim73 
Since it looks like the x86 releases are without a release manager, if a user wants to update KB890830 they can do it by dropping the new file in the appropriate folder (don't forget to delete the old one) and making a few changes to the .apm file as you mentioned. If English is the only language you need then you can make the contents of the apm even easier to read (and edit).
Registry Detection you find after installation unless someone else gets the info to you. If there is a usable File Detection it can be used also, or both. This causes AutoPatcher to display the update in Blue (once installed) so it will be unchecked.
Installation is important, use the wrong file or the wrong commands and things get buggy. This update is easy to edit here, usually only small increments to the v3.xx value. Pay attention here.
Don't rename the folder or the apm file, only replace the file in the folder and edit the contents of the apm (not the Folder or UniqueID details).
Since the release will display Unofficial (not an issue if you created the release) you can get rid of the rti file, should load a bit faster. You may want to put your own name as ModuleAuthor.
Since it looks like the x86 releases are without a release manager, if a user wants to update KB890830 they can do it by dropping the new file in the appropriate folder (don't forget to delete the old one) and making a few changes to the .apm file as you mentioned. If English is the only language you need then you can make the contents of the apm even easier to read (and edit).
Spoiler
Not much to change with Title - the v3.xx value. If you want something other than an English Title and Description use matching languages...Title_1031=blahblahblah Description_1031=blahblahblahRelease Date is easy - yearmonthday - 20110510 - keep this up to date with the file's release date, good habit to have.
Registry Detection you find after installation unless someone else gets the info to you. If there is a usable File Detection it can be used also, or both. This causes AutoPatcher to display the update in Blue (once installed) so it will be unchecked.
Installation is important, use the wrong file or the wrong commands and things get buggy. This update is easy to edit here, usually only small increments to the v3.xx value. Pay attention here.
Don't rename the folder or the apm file, only replace the file in the folder and edit the contents of the apm (not the Folder or UniqueID details).
Since the release will display Unofficial (not an issue if you created the release) you can get rid of the rti file, should load a bit faster. You may want to put your own name as ModuleAuthor.
