Metadata update deployment/usmt 13

windows/deployment/upgrade/log-files.md

@@ -13,20 +13,20 @@ ms.technology: itpro-deploy
 ms.date: 10/28/2022
 ---
 
-# Log files
+# Windows upgrade log files
 
 **Applies to**
--   Windows 10
 
->[!NOTE]
+- Windows 10
->This is a 400 level topic (advanced).<br>
->See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
 
+> [!NOTE]
+> This is a 400 level topic (advanced).<br>
+> See [Resolve Windows 10 upgrade errors](resolve-windows-10-upgrade-errors.md) for a full list of topics in this article.
 
 Several log files are created during each phase of the upgrade process. These log files are essential for troubleshooting upgrade problems. By default, the folders that contain these log files are hidden on the upgrade target computer. To view the log files, configure Windows Explorer to view hidden items, or use a tool to automatically gather these logs. The most useful log is **setupact.log**. The log files are located in a different folder depending on the Windows Setup phase. Recall that you can determine the phase from the extend code. 
 
->[!NOTE]
+> [!NOTE]
->Also see the [Windows Error Reporting](windows-error-reporting.md) section in this document for help locating error codes and log files.
+> Also see the [Windows Error Reporting](windows-error-reporting.md) section in this document for help locating error codes and log files.
 
 The following table describes some log files and how to use them for troubleshooting purposes:<br>
 
@@ -46,15 +46,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.
+1. **The date and time** - 2016-09-08 09:20:05.
 
-2.  **The log level** - Info, Warning, Error, Fatal Error.
+2. **The log level** - Info, Warning, Error, Fatal Error.
 
-3.  **The logging component** - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS.
+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 useful for troubleshooting Windows Setup errors.
 
-4.  **The message** - Operation completed successfully.
+4. **The message** - Operation completed successfully.
 
 See the following example:
 
@@ -62,47 +62,47 @@ See the following example:
 |------|------------|------------|------------|
 |2016-09-08 09:23:50,|  Warning |         MIG  |   Couldn't replace object C:\Users\name\Cookies. Target Object can't be removed.|
 
-
 ## Analyze log files
 
 The following instructions are meant for IT professionals. Also see the [Upgrade error codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json) section in this guide to familiarize yourself with [result codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#result-codes) and [extend codes](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#extend-codes).
 
 To analyze Windows Setup log files:
 
-1.  Determine the Windows Setup error code. This code should be returned by Windows Setup if it isn't successful with the upgrade process.
+1. Determine the Windows Setup error code. This code should be returned by Windows Setup if it isn't successful with the upgrade process.
 
-2.  Based on the [extend code](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#extend-codes) portion of the error code, determine the type and location of a [log files](#log-files) to investigate.
+2. Based on the [extend code](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#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.
+3. Open the log file in a text editor, such as notepad.
 
-4.  Using the [result code](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#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.
+4. Using the [result code](/troubleshoot/windows-client/deployment/windows-10-upgrade-error-codes?toc=/windows/deployment/toc.json&bc=/windows/deployment/breadcrumb/toc.json#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:
+5. To find the last occurrence of the result code:
 
-    1.  Scroll to the bottom of the file and select after the last character.
+    1. Scroll to the bottom of the file and select after the last character.
-    2.  Select **Edit**.
+    2. Select **Edit**.
-    3.  Select **Find**.
+    3. Select **Find**.
-    4.  Type the result code.
+    4. Type the result code.
-    5.  Under **Direction** select **Up**.
+    5. Under **Direction** select **Up**.
-    6.  Select **Find Next**.
+    6. Select **Find Next**.
 
-6.  When you've 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 prior to generating the result code.
+6. When you've 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 prior to generating the result code.
 
-7.  Search for the following important text strings:
+7. Search for the following important text strings:
 
-    *   **Shell application requested abort**
+   - `Shell application requested abort`
-    *   **Abandoning apply due to error for object**
+   - `Abandoning apply due to error for object`
 
-8.  Decode Win32 errors that appear in this section.
+8. Decode Win32 errors that appear in this section.
 
-9.  Write down the timestamp for the observed errors 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:
 
-> [!Note]
+> [!NOTE]
 > Some lines in the text below are shortened to enhance readability. For example
+> 
 > - The date and time at the start of each line (ex: 2016-10-05 15:27:08) is shortened to minutes and seconds
 > - The certificate file name, which is a long text string, is shortened to just "CN."
 

windows/deployment/usmt/usmt-loadstate-syntax.md

@@ -1,4 +1,4 @@
----This
+---
 title: LoadState Syntax (Windows 10)
 description: Learn about the syntax and usage of the command-line options available when you use the LoadState command.
 ms.reviewer: 

windows/deployment/usmt/usmt-log-files.md

@@ -11,7 +11,7 @@ ms.topic: article
 ms.technology: itpro-deploy
 ---
 
-# Log files
+# USMT log files
 
 You can use User State Migration Tool (USMT) 10.0 logs to monitor your migration and to troubleshoot errors and failed migrations. This article describes the available command-line options to enable USMT logs, and new XML elements that configure which types of errors are fatal and should halt the migration, which types are non-fatal and should be skipped so that the migration can continue.
 

windows/deployment/usmt/usmt-migrate-efs-files-and-certificates.md

@@ -13,7 +13,7 @@ ms.technology: itpro-deploy
 
 # Migrate EFS files and certificates
 
-This article describes how to migrate Encrypting File System (EFS) certificates. For more information about the `/efs` option, see [Encrypted file options](#encrypted-file-options) in [ScanState syntax](usmt-scanstate-syntax.md).
+This article describes how to migrate Encrypting File System (EFS) certificates. For more information about the `/efs` option, see [Encrypted file options](usmt-scanstate-syntax.md#encrypted-file-options) in [ScanState syntax](usmt-scanstate-syntax.md).
 
 ## To migrate EFS files and certificates
 

windows/deployment/usmt/usmt-requirements.md

@@ -34,7 +34,7 @@ The following table lists the operating systems supported in USMT.
 ## Unsupported scenarios
 
 - USMT doesn't support any of the Windows Server® operating systems.
-- USMT for Windows 10 shouldn't be used for migrating between previous versions of Windows. USMT for Windows 10 is only meant to migrate to Windows 10 or between Windows 10 versions. For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) 4.0 User’s Guide](/previous-versions/windows/server/dd560801(v=ws.10)).
+- USMT for Windows 10 shouldn't be used for migrating between previous versions of Windows. USMT for Windows 10 is only meant to migrate to Windows 10 or between Windows 10 versions. For more information about previous releases of the USMT tools, see [User State Migration Tool (USMT) 4.0 User's Guide](/previous-versions/windows/server/dd560801(v=ws.10)).
 
 ## Windows PE
 
@@ -55,10 +55,11 @@ To open an elevated command prompt:
 
 > [!IMPORTANT]
 > You must run USMT using an account with full administrative permissions, including the following privileges:
+>
 > - SeBackupPrivilege (Back up files and directories)
 > - SeDebugPrivilege (Debug programs)
 > - SeRestorePrivilege (Restore files and directories)
->- SeSecurityPrivilege (Manage auditing and security log)
+> - SeSecurityPrivilege (Manage auditing and security log)
 > - SeTakeOwnership Privilege (Take ownership of files or other objects)
 
 ## Config.xml