Why Do Automatic Updates ALWAYS Eat Up MUCH More HD Space Than Sta

[Scottbot]

Everytime it happens. This morning there was a security update ... said size
was about half a meg.

After the download 4 megs were eaten up.

After the install 40 more megs were used!

This drives me crazy. Feels like MS is trying to get one over on me every
time.

 

[R. McCarty]

There is nothing abnormal or unusual about this. A single Hotfix is going
to create a Uninstall entry in \Windows and also an entry in the $hf_mig$
folder. Plus the download will be saved in \SoftwareDistribution\Download.

No one is trying to get one over on you ( Whatever that means ), it's
simply the way it works.

 

[Scottbot]

Thanks you for the reply.

So you're saying there's nothing unusual about an update that's stated to be
under 1 meg actually causing 44 megs of space to be used on my HD?

And that's because of some registry entries and saving a copy of itself ?

 

[R. McCarty]

I haven't actually taken the time to count pre/post Hotfix disk space
consumption but what I described to you is how a Hotfix is applied
and the content it creates on the drive. One thing that may account
for the space consumption is a "Restore Point" which Windows will
create prior to applying a hotfix. Sorry I can't provide more exact info.

 

[Nepatsfan]

Everytime it happens. This morning there was a security update ... said size
was about half a meg.

After the download 4 megs were eaten up.

After the install 40 more megs were used!

This drives me crazy. Feels like MS is trying to get one over on me every
time.

I'd speculate that the majority of that 40MBs is the restore point that's
automatically created when the update is installed.

Nepatsfan

 

[Guest]

Everytime it happens. This morning there was a security update ... said
size
was about half a meg.

After the download 4 megs were eaten up.

After the install 40 more megs were used!

This drives me crazy. Feels like MS is trying to get one over on me every
time.

And why are there no fixes that actually reduce the space taken up by MS,
surely there must be oodles of redundant code in there that has been
superseded by the very numerous and increasing list of updates. Can these
not be edited out in some way?

S