A+: Verifying Installation
At the end of the installation process, you should test the system by running Windows Explorer, running built-in programs such as Paint and WordPad, and connecting to the Internet. Make sure you don’t see popup error messages or errors within the Event Viewer. If the installation process doesn’t complete properly, you should check the log files to determine the problem.
Let’s talk about Windows XP log files first. In Windows XP, most of these files are plain text, and are stored in the %systemroot% folder of the operating system. The %systemroot% folder is a variable that indicates the folder where the operating system was installed. In most cases this will be C:\Windows unless otherwise specified below.
Setuperr.log records errors (if any) in installation; check first if installs fail. A zero-byte file shows no install errors.
Setuplog.txt stores text-mode install errirs.
Setupact.log stores errors during GUI-mode. Copy it as soon as Windows is installed, as subsequent hotfixes and updates append to the file, but there are no internal date and time stamps for those changes.
Setupapi.log stores events triggered by .INF files (normally hardware installs) with earliest events at the top.
Setup.log is used by the Recovery Console to determine how Windows installed originally when a repair is needed.
Comsetup.log has install info about Optional Component Manager and COM+ components.
C:\Windows\debug\NetSetup.log has information about workgroup/domain memberships.
Let’s talk about Windows XP log files first. In Windows XP, most of these files are plain text, and are stored in the %systemroot% folder of the operating system. The %systemroot% folder is a variable that indicates the folder where the operating system was installed. In most cases this will be C:\Windows unless otherwise specified below.
Setuperr.log records errors (if any) in installation; check first if installs fail. A zero-byte file shows no install errors.
Setuplog.txt stores text-mode install errirs.
Setupact.log stores errors during GUI-mode. Copy it as soon as Windows is installed, as subsequent hotfixes and updates append to the file, but there are no internal date and time stamps for those changes.
Setupapi.log stores events triggered by .INF files (normally hardware installs) with earliest events at the top.
Setup.log is used by the Recovery Console to determine how Windows installed originally when a repair is needed.
Comsetup.log has install info about Optional Component Manager and COM+ components.
C:\Windows\debug\NetSetup.log has information about workgroup/domain memberships.
Comments