Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

2

Possible verification error

Started by excalibur, Dec 16 2009 05:11 PM

You cannot reply to this topic
Go to first unread post

9 replies to this topic

#1 excalibur

Advanced Member

Members
50 posts

Gender:Male
Location:London

Posted 16 December 2009 - 05:11 PM

Last night I downloaded the latest updates.

I keep a previous version of the updates so that I can compare them with the latest versions.

When comparing some of the APMs seem to have some discrepancies which could lead to verification errors:

KB943729_x86.apm
PREVIOUS (Line 25-32)

   [DetectionRegistry]
   RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP20\KB943729
   KeyName=Type
   KeyValue=Update

   RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP20\KB943729
   KeyName=Type
   KeyValue=Update

LATEST (Line 25-36)

   [DetectionRegistry]
   RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP20\KB943729
   KeyName=Type
   KeyValue=Update

   RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB974266
   KeyName=Type
   KeyValue=Update

   RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows Server 2003\SP20\KB943729
   KeyName=Type
   KeyValue=Update

KB958655_xp_x86.apm
PREVIOUS (Line 28-45)

   [DetectionRegistry]
   RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB958655-v2
   KeyName=Type
   KeyValue=Update

   [DetectionFile]
   FilePath=system:\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
   FileName=KB958655-v2.cat
   FileVersion=ANY
   FileMD5=67F2947027F6F76C41CC1F0D8AA3AFBD

   FileName=KB967756.CAT
   FileVersion=ANY
   FileMD5=ANY

   [OperatingSystem]
   WindowsVersion=XP_SP2_X86,XP_SP3_X86
   SystemLanguage=ANY

LATEST (Line 28-45)

   [DetectionRegistry]
   RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB958655-v2
   KeyName=Type
   KeyValue=Update[/b][/i][/color]

   RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB972397-v2
   KeyName=Type
   KeyValue=Update

   [DetectionFile]
   FilePath=system:\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
   FileName=KB958655-v2.cat
   FileVersion=ANY
   FileMD5=67F2947027F6F76C41CC1F0D8AA3AFBD

   [OperatingSystem]
   WindowsVersion=XP_SP2_X86,XP_SP3_X86
   SystemLanguage=ANY

KB909520_xp_x86_enu.apm
LATEST (Line 22-35)

   [DetectionRegistry]
   RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP1\KB909520
   KeyName=Type
   KeyValue=Update

   RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP4\KB909520
   KeyName=Type
   KeyValue=Update

   [DetectionFile]
   FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
   FileName=basecsp.cat
   FileVersion=ANY
   FileMD5=bbbc61614fe770768647ec026fe1181c

PREVIOUS (Line 22-31)

   [DetectionRegistry]
   RegistryPath=HKLM\SOFTWARE\Microsoft\Updates\Windows XP\SP1\KB909520
   KeyName=Type
   KeyValue=Update

   [DetectionFile]
   FilePath=windows:\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}
   FileName=basecsp.cat
   FileVersion=ANY
   FileMD5=bbbc61614fe770768647ec026fe1181c

It seems that the latest modules are copies of existing ones, amended to fit the release, but the redundant fields have not been removed.

E

Edited by excalibur, 16 December 2009 - 05:12 PM.

Back to top

#2 Cristiano

Super Helpful Guy

Veterans
3,851 posts

Gender:Male
Location:Brazil (Santa Maria - RS)

Posted 16 December 2009 - 05:33 PM

no, the extra detections aren't related to old modules. those extra detections was taken from this topic, where an user that runs another update tool that has non-public fixes was reporting certain issues that can happen with users that has those non-public fixes. for them, the public fixes (that us to be older than the non-public) will never install and there's no need to show them as required, if is possible set extra detections for the non-public updates. those extra detections doesn't harm those that don't install the non-public updates, but helps those that have the non-public updates

[]s

Back to top

#3 excalibur

Advanced Member

Members
50 posts

Gender:Male
Location:London

Posted 16 December 2009 - 06:05 PM

OK.

This mean that Autopatcher can check for various detection entries.

I was not aware of this.

Thanks for the clarification.

Why does M$ not make it as difficult as possible to create utilities like AP/APUp? Posted Image

E

Edited by excalibur, 16 December 2009 - 06:07 PM.

Back to top

#4 Cristiano

Super Helpful Guy

Veterans
3,851 posts

Gender:Male
Location:Brazil (Santa Maria - RS)

Posted 16 December 2009 - 06:24 PM

> This mean that Autopatcher can check for various detection entries.
yep. the same is also valid for file checks, but an registry check must be present. OR checks for files are also possible, but that is more difficult to do than registry

> Why does M$ not make it as difficult as possible to create utilities like AP/APUp?
the part that makes me think a little bit more is that cease and desist issue that we had once. there's a dozen of tools autopatcher like around the web and the only one that got that thing was us. and i bet that if we forget about that and to the things like the other tools do since always, we will be sued and they don't

[]s

Back to top

#5 leeuniverse

Newbie

Members
7 posts

Posted 21 December 2009 - 04:38 AM

Okay, here's my log for my verification error.... I get it when it's at the end of downloading.
Sorry it's so long, but I had no way to tell where the error was.

Hope you can fix.... Need this ASAP, got to reinstall my system, and got to use it to find work.

Thanks much for your all's efforts....

Spoiler

Edited by Cristiano, 21 December 2009 - 10:17 AM.
spoiler

Back to top

#6 _def_x_

audi 5k

Veterans
1,460 posts

Gender:Male

Posted 21 December 2009 - 06:14 AM

@leeuniverse

First, wrap the log in "spoiler" code - it is much easier to view. Read the posting guidelines.

[ spoiler ] log file here [ /spoiler ] - you will need to bring the brackets in to create the "Show" and "Hide" tabs...

Spoiler

Secondly, you posted a log file with SIX selections, I'm not sure what was hard to understand when I recommended downloading only
ONE release at a time (AutoPatcher Updater and AutoPatcher Engine are fine to include) to determine what release(s) are giving you
problems. You are having troubles getting everything, if you have run APUP at least once you should have some of the files listed in
your log. I would recommend selecting only ONE release at a time for download - does APUP give off an error - check the log file and
post in the appropriate forum(s).

I believe these releases are Official and should download without error (at least at AutoPatcher's end) - XP SP3, DirectX, Extras, and Java.

I would try to download the above releases ONE at a time to be safe and make troubleshooting easier. If they finish, move on.

The Net Framework (DotNet) and the Office release may be unofficial or not finish, the DotNet because of Microsoft's server issue which is
out of the control of AutoPatcher, the Office release I'm not sure about.

Your release will show as Unofficial until ALL the releases you have downloaded to the SAME \modules folder are complete and signed, but
you wont know which is the culprit until you load the release in AutoPatcher - click the "About" tab - then the "Release Info" tab, and look to
see which release is marked in RED and labeled False under the Official header.