This article was previously published under Q312965
This article provides information to help you to troubleshoot issues with the User State Migration Tool (USMT) and the Files and Settings Transfer Wizard (FSTW).
To help you to troubleshoot issues with USMT or FSTW:
Note that the USMT tools only support the migration of domain user profiles, not those profiles that are in a workgroup.
If you are using Loadstate.exe, verify that:
Loadstate.exe is being run by a user who has local administrator access, but is not the user that is being migrated.
The user that is being migrated does not already have a profile on the target computer.
Examine the System Event logs, and obtain the exact error message and Event ID. In most cases, the event logs indicate why the tool is not working.
When you are using FSTW, review the Fastwiz.log log file. Look for errors towards the end of the log that may indicate the reason for the failure. In Windows XP, the Fastwiz.log log file is located in the c:\Documents and Settings\user name\Local Settings\Application Data folder. If the source operating system is not Windows XP, search for the log, and note that it is in %CSIDL_LOCAL_APPDATA% (but that is different on a different operating system).
Obtain operating system information about both sides, including version of Microsoft Internet Explorer, and any other relevant program versions that are running on the computers. The command line tool creates the log files (Scanstate.log and Loadstate.log) in the current folder.
Obtain the exact steps that are needed to reproduce the issue. This information may help you to better understand what specifically is wrong, and help you to reproduce the issue in your testing environment.
If you are using the command-line tools (USMT), run them with the /v 7 switch to create the most detailed log file.
The approximate total space that FSTW requires (in temporary area and on the destination drive), is approximately 4 times the size of the store that is used. It unpacks the store in the temporary area (the local fixed drive with the greatest amount of free disk space). The unpacked data is approximately 2 times the size of the store, based on a 50 percent compression ratio. After this, FSTW copies each file from the temporary area to the destination (without deleting the files from the temporary area). When this process completes, the temporary area is cleaned up.
NOTE: Loadstate.exe does not have this requirement.
It may take significant time to restore all of the data, especially if the store is large. At some points it may appear that the computer has stopped responding, or that the progress bar is no longer moving. You should give the migration enough time before you can safely assume that the process is actually not responding. There is a point (at about 40 to 50 percent in the progress bar) where, for big stores with lots of files, a long amount of time passes without activity in the progress bar. Be sure to look for drive activity to determine if the process has hung. If the process is not responding, try the operation again in a clean boot scenario by using the System Configuration Utility (Msconfig.exe) or in Safe mode.