Verify the Condition of a Compressed Migration Store

Updated: May 31, 2012

Applies To: Windows 8, Windows 8.1

When you migrate files and settings during a typical PC-refresh migration, the user state is usually stored in a compressed folder on the intermediate store. This compressed folder, also called the compressed migration store, is a single image file that contains:

  • All of the files being migrated.

  • The user’s settings.

  • A catalog file that contains metadata for all files in the migration store.

When you run the LoadState command to load the data from these files to the destination computer, LoadState requires a valid catalog file in order to open the migration store. You can run the UsmtUtils command with the /verify option to determine whether the compressed migration store is intact, or whether it contains corrupted files or a corrupted catalog. You should run the /verify option on the migration store before you overwrite the original user-state files and settings.

When you use the /verify option, you can specify what type of information to report in the UsmtUtils log file. These report types are:

  • Catalog: Displays the status of only the catalog file.

  • All: Displays the status of all files, including the catalog file.

  • Failure only: Displays only the files that are corrupted.

The following sections demonstrate how to run the UsmtUtils command with the /verify option, and how to specify the information to display in the UsmtUtils log file.

To verify the condition of a compressed migration store, use the following UsmtUtils syntax:

cd /d<USMTpath>usmtutils /verify[:<reportType>] <filePath> [/l:<logfile>] [/decrypt [:<AlgID>] {/key:<keystring> | /keyfile:<filename>}]

Where the placeholders have the following values:

  • <USMTpath> is the location where you have saved the USMT files and tools.

  • <reportType> specifies whether to report on all files, corrupted files only, or the status of the catalog.

  • <filePath> is the location of the compressed migration store.

  • <logfile> is the location and name of the log file.

  • <AlgID> is the cryptographic algorithm that was used to create the migration store on the ScanState command line.

  • <keystring> is the encryption key that was used to encrypt the migration store.

  • <filename> is the location and name of the text file that contains the encryption key.

To verify whether the migration store is intact or whether it contains corrupted files or a corrupted catalog, type:

usmtutils /verify D:\MyMigrationStore\store.mig

Because no report type is specified, UsmtUtils displays the default summary report.

To verify whether the catalog file is corrupted or intact, type:

usmtutils /verify:catalog D:\MyMigrationStore\store.mig

To verify whether there are any corrupted files in the compressed migration store, and to specify the name and location of the log file, type:

usmtutils /verify:all D:\MyMigrationStore\store.mig /decrypt /l:D:\UsmtUtilsLog.txt

In addition to verifying the status of all files, this example decrypts the files. Because no encryption algorithm is specified, UsmtUtils uses the default 3DES cryptographic algorithm.

In this example, the log file will only list the files that became corrupted during the ScanState process. This list will include the catalog file if it is also corrupted.

usmtutils /verify:failureonly D:\MyMigrationStore\USMT\store.mig /decrypt:AES_192 /keyfile:D:\encryptionKey.txt

This example also decrypts the files by specifying the cryptographic algorithm and the location of the file that contains the encryption key.

If the /verify option indicates that there are corrupted files in the migration store, you can use the /extract option in the UsmtUtils tool to recover data from some corrupted stores. For more information, see Extract Files from a Compressed USMT Migration Store.

See Also


Return Codes


UsmtUtils Syntax