Questions regarding User State Migration Tool.

---

Re: Migrate user data lab MD 100
Why can we ignore error code 61 when importing user kyoshida from Plabwin 810 to Plabwin10 using the loadstate command on Plabwin10? Also why do we use x when typing the net use command ? Is there a special reason ? Could we use any letter number or is there something special about x?Also, I was not able to finish the lab a few times I tried. It was not until I discovered that network discovery was off on both Plabwin10 and Plabdm02. When I changed all nodes to have network discovery on it. I was able to complete the lab successfully.

@Geo ,

Good questions.

The x used in the net use command is the drive letter assigned to the mapped drive. You are free to use any letter that is not in use already. One reason you see X used a lot, is it is very rarely in use, and it's easy to remember. FWIW, they don't have to be the same either. You could use x: to map the drive on the Win8 machine, and t: on the Win10 machine.

The error you are seeing is Error 5, which is an access denied error. The USMT is trying to modify the SpyNetReporting registry value, and it is failing. This reg key has to do with Windows Defender Cloud-delivery protection (whether it is enabled or not) setting. This setting cannot be modified through the registry directly, you must change the setting using the Windows Security Center. That is the reason for the access denied error (Error 5)

Loadstate is showing a return code of 61. This return code means there were non-fatal error(s). A non-fatal error means loadstate was able to finish (it didn't crash) but there was an error, so something might not have migrated successfully (in this case, the Spynet setting) The return code doesn't tell us what the error was, just that there was an error (Error 5 access denied on the reg key)

This error can be safely ignored because it's not a critical setting. If we had determined that the error was due to a failure of a critical setting, or if the error was fatal, we would troubleshoot the error and fix the issue. In this case, it wouldn't be worth the effort to try and fix the problem.

Here is a link to USMT return codes, if you are interested. You will find return code 61 towards the bottom of the list

https://docs.microsoft.com/en-us/windows/deployment/usmt/usmt-return-codes

Hope this helps,

@Mike-Rodrick Thank You, Mike.