The following table lists each return code by numeric value, along with the associated error messages and suggested troubleshooting actions.
|
Return code value
|
Return code
|
Error message
|
Troubleshooting, mitigation, workarounds
|
Category
|
|
0
|
USMT_SUCCESS
|
Successful run
|
Not applicable
|
Success or Cancel
|
|
1
|
USMT_DISPLAY_HELP
|
Command line help requested
|
Not applicable
|
Success or Cancel
|
|
2
|
USMT_STATUS_CANCELED
|
User chose to cancel (such as pressing CTRL+C)
|
Not applicable
|
Success or Cancel
|
|
|
|
Gather was aborted because of an EFS file
|
Not applicable
|
|
|
11
|
USMT_INVALID_PARAMETERS
|
Undefined or incomplete command line option
|
Review ScanState log or LoadState log for details about command-line errors.
|
Invalid Command Lines
|
|
|
|
An option argument is missing
|
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.
|
|
|
|
|
The store parameter is required but not specified
|
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.
|
|
|
|
|
Command line arguments are required. Specify /? for options.
|
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.
|
|
|
|
|
The estimate output path is invalid for /p
|
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.
|
|
|
|
|
The source-to-target user account mapping is invalid for /mu
|
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.
|
|
|
|
|
User exclusion argument is invalid
|
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.
|
|
|
|
|
/all conflicts with /ui, /ue or /ue
|
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.
|
|
|
|
|
/key and /keyfile both specified
|
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.
|
|
|
|
|
/genconfig can't be used with most other options
|
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.
|
|
|
|
|
/genmigxml can't be used with most other options
|
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.
|
|
|
|
|
/key or /keyfile used without enabling encryption
|
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.
|
|
|
|
|
/offlinewindir requires a valid path to offline windows folder
|
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.
|
|
|
|
|
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.
|
|
|
|
|
Retry argument must be an integer
|
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.
|
|
|
|
|
The /targetxp option is only available for Windows XP
|
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.
|
|
|
|
|
List file path argument is invalid for /listfiles
|
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.
|
|
|
|
|
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.
|
|
|
|
|
/auto expects an optional parameter for the script folder
|
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.
|
|
|
|
|
Specified encryption algorithm is not supported
|
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.
|
|
|
12
|
USMT_ERROR_OPTION_PARAM_TOO_LARGE
|
Command line arguments cannot exceed 256 characters
|
Review ScanState log or LoadState log for details about command-line errors.
|
Invalid Command Lines
|
|
|
|
A store path exceeds MAX_PATH
|
Review ScanState log or LoadState log for details about command-line errors.
|
|
|
13
|
USMT_INIT_LOGFILE_FAILED
|
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.
|
Invalid Command Lines
|
|
14
|
USMT_ERROR_USE_LAC
|
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.
|
Invalid Command Lines
|
|
26
|
USMT_INIT_ERROR
|
Software malfunction or unknown exception
|
Check all loaded .xml files for errors, common error when using /I to load the Config.xml file.
|
Setup and Initialization
|
|
|
|
Multiple Windows installations found
|
Listfiles.txt could not be created. Verify that the location you specified for the creation of this file is valid.
|
|
|
|
|
Unable to find a valid Windows directory to proceed with requested offline operation \r\n\t
|
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
|
Invalid store path; check the store parameter and/or file system permissions
|
Make sure that the store path is accessible and that the proper permission levels are set.
|
Setup and Initialization
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
28
|
USMT_UNABLE_GET_SCRIPTFILES
|
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.
|
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
|
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.
|
Setup and Initialization
|
|
|
|
Migration failed because of an XML error; look in the log for specific details
|
Check the ScanState log file for migration .xml file errors.
|
|
|
|
|
Another process is preventing migration; only one migration tool can run at a time
|
Check the ScanState log file for migration .xml file errors.
|
|
|
|
|
Unable to automatically map the drive letters to match the online drive letter layout;\r\n\t
Use /offline to provide a mapping table
|
Check the ScanState log file for migration .xml file errors.
|
|
|
|
|
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.
|
|
|
31
|
USMT_UNABLE_FINDMIGUNITS
|
An error occurred during the discover phase; the log should have more specific information
|
Check the ScanState log file for migration .xml file errors.
|
Setup and Initialization
|
|
32
|
USMT_FAILED_SETMIGRATIONTYPE
|
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.
|
Setup and Initialization
|
|
33
|
USMT_UNABLE_READKEY
|
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.
|
Setup and Initialization
|
|
|
|
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
|
No rights to create user profiles
|
Log on as Administrator, and run with elevated privileges.
|
Setup and Initialization
|
|
35
|
USMT_UNABLE_DELETE_STORE
|
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.
|
Setup and Initialization
|
|
36
|
USMT_ERROR_UNSUPPORTED_PLATFORM
|
Compliance check failure; please check the logs for details
|
Investigate whether there is an active temporary profile on the system.
|
Setup and Initialization
|
|
|
|
Use /offline to run gather on this platform
|
The /offline command was not used while running in Windows PE.
|
|
|
|
|
Use of /offline is not supported during apply
|
The /offline command was not used while running in the Windows Preinstallation Environemtn (Windows PE).
|
|
|
37
|
USMT_ERROR_NO_INVALID_KEY
|
The store holds encrypted data but the correct encryption key was not provided
|
Verify that you have included the correct encryption /key or /keyfile.
|
Setup and Initialization
|
|
38
|
USMT_ERROR_CORRUPTED_NOTENCRYPTED_STORE
|
An error occurred during store access
|
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.
|
Setup and Initialization
|
|
39
|
USMT_UNABLE_TO_READ_CONFIG_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.
|
Setup and Initialization
|
|
|
|
Error reading Config.xml
|
Review ScanState log or LoadState log for details about command-line errors in the Config.xml file.
|
|
|
40
|
USMT_ERROR_UNABLE_CREATE_PROGRESS_LOG
|
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.
|
Setup and Initialization
|
|
|
|
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
|
Can't overwrite existing file
|
The Progress log could not be created. Verify that the location is valid and that you have write access.
|
Setup and Initialization
|
|
61
|
USMT_MIGRATION_STOPPED_NONFATAL
|
Processing stopped due to an I/O error
|
USMT exited but can continue with the /c command-line option, with the optional configurable <ErrorControl> section or by using the /vsc command-line option.
|
Non-fatal Errors
|
|
71
|
USMT_INIT_OPERATING_ENVIRONMENT_FAILED
|
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.
|
Fatal Errors
|
|
|
|
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.
|
|
|
72
|
USMT_UNABLE_DOMIGRATION
|
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.
|
Fatal Errors
|
|
|
|
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 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.
|
|
|
|
|
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.
|
|