Windows patch creates memory read problem

Hi.

I download Windows Updates using the following software:
http://www.heise.de/ct/projekte/offlineupdate/

The patches (files) look like this:
windowsxp-kb873376-x86-
enu_5c67061f5227844ef8b5f1eec8596bd2520c542d.exe

The additional 40 hex code is generated by the automated download
software. When executing a patch, I get the following message:

---- cut here ----
The instruction "0x10106018" referenced memory at "0x36643166". The
memory could not be "read". Click OK to terminate the program
---- cut here ----

When I delete the 40 character hex code from the filename, the patch
runs fine (in fact, deleting 20 characters is enough)!

The system is a WinXP SP2. The FS is NTFS (obvious). I can run the
patches from any path (even C:\), the error always appears. The
computer is a Dell XPS 700 (Core 2 Duo) with 2 GB ram. All harddisks
are RAID1 or RAID5.

Does anybody have any clue why this error shows up?

Thanks,

I dont read German, but is there a reason for not using
http://www.microsoft.com/downloads/d...displaylang=en

"geohei" <_> wrote in message
news: oups.com...
> Hi.
>
> I download Windows Updates using the following software:
> http://www.heise.de/ct/projekte/offlineupdate/
>
> The patches (files) look like this:
> windowsxp-kb873376-x86-
> enu_5c67061f5227844ef8b5f1eec8596bd2520c542d.exe
>
> The additional 40 hex code is generated by the automated download
> software. When executing a patch, I get the following message:
>
> ---- cut here ----
> The instruction "0x10106018" referenced memory at "0x36643166". The
> memory could not be "read". Click OK to terminate the program
> ---- cut here ----
>
> When I delete the 40 character hex code from the filename, the patch
> runs fine (in fact, deleting 20 characters is enough)!
>
> The system is a WinXP SP2. The FS is NTFS (obvious). I can run the
> patches from any path (even C:\), the error always appears. The
> computer is a Dell XPS 700 (Core 2 Duo) with 2 GB ram. All harddisks
> are RAID1 or RAID5.
>
> Does anybody have any clue why this error shows up?
>
> Thanks,
>