A+: Did your Win7 install go OK? Use the logs to check
When you complete the clean installation or upgrade, verify that your installation has gone smoothly by testing it. For example, attempt to navigate through Windows, access administrative functions, connect to the Internet, and so on.
If you have confirmed that Windows is working normally, update the system. Install the latest service pack and additional updates as necessary. It is possible that the service pack was included on your installation media, but if not, download it and install it before going any further. Then, download any other updates that are necessary utilizing the Windows Update feature.
Installations usually go smoothly, but not always. If an installation fails for any reason, or if the installation completed but Windows doesn’t seem to be behaving properly, consider reviewing the log files to find out more about the problem and why it occurred.
The following table refers to variable directory called %WINDIR%. By default, the name of this folder in Windows 7 will be “Windows.” %WINDIR% is the new name of the variable previously called %systemroot%. Also, $windows.~bt is a temporary boot folder created during setup. It remains if the installation was not successful, allowing you to analyze the log files, but should be automatically deleted when the installation completes properly.
Windows 7 and Vista, as well as Server 2008, include the capability to review Setup events within the Event Viewer, or by way of a script. See for details: http://technet.microsoft.com/en-us/library/dd744583(WS.10).aspx.
If you have confirmed that Windows is working normally, update the system. Install the latest service pack and additional updates as necessary. It is possible that the service pack was included on your installation media, but if not, download it and install it before going any further. Then, download any other updates that are necessary utilizing the Windows Update feature.
Installations usually go smoothly, but not always. If an installation fails for any reason, or if the installation completed but Windows doesn’t seem to be behaving properly, consider reviewing the log files to find out more about the problem and why it occurred.
The following table refers to variable directory called %WINDIR%. By default, the name of this folder in Windows 7 will be “Windows.” %WINDIR% is the new name of the variable previously called %systemroot%. Also, $windows.~bt is a temporary boot folder created during setup. It remains if the installation was not successful, allowing you to analyze the log files, but should be automatically deleted when the installation completes properly.
Windows 7 and Vista, as well as Server 2008, include the capability to review Setup events within the Event Viewer, or by way of a script. See for details: http://technet.microsoft.com/en-us/library/dd744583(WS.10).aspx.
| Log File Location | Description of Logfile |
| $windows.~bt\Sources\Panther | Location before Setup can access the drive |
| $windows.~bt\Sources\Rollback | If a fatal error happens, log location used if Setup does a roll back |
| %WINDIR%\Panther | Setup actions after disc configured |
| %WINDIR%Panther\setuperr.log | Info of errors diring install. A file size of 0 bytes means no install errors. |
| ^START WITH THIS LOG FILE WHEN TROUBLESHOOTING^. | |
| %WINDIR%Panther\setupact.log | Shows setup actions during the install |
| %WINDIR%\Inf\Setupapi*.log | Plug and Play devices installed |
| %WINDIR%Panther\Setup.etl | Windows Setup performance evants |
| %WINDIR%\Memory.dmp | Memory dump used for bug checks |
| %WINDIR%\Minidump\*.dmp | Mini memory dumps used for bug checks |
| %WINDIR%\System32\Sysprep\Panther | Logs made by Sysprep |
Comments