4 replies to this topic

[DALAMAR]

I get an error running apup. Heres the info:

Item=wmp11-windowsxp-x64-enu.exe

DetectFile=autopatcher:\modules\Components\wmp11_xp_2k3_x64_enu.apm_files\wmp11-windowsxp-x64-enu.exe
DetectHash=1269E4628CB3F8AB7B9CCA3915B464AD
DownloadFrom=http://download.microsoft.com/download/3/0/8/3080c52c-2517-43de-bdb4-b7eafd88f084/wmp11-windowsxp-x64-enu.exe
DownloadTo=autopatcher:\modules\Components\wmp11_xp_2k3_x64_enu.apm_files\wmp11-windowsxp-x64-enu.exe
ExpectedSize=27936568
ExpectedHash=1269E4628CB3F8AB7B9CCA3915B464AD

------------------------------------------------------------------------------------------------------------------------------------------------------------------

ACTUAL DATA
Size: 26.6 MB (27,926,896 bytes)
Size on disk: 26.6 MB (27,930,624 bytes)




it seems the ExpectedSize listed in the autopatcher_xp_2003_x64_enu.script file doesnt match the actual file size.

[James]

Hi DALAMAR,
Welcome to the forums!

Thanks for the report. I'm not sure what has gone wrong here, because the file on Microsoft's servers is 27,926,896 bytes as you say, but it also carries a last-modified date of Thu, 28 Feb 2008 19:19:39 GMT, so it has not changed recently.

Does the log-file show an incorrect MD5 hash for this file as well as an incorrect size for the file?

--

[DALAMAR]

***Starting Detection Routine Phase***

Detection error for file C:\Documents and Settings\*****\Desktop\apup\apup\modules\Components\wmp11_xp_2k3_x64_enu.apm_files\wmp11-windowsxp-x64-enu.exe
MD5 Hashes do NOT match. Expecting 1269E4628CB3F8AB7B9CCA3915B464AD, but found 8bc7f3cd5f20fd04a607360bbeda46cf!!!
Item wmp11-windowsxp-x64-enu.exe failed detection. Adding its download to the queue.
--Adding http://download.microsoft.com/download/3/0...p-x64-enu.exe--

***Downloading Releases***

Files to be Downloaded: 1

Download Error: C:\Documents and Settings\*****\Desktop\apup\apup\modules\Components\wmp11_xp_2k3_x64_enu.apm_files\wmp11-windowsxp-x64-enu.exe
File size does NOT match. Expecting 27936568, but found 27926896!!!


> Does the log-file show an incorrect MD5 hash for this file as well as an incorrect size for the file?

Apparently the MD5 doesnt match either.

Edited by DALAMAR, 02 November 2008 - 09:33 PM.

[Cristiano]

> Apparently the MD5 doesnt match either
of course not. take a look at File size does NOT match. if this not match, the most probable issue that you will have is MD5 doesn't match. i've manually downloaded this file and i've got this md5: 8bc7f3cd5f20fd04a607360bbeda46cf, that matches the md5 that you have. also, i have this size for the file: 27926896, that also matches with your file. so, the most probable reason for this is that this file was changed by ms. so, your download is right and the expected file for the script is wrong. so, this one has to be updated at the script, after checked by someone in another location too (ms has a lot of mirrors and sometimes they are out of sync)

don't worry. the file is safe to run, but the detection may be wrong because of that md5 file change

[]s

[James]

It seems that Microsoft have recently changed the download page for Windows Media Player 11 for Windows XP (64-bit) showing a new release date of "10/15/2008".

Apup's script needs updating, but in the meantime, as Cristiano says, it is safe to install the file that is actually being downloaded.

--