Why do repairs fail?

[jp2msft]

Every so often I try to do a repair on VS2005 through the Add/Remove Programs
applet.

I try not to use anything else while it is repairing, so that the program
will be successful and will finish as soon as possible.

Whenever VS2005 is repairing itself, the processor stays below 10% usage and
takes 2 or 3 hours. Why can't it step up the processor to 90-100%?

Every time it finishes, it tells me the repair failed, and to view the log
file. Well, the log file is about 65 pages! What am I supposed to be looking
for?

For what it's worth, VS always works afterwards, but I keep thinking that
the initial failure is why I wind up having to go in and do a repair every
few months when the IDE starts doing strange stuff (losing my forms,
forgetting how to connect to active sync or unable to connect to it's own
device emulator).

 

[Ignacio Machin ( .NET/ C# MVP )]

Every so often I try to do a repair on VS2005 through the Add/Remove Programs
applet.

I try not to use anything else while it is repairing, so that the program
will be successful and will finish as soon as possible.

Whenever VS2005 is repairing itself, the processor stays below 10% usage and
takes 2 or 3 hours. Why can't it step up the processor to 90-100%?

Every time it finishes, it tells me the repair failed, and to view the log
file. Well, the log file is about 65 pages! What am I supposed to be looking
for?

For what it's worth, VS always works afterwards, but I keep thinking that
the initial failure is why I wind up having to go in and do a repair every
few months when the IDE starts doing strange stuff (losing my forms,
forgetting how to connect to active sync or unable to connect to it's own
device emulator).

Weird, I mean that you have had to repair it more than once, I do not
remember having to do it never
but in anycase, it's not weird that it takes that long and that the
processor is not that busy, most probably it's copying/moving files,
that does not occupy the processor at all