Article ID: 281653 - Last Review: January 25, 2006 - Revision: 1.2

Setup Appears to Stop Responding at the Registering Components Screen During an Unattended Installation

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
This article was previously published under Q281653
Expand all | Collapse all

SYMPTOMS

In an unattended installation, if a large amount of files are being copied with the /copydir or /copysource switch, Setup may appear to stop responding, where the time to completion does not progress for an extended period of time.
Back to the top

CAUSE

This problem occurs because Setup checks each file for a signature, and logs an entry in the %SystemRoot%\Setupapi.log file if the file is not signed. In cases where the installation uses this feature to copy a large amount of files, impact of this operation may be significant.
Back to the top

RESOLUTION

To work around this problem, use the $oem$ folder structure to copy files during the installation.

For more information about $oem$ usage, read the Deploy.doc that is located on the Windows XP CD-ROM in the following location:
\Support\Tools\Deploy.cab
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Back to the top
APPLIES TO
  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Professional
Back to the top
Keywords: 
kbenv kbprb kbsetup KB281653
Back to the top