deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-14 14:27:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Metadata update deployment/usmt 15

Browse Source
This commit is contained in:
Frank Rojas 2022-11-03 21:55:53 -04:00
parent 9e755b7bca
commit a6b4b25144
4 changed files with 262 additions and 246 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
windows/deployment/usmt/usmt-requirements.md
View File

@ -34,7 +34,7 @@ The following table lists the operating systems supported in USMT.
## Unsupported scenarios ## Unsupported scenarios
- USMT doesn't support any of the Windows Server® operating systems. - 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) Overview](/previous-versions/windows/hh825227(v=win.10).
## Windows PE ## Windows PE
@ -48,7 +48,7 @@ The following table lists the operating systems supported in USMT.
To open an elevated command prompt: To open an elevated command prompt:
1. Select **Start**. 1. Select **Start**.
2. Enter **cmd** in the search function. 2. Enter `cmd` in the search function.
3. Depending on the OS you're using, **cmd** or **Command Prompt** is displayed. 3. Depending on the OS you're using, **cmd** or **Command Prompt** is displayed.
4. Right-click **cmd** or **Command Prompt**, and then select **Run as administrator**. 4. Right-click **cmd** or **Command Prompt**, and then select **Run as administrator**.
5. If the current user isn't already an administrator, you'll be prompted to enter administrator credentials. 5. If the current user isn't already an administrator, you'll be prompted to enter administrator credentials.
@ -70,11 +70,11 @@ USMT will fail if it can't migrate a file or setting, unless you specify the `/c
## LoadState ## LoadState
### Install applications before running the LoadState command. ### Install applications before running the LoadState command
Install all applications on the destination computer before restoring the user state. Installing applications before running the `LoadState.exe` command ensures that migrated settings are preserved. Install all applications on the destination computer before restoring the user state. Installing applications before running the `LoadState.exe` command ensures that migrated settings are preserved.
## Hard-Disk requirements ## Hard-disk requirements
Ensure that there's enough available space in the migration-store location and on the source and destination computers. For more information, see [Estimate Migration Store Size](usmt-estimate-migration-store-size.md). Ensure that there's enough available space in the migration-store location and on the source and destination computers. For more information, see [Estimate Migration Store Size](usmt-estimate-migration-store-size.md).

54
windows/deployment/usmt/usmt-reroute-files-and-settings.md
View File

@ -13,50 +13,39 @@ ms.technology: itpro-deploy
# Reroute Files and Settings # Reroute Files and Settings
To reroute files and settings, create a custom .xml file and specify the .xml file name on both the `ScanState.exe` and `LoadState.exe` command-lines. Th custom .xml file enables you to keep your changes separate from the default .xml files, so that it's easier to track your modifications.
To reroute files and settings, create a custom .xml file and specify this file name on both the ScanState and LoadState commandlines. This enables you to keep your changes separate from the default .xml files, so that it is easier to track your modifications. ## Reroute a folder
In this topic: The following custom .xml file migrates the directories and files from `C:\EngineeringDrafts` into the **My Documents** folder of every user. **%CSIDL_PERSONAL%** is the virtual folder representing the **My Documents** desktop item, which is equivalent to **CSIDL_MYDOCUMENTS**.
- [Reroute a Folder](#bkmk-reroutefolder)
- [Reroute a Specific File Type](#bkmk-reroutespecfiletype)
- [Reroute a Specific File](#bkmk-reroutespecificfile)
## <a href="" id="bkmk-reroutefolder"></a>Reroute a Folder
The following custom .xml file migrates the directories and files from C:\\EngineeringDrafts into the My Documents folder of every user. %CSIDL\_PERSONAL% is the virtual folder representing the My Documents desktop item, which is equivalent to CSIDL\_MYDOCUMENTS.
``` xml ``` xml
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test"> <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
<component type="Documents" context="User"> <component type="Documents" context="User">
<displayName>Engineering Drafts Documents to Personal Folder</displayName> <displayName>Engineering Drafts Documents to Personal Folder</displayName>
<role role="Data"> <role role="Data">
   <rules> <rules>
<!-- Migrate all directories and files present in c:\EngineeringDrafts folder --> <!-- Migrate all directories and files present in c:\EngineeringDrafts folder -->
<include> <include>
<objectSet> <objectSet>
<pattern type="File">C:\EngineeringDrafts\* [*]</pattern> <pattern type="File">C:\EngineeringDrafts\* [*]</pattern>
</objectSet> </objectSet>
     </include> </include>
<!-- This migrates all files and directories from C:\EngineeringDrafts to every user’s personal folder.--> <!-- This migrates all files and directories from C:\EngineeringDrafts to every user's personal folder.-->
<locationModify script="MigXmlHelper.RelativeMove('C:\EngineeringDrafts','%CSIDL_PERSONAL%')"> <locationModify script="MigXmlHelper.RelativeMove('C:\EngineeringDrafts','%CSIDL_PERSONAL%')">
<objectSet> <objectSet>
<pattern type="File">C:\EngineeringDrafts\* [*]</pattern> <pattern type="File">C:\EngineeringDrafts\* [*]</pattern>
</objectSet> </objectSet>
     </locationModify> </locationModify>
   </rules> </rules>
</role> </role>
</component> </component>
</migration> </migration>
``` ```
## <a href="" id="bkmk-reroutespecfiletype"></a>Reroute a Specific File Type ## Reroute a specific file type
The following custom .xml file reroutes .mp3 files located in the fixed drives on the source computer into the `C:\Music` folder on the destination computer.
The following custom .xml file reroutes .mp3 files located in the fixed drives on the source computer into the C:\\Music folder on the destination computer.
``` xml ``` xml
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test"> <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
@ -81,10 +70,9 @@ The following custom .xml file reroutes .mp3 files located in the fixed drives o
</migration> </migration>
``` ```
## <a href="" id="bkmk-reroutespecificfile"></a>Reroute a Specific File ## Reroute a specific file
The following custom .xml file migrates the `Sample.doc` file from `C:\EngineeringDrafts` into the **My Documents** folder of every user. **%CSIDL_PERSONAL%** is the virtual folder representing the **My Documents** desktop item, which is equivalent to **CSIDL_MYDOCUMENTS**.
The following custom .xml file migrates the Sample.doc file from C:\\EngineeringDrafts into the My Documents folder of every user. %CSIDL\_PERSONAL% is the virtual folder representing the My Documents desktop item, which is equivalent to CSIDL\_MYDOCUMENTS.
``` xml ``` xml
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test"> <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test">
@ -108,20 +96,10 @@ The following custom .xml file migrates the Sample.doc file from C:\\Engineering
</migration> </migration>
``` ```
## Related topics ## Related articles
[Customize USMT XML Files](usmt-customize-xml-files.md)
[Conflicts and Precedence](usmt-conflicts-and-precedence.md)
[USMT XML Reference](usmt-xml-reference.md)
 
 
[Customize USMT XML files](usmt-customize-xml-files.md)
[Conflicts and precedence](usmt-conflicts-and-precedence.md)
[USMT XML reference](usmt-xml-reference.md)

23
windows/deployment/usmt/usmt-resources.md
View File

@ -11,33 +11,26 @@ ms.topic: article
ms.technology: itpro-deploy ms.technology: itpro-deploy
--- ---
# USMT Resources # USMT resources
## USMT Online Resources
## USMT online resources
- [ADK Release Notes](/windows-hardware/get-started/what-s-new-in-kits-and-tools) - [ADK Release Notes](/windows-hardware/get-started/what-s-new-in-kits-and-tools)
- Microsoft Visual Studio - Microsoft Visual Studio
- You can use the User State Migration Tool (USMT) XML schema (the MigXML.xsd file) to validate the migration .xml files using an XML authoring tool such as Microsoft® Visual Studio®. - You can use the User State Migration Tool (USMT) XML schema (the `MigXML.xsd` file) to validate the migration .xml files using an XML authoring tool such as Microsoft® Visual Studio®.
For more information about how to use the schema with your XML authoring environment, see the environment’s documentation. For more information about how to use the schema with your XML authoring environment, see the environment's documentation.
- [Ask the Directory Services Team blog](/archive/blogs/askds/) - [Ask the Directory Services Team blog](https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/bg-p/AskDS)
- Forums: - Forums:
- [Microsoft Deployment Toolkit](https://go.microsoft.com/fwlink/p/?LinkId=226386) - [Microsoft Deployment Toolkit](https://go.microsoft.com/fwlink/p/?LinkId=226386)
- [Configuration Manager Operating System Deployment](https://go.microsoft.com/fwlink/p/?LinkId=226388) - [Configuration Manager Operating System Deployment](https://social.technet.microsoft.com/Forums/en-US/home?forum=ConfigMgrCBOSD)
## Related topics ## Related articles
[User State Migration Tool (USMT) overview topics](usmt-topics.md)
[User State Migration Tool (USMT) Overview Topics](usmt-topics.md)
 
 

371
windows/deployment/usmt/usmt-return-codes.md
View File

@ -1,6 +1,6 @@
--- ---
title: Return Codes (Windows 10) title: Return Codes (Windows 10)
description: Learn about User State Migration Tool (USMT) 10.0 return codes and error messages. Also view a list of USMT return codes and their associated migration steps. description: Learn about User State Migration Tool (USMT) 10.0 return codes and error messages. Also view a list of USMT return codes and their associated migration steps.
ms.reviewer: ms.reviewer:
manager: aaroncz manager: aaroncz
ms.author: frankroj ms.author: frankroj
@ -11,265 +11,310 @@ ms.topic: article
ms.technology: itpro-deploy ms.technology: itpro-deploy
--- ---
# Return Codes # Return codes
This topic describes User State Migration Tool (USMT) 10.0 return codes and error messages. Also included is a table listing the USMT return codes with their associated mitigation steps. In addition, this topic provides tips to help you use the logfiles to determine why you received an error. This topic describes User State Migration Tool (USMT) 10.0 return codes and error messages. Also included is a table listing the USMT return codes with their associated mitigation steps. In addition, this topic provides tips to help you use the logfiles to determine why you received an error.
Understanding the requirements for running USMT can help minimize errors in your USMT migrations. For more information, see [USMT Requirements](usmt-requirements.md). Understanding the requirements for running USMT can help minimize errors in your USMT migrations. For more information, see [USMT Requirements](usmt-requirements.md).
## In This Topic ## USMT return codes
[USMT Return Codes](#bkmk-returncodes)
[USMT Error Messages](#bkmk-errormessages)
[Troubleshooting Return Codes and Error Messages](#bkmk-tscodeserrors)
## <a href="" id="bkmk-returncodes"></a>USMT Return Codes
If you encounter an error in your USMT migration, you can use return codes and the more specific information provided in the associated USMT error messages to troubleshoot the issue and to identify mitigation steps. If you encounter an error in your USMT migration, you can use return codes and the more specific information provided in the associated USMT error messages to troubleshoot the issue and to identify mitigation steps.
Return codes are grouped into the following broad categories that describe their area of error reporting: Return codes are grouped into the following broad categories that describe their area of error reporting:
Success or User Cancel - Success or User Cancel
Invalid Command Lines - Invalid Command Lines
Setup and Initialization - Setup and Initialization
Non-fatal Errors - Non-fatal Errors
Fatal Errors - Fatal Errors
As a best practice, we recommend that you set verbosity level to 5, **/v**<em>:5</em>, on the **ScanState**, **LoadState**, and **USMTUtils** command lines so that the most detailed reporting is available in the respective USMT logs. You can use a higher verbosity level if you want the log files output to go to a debugger. As a best practice, we recommend that you set verbosity level to 5, `v:5`, on the `ScanState.exe`, `LoadState.exe`, and `USMTUtils.exe` command lines so that the most detailed reporting is available in the respective USMT logs. You can use a higher verbosity level if you want the log files output to go to a debugger.
## <a href="" id="bkmk-errormessages"></a>USMT Error Messages ## USMT error messages
Error messages provide more detailed information about the migration problem than the associated return code. For example, the **ScanState**, **LoadState**, or **USMTUtils** tool might return a code of "11” (for “USMT\_INVALID\_PARAMETERS") and a related error message that reads "/key and /keyfile both specified". The error message is displayed at the command prompt and is identified in the **ScanState**, **LoadState**, or **USMTUtils** log files to help you determine why the return code was received. Error messages provide more detailed information about the migration problem than the associated return code. For example, the **ScanState**, **LoadState**, or **USMTUtils** tool might return a code of **11** (for **USMT_INVALID_PARAMETERS**) and a related error message that reads **/key and /keyfile both specified**. The error message is displayed at the command prompt and is identified in the **ScanState**, **LoadState**, or **USMTUtils** log files to help you determine why the return code was received.
You can obtain more information about any listed Windows application programming interface (API) system error codes by typing **net helpmsg** on the command line and, then typing the error code number. For more information about System Error Codes, see [this Microsoft Web site](/windows/win32/debug/system-error-codes--0-499-). You can obtain more information about any listed **Windows** system error codes by typing in a command prompt window `net.exe helpmsg <error_number>` where *<error_number>* is the error code number generated by the error message. For more information about System Error Codes, see [System Error Codes (0-499)](/windows/win32/debug/system-error-codes--0-499-).
## <a href="" id="bkmk-tscodeserrors"></a>Troubleshooting Return Codes and Error Messages ## Troubleshooting return codes and error messages
The following information lists each return code by numeric value, along with the associated error messages and suggested troubleshooting actions. The following information lists each return code by numeric value, along with the associated error messages and suggested troubleshooting actions.
- **0: USMT_SUCCESS** ### **0: USMT_SUCCESS**
- **Error message**: Successful run
- **1: USMT_DISPLAY_HELP**
- **Error message**: Command line help requested
- **2: USMT_STATUS_CANCELED**
- **Error message**:
- Gather was aborted because of an EFS file
- User chose to cancel (such as pressing CTRL+C)
- **3: USMT_WOULD_HAVE_FAILED**
- **Error message**: At least one error was skipped as a result of /c.
- **Troubleshooting, mitigation, workarounds**: Review ScanState, LoadState, or UsmtUtils log for details about command-line errors.
- **11: USMT_INVALID_PARAMETERS**
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| /all conflicts with /ui, /ue or /uel | Review ScanState log or LoadState log for details about command-line errors. | | **Successful run** | NA |
| /auto expects an optional parameter for the script folder | Review ScanState log or LoadState log for details about command-line errors. |
| /encrypt can't be used with /nocompress | Review ScanState log or LoadState log for details about command-line errors. |
| /encrypt requires /key or /keyfile | Review ScanState log or LoadState log for details about command-line errors. |
| /genconfig can't be used with most other options | Review ScanState log or LoadState log for details about command-line errors. |
| /genmigxml can't be used with most other options | Review ScanState log or LoadState log for details about command-line errors. |
| /hardlink requires /nocompress | Review ScanState log or LoadState log for details about command-line errors. |
| /key and /keyfile both specified | Review ScanState log or LoadState log for details about command-line errors. |
| /key or /keyfile used without enabling encryption | Review ScanState log or LoadState log for details about command-line errors. |
| /lae is only used with /lac | Review ScanState log or LoadState log for details about command-line errors. |
| /listfiles cannot be used with /p | Review ScanState log or LoadState log for details about command-line errors. |
| /offline requires a valid path to an XML file describing offline paths | Review ScanState log or LoadState log for details about command-line errors. |
| /offlinewindir requires a valid path to offline windows folder | Review ScanState log or LoadState log for details about command-line errors. |
| /offlinewinold requires a valid path to offline windows folder | Review ScanState log or LoadState log for details about command-line errors. |
| A command was already specified | Verify that the command-line syntax is correct and that there are no duplicate commands. |
| An option argument is missing | Review ScanState log or LoadState log for details about command-line errors. |
| An option is specified more than once and is ambiguous | Review ScanState log or LoadState log for details about command-line errors. |
| By default /auto selects all users and uses the highest log verbosity level. Switches like /all, /ui, /ue, /v are not allowed. | Review ScanState log or LoadState log for details about command-line errors. |
| Command line arguments are required. Specify /? for options. | Review ScanState log or LoadState log for details about command-line errors. |
| Command line option is not valid | Review ScanState log or LoadState log for details about command-line errors. |
| EFS parameter specified is not valid for /efs | Review ScanState log or LoadState log for details about command-line errors. |
| File argument is invalid for /genconfig | Review ScanState log or LoadState log for details about command-line errors. |
| File argument is invalid for /genmigxml | Review ScanState log or LoadState log for details about command-line errors. |
| Invalid space estimate path. Check the parameters and/or file system permissions | Review ScanState log or LoadState log for details about command-line errors. |
| List file path argument is invalid for /listfiles | Review ScanState log or LoadState log for details about command-line errors. |
| Retry argument must be an integer | Review ScanState log or LoadState log for details about command-line errors. |
| Settings store argument specified is invalid | Review ScanState log or LoadState log for details about command-line errors. Make sure that the store path is accessible and that the proper permission levels are set. |
| Specified encryption algorithm is not supported | Review ScanState log or LoadState log for details about command-line errors. |
| The /efs:hardlink requires /hardlink | Review ScanState log or LoadState log for details about command-line errors. |
| The /targetWindows7 option is only available for Windows XP, Windows Vista, and Windows 7 | Review ScanState log or LoadState log for details about command-line errors. |
| The store parameter is required but not specified | Review ScanState log or LoadState log for details about command-line errors. |
| The source-to-target domain mapping is invalid for /md | Review ScanState log or LoadState log for details about command-line errors. |
| The source-to-target user account mapping is invalid for /mu | Review ScanState log or LoadState log for details about command-line errors. |
| Undefined or incomplete command line option | Review ScanState log or LoadState log for details about command-line errors. <br/><br/>Category: Invalid Command Lines|
| Use /nocompress, or provide an XML file path with /p"pathtoafile" to get a compressed store size estimate | Review ScanState log or LoadState log for details about command-line errors. |
| User exclusion argument is invalid | Review ScanState log or LoadState log for details about command-line errors. |
| Verbosity level must be specified as a sum of the desired log options: Verbose (0x01), Record Objects (0x04), Echo to debug port (0x08) | Review ScanState log or LoadState log for details about command-line errors. |
| Volume shadow copy feature is not supported with a hardlink store | Review ScanState log or LoadState log for details about command-line errors. |
| Wait delay argument must be an integer | Review ScanState log or LoadState log for details about command-line errors. |
- **12: USMT_ERROR_OPTION_PARAM_TOO_LARGE** ### **1: USMT_DISPLAY_HELP**
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| Command line arguments cannot exceed 256 characters | Review ScanState log or LoadState log for details about command-line errors.<br/><br/>Category: Invalid Command Lines | | **Command line help requested** | NA |
| Specified settings store path exceeds the maximum allowed length of 256 characters | Review ScanState log or LoadState log for details about command-line errors. |
### **2: USMT_STATUS_CANCELED**
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **Gather was aborted because of an EFS file** | NA |
| **User chose to cancel (such as pressing CTRL+C)** | NA |
### **3: USMT_WOULD_HAVE_FAILED**
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **At least one error was skipped as a result of /c.** | Review ScanState, LoadState, or UsmtUtils log for details about command-line errors. |
### **11: USMT_INVALID_PARAMETERS**
- **13: USMT_INIT_LOGFILE_FAILED**
- **Error message**: Log path argument is invalid for /l
- **Troubleshooting, mitigation, workarounds**: When /l is specified in the ScanState command line, USMT validates the path. Verify that the drive and other information, for example file system characters, are correct.
- **Category**: Invalid Command Lines - **Category**: Invalid Command Lines
- **14: USMT_ERROR_USE_LAC** | Error message | Troubleshooting, mitigation, workarounds |
- **Error message**: Unable to create a local account because /lac was not specified | --- | --- |
- **Troubleshooting, mitigation, workarounds**: When creating local accounts, the command-line options /lac and /lae should be used. | **/all conflicts with /ui, /ue or /uel** | Review ScanState log or LoadState log for details about command-line errors. |
| **/auto expects an optional parameter for the script folder** | Review ScanState log or LoadState log for details about command-line errors. |
| **/encrypt can't be used with /nocompress** | Review ScanState log or LoadState log for details about command-line errors. |
| **/encrypt requires /key or /keyfile** | Review ScanState log or LoadState log for details about command-line errors. |
| **/genconfig can't be used with most other options** | Review ScanState log or LoadState log for details about command-line errors. |
| **/genmigxml can't be used with most other options** | Review ScanState log or LoadState log for details about command-line errors. |
| **/hardlink requires /nocompress** | Review ScanState log or LoadState log for details about command-line errors. |
| **/key and /keyfile both specified** | Review ScanState log or LoadState log for details about command-line errors. |
| **/key or /keyfile used without enabling encryption** | Review ScanState log or LoadState log for details about command-line errors. |
| **/lae is only used with /lac** | Review ScanState log or LoadState log for details about command-line errors. |
| **/listfiles cannot be used with /p** | Review ScanState log or LoadState log for details about command-line errors. |
| **/offline requires a valid path to an XML file describing offline paths** | Review ScanState log or LoadState log for details about command-line errors. |
| **/offlinewindir requires a valid path to offline windows folder** | Review ScanState log or LoadState log for details about command-line errors. |
| **/offlinewinold requires a valid path to offline windows folder** | Review ScanState log or LoadState log for details about command-line errors. |
| **A command was already specified** | Verify that the command-line syntax is correct and that there are no duplicate commands. |
| **An option argument is missing** | Review ScanState log or LoadState log for details about command-line errors. |
| **An option is specified more than once and is ambiguous** | Review ScanState log or LoadState log for details about command-line errors. |
| **By default /auto selects all users and uses the highest log verbosity level. Switches like /all, /ui, /ue, /v are not allowed.** | Review ScanState log or LoadState log for details about command-line errors. |
| **Command line arguments are required. Specify /? for options.** | Review ScanState log or LoadState log for details about command-line errors. |
| **Command line option is not valid** | Review ScanState log or LoadState log for details about command-line errors. |
| **EFS parameter specified is not valid for /efs** | Review ScanState log or LoadState log for details about command-line errors. |
| **File argument is invalid for /genconfig** | Review ScanState log or LoadState log for details about command-line errors. |
| **File argument is invalid for /genmigxml** | Review ScanState log or LoadState log for details about command-line errors. |
| **Invalid space estimate path. Check the parameters and/or file system permissions** | Review ScanState log or LoadState log for details about command-line errors. |
| **List file path argument is invalid for /listfiles** | Review ScanState log or LoadState log for details about command-line errors. |
| **Retry argument must be an integer** | Review ScanState log or LoadState log for details about command-line errors. |
| **Settings store argument specified is invalid** | Review ScanState log or LoadState log for details about command-line errors. Make sure that the store path is accessible and that the proper permission levels are set. |
| **Specified encryption algorithm is not supported** | Review ScanState log or LoadState log for details about command-line errors. |
| **The /efs:hardlink requires /hardlink** | Review ScanState log or LoadState log for details about command-line errors. |
| **The /targetWindows7 option is only available for Windows XP, Windows Vista, and Windows 7** | Review ScanState log or LoadState log for details about command-line errors. |
| **The store parameter is required but not specified** | Review ScanState log or LoadState log for details about command-line errors. |
| **The source-to-target domain mapping is invalid for /md** | Review ScanState log or LoadState log for details about command-line errors. |
| **The source-to-target user account mapping is invalid for /mu** | Review ScanState log or LoadState log for details about command-line errors. |
| **Undefined or incomplete command line option** | Review ScanState log or LoadState log for details about command-line errors. |
| **Use /nocompress, or provide an XML file path with /p"pathtoafile" to get a compressed store size estimate** | Review ScanState log or LoadState log for details about command-line errors. |
| **User exclusion argument is invalid** | Review ScanState log or LoadState log for details about command-line errors. |
| **Verbosity level must be specified as a sum of the desired log options: Verbose (0x01), Record Objects (0x04), Echo to debug port (0x08)** | Review ScanState log or LoadState log for details about command-line errors. |
| **Volume shadow copy feature is not supported with a hardlink store** | Review ScanState log or LoadState log for details about command-line errors. |
| **Wait delay argument must be an integer** | Review ScanState log or LoadState log for details about command-line errors. |
### **12: USMT_ERROR_OPTION_PARAM_TOO_LARGE**
- **Category**: Invalid Command Lines - **Category**: Invalid Command Lines
- **26: USMT_INIT_ERROR** | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **Command line arguments cannot exceed 256 characters** | Review ScanState log or LoadState log for details about command-line errors. |
| **Specified settings store path exceeds the maximum allowed length of 256 characters** | Review ScanState log or LoadState log for details about command-line errors. |
### **13: USMT_INIT_LOGFILE_FAILED**
- **Category**: Invalid Command Lines
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| Multiple Windows installations found | Listfiles.txt could not be created. Verify that the location you specified for the creation of this file is valid. <br/><br/>Category: Setup and Initialization | | **Log path argument is invalid for /l** | When /l is specified in the ScanState command line, USMT validates the path. Verify that the drive and other information, for example file system characters, are correct. |
| Software malfunction or unknown exception | Check all loaded .xml files for errors, common error when using /I to load the Config.xml file. |
| Unable to find a valid Windows directory to proceed with requested offline operation; Check if offline input file is present and has valid entries | Verify that the offline input file is present and that it has valid entries. USMT could not find valid offline operating system. Verify your offline directory mapping. |
- **27: USMT_INVALID_STORE_LOCATION** ### **14: USMT_ERROR_USE_LAC**
- **Category**: Invalid Command Lines
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| A store path can't be used because an existing store exists; specify /o to overwrite | Specify /o to overwrite an existing intermediate or migration store. <br/><br/>Category: Setup and Initialization | | **Unable to create a local account because /lac was not specified** | When creating local accounts, the command-line options /lac and /lae should be used. |
| A store path is missing or has incomplete data | Make sure that the store path is accessible and that the proper permission levels are set. |
| An error occurred during store creation | Make sure that the store path is accessible and that the proper permission levels are set. Specify /o to overwrite an existing intermediate or migration store. |
| An inappropriate device such as a floppy disk was specified for the store | Make sure that the store path is accessible and that the proper permission levels are set. |
| Invalid store path; check the store parameter and/or file system permissions | Invalid store path; check the store parameter and/or file system permissions. |
| The file layout and/or file content is not recognized as a valid store | Make sure that the store path is accessible and that the proper permission levels are set. Specify /o to overwrite an existing intermediate or migration store. |
| The store path holds a store incompatible with the current USMT version | Make sure that the store path is accessible and that the proper permission levels are set. |
| The store save location is read-only or does not support a requested storage option | Make sure that the store path is accessible and that the proper permission levels are set. |
- **28: USMT_UNABLE_GET_SCRIPTFILES** ### **26: USMT_INIT_ERROR**
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| Script file is invalid for /i | Check all specified migration .xml files for errors. This is a common error when using /i to load the Config.xml file. <br/><br/>Category: Setup and Initialization |
| Unable to find a script file specified by /i | Verify the location of your script files, and ensure that the command-line options are correct. |
- **29: USMT_FAILED_MIGSTARTUP**
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| A minimum of 250 MB of free space is required for temporary files | Verify that the system meets the minimum temporary disk space requirement of 250 MB. As a workaround, you can set the environment variable `USMT_WORKING_DIR=<path>` to redirect the temporary files working directory. <br/><br/>Category: Setup and Initialization |
| Another process is preventing migration; only one migration tool can run at a time | Check the ScanState log file for migration .xml file errors. |
| Failed to start main processing, look in log for system errors or check the installation | Check the ScanState log file for migration .xml file errors. |
| Migration failed because of an XML error; look in the log for specific details | Check the ScanState log file for migration .xml file errors. |
| Unable to automatically map the drive letters to match the online drive letter layout; Use /offline to provide a mapping table | Check the ScanState log file for migration .xml file errors. |
- **31: USMT_UNABLE_FINDMIGUNITS**
- **Error message**: An error occurred during the discover phase; the log should have more specific information
- **Troubleshooting, mitigation, workarounds**: Check the ScanState log file for migration .xml file errors.
- **Category**: Setup and Initialization - **Category**: Setup and Initialization
- **32: USMT_FAILED_SETMIGRATIONTYPE** | Error message | Troubleshooting, mitigation, workarounds |
- **Error message**: An error occurred processing the migration system | --- | --- |
- **Troubleshooting, mitigation, workarounds**: Check the ScanState log file for migration .xml file errors, or use online Help by typing /? on the command line. | **Multiple Windows installations found** | Listfiles.txt could not be created. Verify that the location you specified for the creation of this file is valid. |
| **Software malfunction or unknown exception** | Check all loaded .xml files for errors, common error when using /I to load the Config.xml file. |
| **Unable to find a valid Windows directory to proceed with requested offline operation; Check if offline input file is present and has valid entries** | Verify that the offline input file is present and that it has valid entries. USMT could not find valid offline operating system. Verify your offline directory mapping. |
### **27: USMT_INVALID_STORE_LOCATION**
- **Category**: Setup and Initialization - **Category**: Setup and Initialization
- **33: USMT_UNABLE_READKEY** | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **A store path can't be used because an existing store exists; specify /o to overwrite** | Specify /o to overwrite an existing intermediate or migration store. |
| **A store path is missing or has incomplete data** | Make sure that the store path is accessible and that the proper permission levels are set. |
| **An error occurred during store creation** | Make sure that the store path is accessible and that the proper permission levels are set. Specify /o to overwrite an existing intermediate or migration store. |
| **An inappropriate device such as a floppy disk was specified for the store** | Make sure that the store path is accessible and that the proper permission levels are set. |
| **Invalid store path; check the store parameter and/or file system permissions** | Invalid store path; check the store parameter and/or file system permissions. |
| **The file layout and/or file content is not recognized as a valid store** | Make sure that the store path is accessible and that the proper permission levels are set. Specify /o to overwrite an existing intermediate or migration store. |
| **The store path holds a store incompatible with the current USMT version** | Make sure that the store path is accessible and that the proper permission levels are set. |
| **The store save location is read-only or does not support a requested storage option** | Make sure that the store path is accessible and that the proper permission levels are set. |
### **28: USMT_UNABLE_GET_SCRIPTFILES**
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| Error accessing the file specified by the /keyfile parameter | Check the ScanState log file for migration .xml file errors, or use online Help by typing /? on the command line. <br/><br/>Category: Setup and Initialization | | **Script file is invalid for /i** | Check all specified migration .xml files for errors. This is a common error when using /i to load the Config.xml file. |
| The encryption key must have at least one character | Check the ScanState log file for migration .xml file errors, or use online Help by typing /? on the command line. | | **Unable to find a script file specified by /i** | Verify the location of your script files, and ensure that the command-line options are correct. |
- **34: USMT_ERROR_INSUFFICIENT_RIGHTS** ### **29: USMT_FAILED_MIGSTARTUP**
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| Directory removal requires elevated privileges | Log on as Administrator, and run with elevated privileges. <br/><br/>Category: Setup and Initialization | | **A minimum of 250 MB of free space is required for temporary files** | Verify that the system meets the minimum temporary disk space requirement of 250 MB. As a workaround, you can set the environment variable `USMT_WORKING_DIR=<path>` to redirect the temporary files working directory. |
| No rights to create user profiles; log in as Administrator; run with elevated privileges | Log on as Administrator, and run with elevated privileges. | | **Another process is preventing migration; only one migration tool can run at a time** | Check the ScanState log file for migration .xml file errors. |
| No rights to read or delete user profiles; log in as Administrator, run with elevated privileges | Log on as Administrator, and run with elevated privileges. | | **Failed to start main processing, look in log for system errors or check the installation** | Check the ScanState log file for migration .xml file errors. |
| **Migration failed because of an XML error; look in the log for specific details** | Check the ScanState log file for migration .xml file errors. |
| **Unable to automatically map the drive letters to match the online drive letter layout; Use /offline to provide a mapping table** | Check the ScanState log file for migration .xml file errors. |
- **35: USMT_UNABLE_DELETE_STORE** ### **31: USMT_UNABLE_FINDMIGUNITS**
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| A reboot is required to remove the store | Reboot to delete any files that could not be deleted when the command was executed. <br/><br/>Category: Setup and Initialization | | **An error occurred during the discover phase; the log should have more specific information** | Check the ScanState log file for migration .xml file errors. |
| A store path can't be used because it contains data that could not be overwritten | A migration store could not be deleted. If you are using a hardlink migration store you might have a locked file in it. You should manually delete the store, or use **USMTUtils /rd** command to delete the store. |
| There was an error removing the store | Review ScanState log or LoadState log for details about command-line errors. |
- **36: USMT_ERROR_UNSUPPORTED_PLATFORM**
### **32: USMT_FAILED_SETMIGRATIONTYPE**
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| Compliance check failure; please check the logs for details | Investigate whether there is an active temporary profile on the system. <br/><br/>Category: Setup and Initialization | | **An error occurred processing the migration system** | Check the ScanState log file for migration .xml file errors, or use online Help by typing /? on the command line. |
| Use of /offline is not supported during apply | The **/offline** command was not used while running in the Windows Preinstallation Environment (WinPE). |
| Use /offline to run gather on this platform | The **/offline** command was not used while running in WinPE. |
- **37: USMT_ERROR_NO_INVALID_KEY**
### **33: USMT_UNABLE_READKEY**
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **Error accessing the file specified by the /keyfile parameter** | Check the ScanState log file for migration .xml file errors, or use online Help by typing /? on the command line. |
| **The encryption key must have at least one character** | Check the ScanState log file for migration .xml file errors, or use online Help by typing /? on the command line. |
### **34: USMT_ERROR_INSUFFICIENT_RIGHTS**
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **Directory removal requires elevated privileges** | Log on as Administrator, and run with elevated privileges. |
| **No rights to create user profiles; log in as Administrator; run with elevated privileges** | Log on as Administrator, and run with elevated privileges. |
| **No rights to read or delete user profiles; log in as Administrator, run with elevated privileges** | Log on as Administrator, and run with elevated privileges. |
### **35: USMT_UNABLE_DELETE_STORE**
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **A reboot is required to remove the store** | Reboot to delete any files that could not be deleted when the command was executed. |
| **A store path can't be used because it contains data that could not be overwritten** | A migration store could not be deleted. If you are using a hardlink migration store you might have a locked file in it. You should manually delete the store, or use **USMTUtils /rd** command to delete the store. |
| **There was an error removing the store** | Review ScanState log or LoadState log for details about command-line errors. |
### **36: USMT_ERROR_UNSUPPORTED_PLATFORM**
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **Compliance check failure; please check the logs for details** | Investigate whether there is an active temporary profile on the system. |
| **Use of /offline is not supported during apply** | The **/offline** command was not used while running in the Windows Preinstallation Environment (WinPE). |
| **Use /offline to run gather on this platform** | The **/offline** command was not used while running in WinPE. |
### **37: USMT_ERROR_NO_INVALID_KEY**
- **Error message**: The store holds encrypted data but the correct encryption key was not provided - **Error message**: The store holds encrypted data but the correct encryption key was not provided
- **Troubleshooting, mitigation, workarounds**: Verify that you have included the correct encryption /key or /keyfile. - **Troubleshooting, mitigation, workarounds**: Verify that you have included the correct encryption /key or /keyfile.
- **Category**: Setup and Initialization - **Category**: Setup and Initialization
- **38: USMT_ERROR_CORRUPTED_NOTENCRYPTED_STORE** ### **38: USMT_ERROR_CORRUPTED_NOTENCRYPTED_STORE**
- **Error message**: An error occurred during store access - **Error message**: An error occurred during store access
- **Troubleshooting, mitigation, workarounds**: Review ScanState log or LoadState log for details about command-line errors. Make sure that the store path is accessible and that the proper permission levels are set. - **Troubleshooting, mitigation, workarounds**: Review ScanState log or LoadState log for details about command-line errors. Make sure that the store path is accessible and that the proper permission levels are set.
- **Category**: Setup and Initialization - **Category**: Setup and Initialization
- **39: USMT_UNABLE_TO_READ_CONFIG_FILE** ### **39: USMT_UNABLE_TO_READ_CONFIG_FILE**
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| Error reading Config.xml | Review ScanState log or LoadState log for details about command-line errors in the Config.xml file. <br/><br/>Category: Setup and Initialization | | **Error reading Config.xml** | Review ScanState log or LoadState log for details about command-line errors in the Config.xml file. |
| File argument is invalid for /config | Check the command line you used to load the Config.xml file. You can use online Help by typing /? on the command line. | | **File argument is invalid for /config** | Check the command line you used to load the Config.xml file. You can use online Help by typing /? on the command line. |
- **40: USMT_ERROR_UNABLE_CREATE_PROGRESS_LOG** ### **40: USMT_ERROR_UNABLE_CREATE_PROGRESS_LOG**
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| Error writing to the progress log | The Progress log could not be created. Verify that the location is valid and that you have write access. <br/><br/>Category: Setup and Initialization | | **Error writing to the progress log** | The Progress log could not be created. Verify that the location is valid and that you have write access. |
| Progress log argument is invalid for /progress | The Progress log could not be created. Verify that the location is valid and that you have write access. | | **Progress log argument is invalid for /progress** | The Progress log could not be created. Verify that the location is valid and that you have write access. |
- **41: USMT_PREFLIGHT_FILE_CREATION_FAILED** ### **41: USMT_PREFLIGHT_FILE_CREATION_FAILED**
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| Can't overwrite existing file | The Progress log could not be created. Verify that the location is valid and that you have write access. <br/><br/>Category: Setup and Initialization | | **Can't overwrite existing file** | The Progress log could not be created. Verify that the location is valid and that you have write access. |
| Invalid space estimate path. Check the parameters and/or file system permissions | Review ScanState log or LoadState log for details about command-line errors. | | **Invalid space estimate path. Check the parameters and/or file system permissions** | Review ScanState log or LoadState log for details about command-line errors. |
- **42: USMT_ERROR_CORRUPTED_STORE** ### **42: USMT_ERROR_CORRUPTED_STORE**
- **Error message**: The store contains one or more corrupted files - **Error message**: The store contains one or more corrupted files
- **Troubleshooting, mitigation, workarounds**: Review UsmtUtils log for details about the corrupted files. For information on how to extract the files that are not corrupted, see [Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md). - **Troubleshooting, mitigation, workarounds**: Review UsmtUtils log for details about the corrupted files. For information on how to extract the files that are not corrupted, see [Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md).
- **61: USMT_MIGRATION_STOPPED_NONFATAL** ### **61: USMT_MIGRATION_STOPPED_NONFATAL**
- **Error message**: Processing stopped due to an I/O error - **Error message**: Processing stopped due to an I/O error
- **Troubleshooting, mitigation, workarounds**: USMT exited but can continue with the /c command-line option, with the optional configurable &lt;ErrorControl&gt; section or by using the /vsc command-line option. - **Troubleshooting, mitigation, workarounds**: USMT exited but can continue with the /c command-line option, with the optional configurable &lt;ErrorControl&gt; section or by using the /vsc command-line option.
- **Category**: Non-fatal Errors - **Category**: Non-fatal Errors
- **71: USMT_INIT_OPERATING_ENVIRONMENT_FAILED** ### **71: USMT_INIT_OPERATING_ENVIRONMENT_FAILED**
- **Category**: Fatal Errors
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| A Windows Win32 API error occurred | Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details. <br/><br/>Category: Fatal Errors | | **A Windows Win32 API error occurred** | Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details. |
| An error occurred when attempting to initialize the diagnostic mechanisms such as the log | Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details. | | **An error occurred when attempting to initialize the diagnostic mechanisms such as the log** | Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details. |
| Failed to record diagnostic information | Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details. | | **Failed to record diagnostic information** | Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details. |
| Unable to start. Make sure you are running USMT with elevated privileges | Exit USMT and log in again with elevated privileges. | | **Unable to start. Make sure you are running USMT with elevated privileges** | Exit USMT and log in again with elevated privileges. |
- **72: USMT_UNABLE_DOMIGRATION** ### **72: USMT_UNABLE_DOMIGRATION**
- **Category**: Fatal Errors
| Error message | Troubleshooting, mitigation, workarounds | | Error message | Troubleshooting, mitigation, workarounds |
| --- | --- | | --- | --- |
| An error occurred closing the store | Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. <br/><br/>Category: Fatal Errors| | **An error occurred closing the store** | Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. |
| An error occurred in the apply process | Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. | | **An error occurred in the apply process** | Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. |
| An error occurred in the gather process | Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. | | **An error occurred in the gather process** | Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. |
| Out of disk space while writing the store | Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. | | **Out of disk space while writing the store** | Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. |
| Out of temporary disk space on the local system | Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. | | **Out of temporary disk space on the local system** | Data transfer has begun, and there was an error during migration-store creation or during the apply phase. Review the ScanState log or LoadState log for details. |
## Related topics ## Related topics
[User State Migration Tool (USMT) Troubleshooting](usmt-troubleshooting.md) [User State Migration Tool (USMT) troubleshooting](usmt-troubleshooting.md)
[Log Files](usmt-log-files.md) [USMT log files](usmt-log-files.md)