"Unknown archive file size" if I try to install/update a "full" MiKTeX distribution

Hello,

First, I prefer to install MiKTeX complete and additional
install the "optional" packeges, which are not included in
the complete install. btw: why? This is confusing to me.
Because a _complete_ install should be complete not "half-"
complete, shouldn't it? ;)

Anyway. After Refresh FNDB and Formats as admin and as user
settings I usually install the "optional/additional" packages
within the settings (as Admin) dialog box by selecting the
unmarked checkboxes. In these days the package "latex-reference"
is not installed after an update, but if I do this I get
an errror which tells me:

"Unknown archive file size"

in a Toolbox. The [Copy Info] Button shows me:

---snip---
MiKTeX Problem Report
Message: Unknown archive file size.
Data: latex-referenz
Source: libraries\miktex\packagemanager\internal.h
Line: 909
MiKTeX: 2.9
OS: Microsoft Windows 7 Business Edition, 64-bit Service Pack 1 (build 7601)
Invokers: explorer
SystemAdmin: yes
PowerUser: yes
Root0: C:\Users\%USERNAME%\AppData\Roaming\MiKTeX\2.9
Root1: C:\Users\%USERNAME%\AppData\Local\MiKTeX\2.9
Root2: C:\ProgramData\MiKTeX\2.9
Root3: C:\Program Files (x86)\MiKTeX 2.9
UserInstall: C:\Users\%USERNAME%\AppData\Roaming\MiKTeX\2.9
UserConfig: C:\Users\%USERNAME%\AppData\Roaming\MiKTeX\2.9
UserData: C:\Users\%USERNAME%\AppData\Local\MiKTeX\2.9
CommonInstall: C:\Program Files (x86)\MiKTeX 2.9
CommonConfig: C:\ProgramData\MiKTeX\2.9
CommonData: C:\ProgramData\MiKTeX\2.9
---snap---

btw: %USERNAME% is an administrator (Win7 SP1) account.

In this case the archive file size of "latex-referenz"
seems to be unknown, but I don't know how can I fix it?

Usually one or a few updates later the error is gone, but this
happens so often... Why? And why is it so difficult to avoid
such errors and transmit the right size while synchronizing
the package database.

Another idea:
Calculate the size of a package by the mo*.exe itself!

This behavior of MiKTeX is sometimes very nerving to me and I
really would appreciate if that behavior would be fixed...

But until this is not fixed, how can I fix such errors by myself?

T.




------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk