This issue was looked into a while ago and a Microsoft employee got involved in trying to shorten or eliminate the process, since this is a function of the Microsoft installation software.
Unfortunately, he concluded there wasn't any way around it. It seems to be a function of large numbers of files in the installation package.
|