Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I’ve always been curious about this. It seems that there must be more than simple file copy operations happening. I just reinstalled XP on my netbook (Atom proc, 1GBmem) and installing all the various updates took forever. This morning, I installed .net 4 and then it found 8 different updates to that. It has been installing those 8 updates for well over 15min now. If it were just replacing files or making registry tweaks, surely it wouldn’t take this long? Is it compiling stuff? What could be taking this long?

share|improve this question
up vote 2 down vote accepted

The short answer is that Component Based Servicing and Windows Side By Side (SxS) make updates take forever.

The issue is that there are a large number of interdependencies among Windows components and when one of them is updated, all of the things it depends on and all the things that depend on it have to have their assemblies rebuilt. Also, everything is checkpointed so that a failed update can be rolled back. That adds quite a bit of time as well.

This is in addition to the actual process of making sure the update applies to the system, unregistering the files that need to be patched, patching each individual file, and then re-registering the files.

share|improve this answer
Good info as usual Dave. Additionally, .NET upgrades also trigger a "background" (p)recompile that can last a good 10 minutes (sometimes, per-update!). See What is mscorsvw.exe and why is it eating up my CPU? for more info. – Ƭᴇcʜιᴇ007 Aug 5 '12 at 16:57

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.