Jump to content


Verification Failed


55 replies to this topic

#1 Aldebaran

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 23 June 2010 - 02:23 PM

Hi

I get a verification failed message (see attachment).
The end of the log file shows:

***Downloading Releases***

Files to be Downloaded: 1
Download queue processed. Proceeding to next phase.

Download Error: C:\apup\modules\Components\WMP11_xp_x86_enu.apm_files\wmp11-windowsxp-x86-enu.exe
File size does NOT match. Expecting 25740144, but found 25740256!!!

***Processing Cleanup Routines***

Any thoughts how to prevent this error or how to fix it?

Many thanks in advance.

Attached Files



#2 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 23 June 2010 - 02:47 PM

ok, i will check that tonight. sorry about my late, but in the past 2 days i did an learning travel

[]s

#3 Aldebaran

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 23 June 2010 - 02:55 PM

Would be great....I like Autopatcher very much as it enables me to spread the patches via P2P to my desktops.

I know CD's, USB and DVD are more common when using Autopatcher. I use a product named DistriBrute that uses a real P2P protocol.
This way I can avoid extra WSUS servers at branche offices. Looking forward to a fix.

#4 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 23 June 2010 - 04:32 PM

great. ms has in deed changed this file. the md5 for this one doesn't match either. the new release date is 6/22/2010, as can be seen in here. the download location seems to be the same, but the .cat file that works as detection doesn't match. so, i guess that something else has changed too. i will update the enu script tonight to fix this download issue and the detection issue as well, but my vms are still down (i'm having an sound card issue in my new computer and also an windows installer issue. if an fix for booth isn't possible, then i will wipe and do again. so, no reason to deploy the vms yet) and due that, if they have changed the install strings too, i may not see that right now.

again, thanks for your report

[]s

#5 Aldebaran

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 23 June 2010 - 04:58 PM

maybe a dumb question (i'm a relatively new Autopatch user) but are you releaseing a new version or just a single file to patch the current version?

#6 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 23 June 2010 - 04:59 PM

just a single file to patch the current version. there's no need to download the whole thing again

[]s

#7 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 23 June 2010 - 10:44 PM

done. this issue shall be fixed now. if the script find the new version of wmp11, then only the new module, rti file and md5 checksum will be downloaded. if not, then all those files will be downloaded, plus wmp11

thanks again

[]s

#8 Aldebaran

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 24 June 2010 - 05:40 AM

Thanks for the great support!

#9 click-click

    I am not young enough to know everything.

  • Release Managers
  • PipPipPipPip
  • 484 posts
  • Gender:Male

Posted 16 July 2010 - 12:25 PM

View PostCristiano, on 23 June 2010 - 10:44 PM, said:

done. this issue shall be fixed now. if the script find the new version of wmp11, then only the new module, rti file and md5 checksum will be downloaded. if not, then all those files will be downloaded, plus wmp11

thanks again

[]s

If I'm not mistaken, the new Windows Media Player 11.0.5721.5262 replaces the following:

KBs in NonCritical:

KB939683_XP_WMP11_X86*
KB928788_XP_WMP11_X86*
KB929773_XP_WMP11_X86*
KB933547_XP_WMP11_X86*
KB932390_XP_WMP11_X86*
KB929399_XP_WMP11_X86*
KB935551_XP_WMP11_X86*
KB935552_XP_WMP11_X86*
KB939209_XP_WMP11_X86*
KB944882_XP_WMP11_X86*

KBs in Critical

KB941569_XP_WMP_x86_ENU*
KB954154_XP_WMP11_x86_ENU*

These are no longer showing blue after I updated with the following

Windows Media Player 11 (11.0.5721.5262)
added KB954155 - wmspdmod.dll/11.0.5721.5263 MS09-051
added KB973442 - wmvdecod.dll/11.0.5721.5268 hotfix
added KB974905 - wmnetmgr.dll/11.0.5721.5269 hotfix
added KB978695 - wmvcore.dll/11.0.5721.5275 MS10-033
added KB973540 - wmp.dll wmpdxm.dll/11.0.5721.5268 MS09-37
added KB943604 - Npdsplay.dll/3.0.2.629 Dxmasf.dll/6.4.9.1133 Npdrmv2.dll Npwmsdrm.dll/9.0.0.4504 hotfix

Edited by click-click, 16 July 2010 - 01:19 PM.


#10 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 16 July 2010 - 08:26 PM

thanks. i've forgot about this one. but oh well, i didn't found more infos about this update too

i will set an removal for those later. now, i'm in deep freeze brrrrrrrrrr

[]s

#11 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 20 July 2010 - 01:07 AM

once again, you are right, my friend, after several checks, seems that all those kbs was in deed replaced by 11.0.5721.5262. issue: the wmp11 has now an glitch in the detection, because it is looking for the cat file, that was left untouched. the detection can be replaced by file version (in this case, the wmp11 executable himself), but what if an update replaces this one too? i'm trying to figure an more reliable detection, but so far, no luck. i'm with an idea about set an minimum version for wmp file version, that shall fix the issue, but before do that, i will do a few more tests, because the operator > us to have an problem with certain files. until that, there's no reason to no one download obsolete files, so an removal was set for all those

thanks again

[]s

#12 JRosenfeld

    Advanced Member

  • Members
  • PipPipPip
  • 107 posts

Posted 21 July 2010 - 10:05 PM

The version of WMP 11 that I have on my XPpro SP3 is 11.0.5721.5268.
That's starting with whatever version was available in April 2008, with the updates shown in blue in the two pics. (I haven't bothered with the other recommended updates as I don't need them). I guess that must be due to the third critical update KB 973540?




Edited by JRosenfeld, 21 July 2010 - 10:31 PM.


#13 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 22 July 2010 - 12:52 AM

the version 11.0.5721.5262 of wmp was released in 6/22/2010 and it included several updates (if not all) wmp11 updates. the ones that has become obsolete was already removed from the script, giving this changelog: -KB939683; -KB928788; -KB929773; -KB933547; -KB932390; -KB929399; -KB935551; -KB935552; -KB939209; -KB944882; -KB941569; -KB954154

kb973540 was one of those

[]s

#14 JRosenfeld

    Advanced Member

  • Members
  • PipPipPip
  • 107 posts

Posted 23 July 2010 - 09:32 PM

Just ran apup again (Windows XP). I noticed that under Microsoft Windows recommended updates there is now an entry

'WMP - recommended updates'. But looking in the module folder I see these are all for WMP 10. Users who have WMP 11 might try to install these in error.

I suggest that to avoid confusion the item is labelled WMP 10 - recommended updates.

#15 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 23 July 2010 - 11:42 PM

yep, but what about if ms releases another update for wmp11?

[]s

#16 JRosenfeld

    Advanced Member

  • Members
  • PipPipPip
  • 107 posts

Posted 24 July 2010 - 01:48 AM

In Autopatcher the 'WMP - recomended updates' line does not expand (it has just a single checkbox, no + sign next to it). I assumed that meant that if one checked it it would install all the updates listed in the correspondng modules folders (NonCritical\__WMP_noncritical\...). Is that is by design or maybe, since I have WMP 11, and at the moment there are only WMP 10 updates, that is why the entry does not expand on my system??

If by design, then I suggest WMP 11 updates be stored separately from those of WNP 10, so one would see two entries: 'WMP 10 - recommended updates' and 'WMP 11 - recommended updates'. If it is because Autopatcher knows that I have WMP 11, then it should not show that entry if there are only WMP 10 updates?

Or, if it was intended that the Autopatcher entry could be expanded to show the individual updates, that would need fixing :-)

#17 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 24 July 2010 - 11:18 AM

if i'm not mistaken, there's not an update for wmp at the recomended updates anymore. due that, the parent module can't expand. to that, only one solution: the removal of the module. i will check if there's something else in there to see if something can be done.

oh yes, if i'm not mistaken, flash player had an update. i will check that too, but an fix shall arrive only tomorrow. today, with rain or not, i need take the road...

[]s

#18 gondwana

    Member

  • Members
  • PipPip
  • 13 posts

Posted 24 July 2010 - 03:30 PM

Hi Cristiano,

I have run into a related error, autopatcher went "unofficial", file download not verified, xp3_enu = false. i got a log :
Spoiler

hope this helps and many thanks for all the work you put into autopatcher

#19 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 25 July 2010 - 11:41 AM

well, the links are alive, so it must be an issue in the download. also, seems weird that you don't have the wmp10 updates, but have everything else. have you tried the .md5 file that is in autopatcher root? it may help. also, if you can, please take an recursive md5, starting from G:\My Documents\Operating Sys\WinXP\Autopatcher

also, if this G is an remote folder, you have to move it to an local patch, because there's a lot of issues related to remote folders

thanks

[]s

#20 gondwana

    Member

  • Members
  • PipPip
  • 13 posts

Posted 25 July 2010 - 11:19 PM

I have run apup several times with the same result, each time it downloads the same wmp10 files KB 949056, 944110, 922814, 902344, 895181, 892313. None of these are new files, I have them already. The MD5 for each file is correct.

I updated on 16 June all was well, updated on 13 July is when things went wrong.
I have attached a new MD5 file for my autopatcher folder, I hope this is what you ment
Spoiler


The G: is not remote, it is my second internal hard drive on this machine,

Thanks





2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users