deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Metadata update deployment/usmt 17

Browse Source
This commit is contained in:
Frank Rojas
2022-11-04 15:11:10 -04:00
parent 883a7ce855
commit d90dd9e71d
12 changed files with 362 additions and 376 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -13,7 +13,7 @@ ms.technology: itpro-deploy
# 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 article 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 article 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).
@ -33,11 +33,11 @@ Return codes are grouped into the following broad categories that describe their
- Fatal Errors
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.
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.
## 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** 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-).
@ -139,7 +139,7 @@ The following information lists each return code by numeric value, along with th
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **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. |
| **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. |
### 14: USMT_ERROR_USE_LAC
@ -147,7 +147,7 @@ The following information lists each return code by numeric value, along with th
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **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. |
| **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. |
### 26: USMT_INIT_ERROR
@ -155,9 +155,9 @@ The following information lists each return code by numeric value, along with th
| 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. |
| **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. |
| **Multiple Windows installations found** | Listfiles.txt couldn't 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 couldn't find valid offline operating system. Verify your offline directory mapping. |
### 27: USMT_INVALID_STORE_LOCATION
@ -165,12 +165,12 @@ The following information lists each return code by numeric value, along with th
| 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 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 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 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. |
@ -180,7 +180,7 @@ The following information lists each return code by numeric value, along with th
| 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. |
| **Script file is invalid for /i** | Check all specified migration .xml files for errors. This error is common when using `/i` to load the `Config.xml` file. |
| **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
@ -203,15 +203,13 @@ The following information lists each return code by numeric value, along with th
| --- | --- |
| **An error occurred during the discover phase; the log should have more specific information** | Check the ScanState log file for migration .xml file errors. |
### 32: USMT_FAILED_SETMIGRATIONTYPE
- **Category**: Setup and Initialization
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **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. |
| **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. |
### 33: USMT_UNABLE_READKEY
@ -219,8 +217,8 @@ The following information lists each return code by numeric value, along with th
| 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. |
| **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
@ -228,9 +226,9 @@ The following information lists each return code by numeric value, along with th
| 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. |
| **Directory removal requires elevated privileges** | Sign in as Administrator, and run with elevated privileges. |
| **No rights to create user profiles; log in as Administrator; run with elevated privileges** | Sign in as Administrator, and run with elevated privileges. |
| **No rights to read or delete user profiles; log in as Administrator, run with elevated privileges** | Sign in as Administrator, and run with elevated privileges. |
### 35: USMT_UNABLE_DELETE_STORE
@ -238,8 +236,8 @@ The following information lists each return code by numeric value, along with th
| 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. |
| **A reboot is required to remove the store** | Reboot to delete any files that couldn't 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 couldn't be deleted. If you're using a hardlink migration store, you might have a locked file in it. You should manually delete the store, or use `UsmtUtils.exe /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
@ -248,9 +246,9 @@ The following information lists each return code by numeric value, along with th
| 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. |
| **Compliance check failure; please check the logs for details** | Investigate whether there's an active temporary profile on the system. |
| **Use of /offline is not supported during apply** | The `/offline` command wasn't used while running in the Windows Preinstallation Environment (WinPE). |
| **Use /offline to run gather on this platform** | The `/offline` command wasn't used while running in WinPE. |
### 37: USMT_ERROR_NO_INVALID_KEY
@ -258,9 +256,7 @@ The following information lists each return code by numeric value, along with th
| Error message | Troubleshooting, mitigation, workarounds |
| --- | --- |
| **The store holds encrypted data but the correct encryption key was not provided** | Verify that you have included the correct encryption /key or /keyfile. |
- **Category**: Setup and Initialization
| **The store holds encrypted data but the correct encryption key was not provided** | Verify that the correct encryption key or keyfile was included with the `/key` or `/keyfile` option. |
### 38: USMT_ERROR_CORRUPTED_NOTENCRYPTED_STORE
@ -277,7 +273,7 @@ The following information lists each return code by numeric value, along with th
| 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. |
| **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
@ -285,8 +281,8 @@ The following information lists each return code by numeric value, along with th
| 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. |
| **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. |
| **Error writing to the progress log** | The Progress log couldn't be created. Verify that the location is valid and that you have write access. |
| **Progress log argument is invalid for /progress** | The Progress log couldn't be created. Verify that the location is valid and that you have write access. |
### 41: USMT_PREFLIGHT_FILE_CREATION_FAILED
@ -294,7 +290,7 @@ The following information lists each return code by numeric value, along with th
| 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. |
| **Can't overwrite existing file** | The Progress log couldn't 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. |
### 42: USMT_ERROR_CORRUPTED_STORE
@ -303,7 +299,7 @@ The following information lists each return code by numeric value, along with th
| Error message | The store contains one or more corrupted files |
| --- | --- |
| **The store holds encrypted data but the correct encryption key was not provided** | 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). |
| **The store holds encrypted data but the correct encryption key was not provided** | Review UsmtUtils log for details about the corrupted files. For information on how to extract the files that aren't corrupted, see [Extract files from a compressed USMT migration store](usmt-extract-files-from-a-compressed-migration-store.md). |
### 61: USMT_MIGRATION_STOPPED_NONFATAL
@ -322,7 +318,7 @@ The following information lists each return code by numeric value, along with th
| **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. |
| **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 sign in again with elevated privileges. |
### 72: USMT_UNABLE_DOMIGRATION
@ -336,7 +332,7 @@ The following information lists each return code by numeric value, along with th
| **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. |
## Related topics
## Related articles
[User State Migration Tool (USMT) troubleshooting](usmt-troubleshooting.md)