diff --git a/windows/deployment/upgrade/log-files.md b/windows/deployment/upgrade/log-files.md index 4adb240a10..3d678e1787 100644 --- a/windows/deployment/upgrade/log-files.md +++ b/windows/deployment/upgrade/log-files.md @@ -49,15 +49,15 @@ The following table describes some log files and how to use them for troubleshoo A setupact.log or setuperr.log entry (files are located at C:\Windows) includes the following elements: -
    -
  1. The date and time - 2016-09-08 09:20:05. -
  2. The log level - Info, Warning, Error, Fatal Error. -
  3. The logging component - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS. - -
  4. The message - Operation completed successfully. -
+1. **The date and time** - 2016-09-08 09:20:05. + +2. **The log level** - Info, Warning, Error, Fatal Error. + +3. **The logging component** - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS. + + The logging components SP (setup platform), MIG (migration engine), and CONX (compatibility information) are particularly useful for troubleshooting Windows Setup errors. + +4. **The message** - Operation completed successfully. See the following example: @@ -70,32 +70,37 @@ See the following example: The following instructions are meant for IT professionals. Also see the [Upgrade error codes](upgrade-error-codes.md) section in this guide to familiarize yourself with [result codes](upgrade-error-codes.md#result-codes) and [extend codes](upgrade-error-codes.md#extend-codes). -
To analyze Windows Setup log files: +To analyze Windows Setup log files: -
    -
  1. Determine the Windows Setup error code. This code should be returned by Windows Setup if it is not successful with the upgrade process. -
  2. Based on the extend code portion of the error code, determine the type and location of a log files to investigate. -
  3. Open the log file in a text editor, such as notepad. -
  4. Using the result code portion of the Windows Setup error code, search for the result code in the file and find the last occurrence of the code. Alternatively search for the "abort" and abandoning" text strings described in step 7 below. -
  5. To find the last occurrence of the result code: -
      -
    1. Scroll to the bottom of the file and click after the last character. -
    2. Click Edit. -
    3. Click Find. -
    4. Type the result code. -
    5. Under Direction select Up. -
    6. Click Find Next. -
    -
  6. When you have located the last occurrence of the result code, scroll up a few lines from this location in the file and review the processes that failed just prior to generating the result code. -
  7. Search for the following important text strings: - -
  8. Decode Win32 errors that appear in this section. -
  9. Write down the timestamp for the observed errors in this section. -
  10. Search other log files for additional information matching these timestamps or errors. -
+1. Determine the Windows Setup error code. This code should be returned by Windows Setup if it is not successful with the upgrade process. + +2. Based on the [extend code](upgrade-error-codes.md#extend-codes) portion of the error code, determine the type and location of a [log files](#log-files) to investigate. + +3. Open the log file in a text editor, such as notepad. + +4. Using the [result code](upgrade-error-codes.md#result-codes) portion of the Windows Setup error code, search for the result code in the file and find the last occurrence of the code. Alternatively search for the "abort" and abandoning" text strings described in step 7 below. + +5. To find the last occurrence of the result code: + + 1. Scroll to the bottom of the file and click after the last character. + 2. Click **Edit**. + 3. Click **Find**. + 4. Type the result code. + 5. Under **Direction** select **Up**. + 6. Click **Find Next**. + +6. When you have located the last occurrence of the result code, scroll up a few lines from this location in the file and review the processes that failed just prior to generating the result code. + +7. Search for the following important text strings: + + * **Shell application requested abort** + * **Abandoning apply due to error for object** + +8. Decode Win32 errors that appear in this section. + +9. Write down the timestamp for the observed errors in this section. + +10. Search other log files for additional information matching these timestamps or errors. For example, assume that the error code for an error is 0x8007042B - 0x2000D. Searching for "8007042B" reveals the following content from the setuperr.log file: