Windows 10: Unable to use USMT scanstate.exe on Windows 10 2004 build

I am trying to use the USMT tool to migrate a user from a local user profile over to a domain profile on the same local machine however I have become somewhat stuck at the first hurdle when trying to run the scanstate.exe command, the below error is being returned to me;



SCANSTATE.EXE Version 10.0.19041

C 2012 Microsoft Corporation. All rights reserved.



Log messages are being sent to 'C:\Program Files x86\Windows Kits\10\Assessment and Deployment Kit\User State Migration Tool\x86\scanstate.log'



Running 32-Bit process on a 64-Bit system is not supported.



Failed.

Compliance check failure; please check the logs for details



ScanState return code: 36



I was originally doing my testing for using USMT to complete this task on VM's on my Hyper-V infrastructure to understand whether this may be an issue with running the migration on VM's however I get the same results on a Windows 10 2004 physical machine as well.


Could you please advise how to resolve as I have over 200 windows 10 client machines which need to be joined to our corporate domain and local user profiles migrated to their new domain profiles?

:)

 

USMT user migration

I am having a little trouble getting a user migration to complete successfully. I am trying to upgrade a PC from Windows 10 pro (build 1607) x86 to x64. I understand and have no problem with installing the
x64 version and applications from scratch. My problem is getting all the user info migrated over. I learned the hard way that Windows 10 does not have the Easy Transfer Tool, so I am forced to use the USMT found in Windows AIK for windows 10.

I have used the USMT once before and it was not pretty to say the least. Is there anything out there that can guide me through the process of running USMT successfully or can anyone help? Last time I tried
to use it, nothing worked for me. This time, I kept getting loadstate return code 11 or 71. Per technet, I know
code 11 is invalid parameters and code 71 has to do with operating environment. Both have multiple possibilities and I am not sure how to . I believe I used the correct syntax. The commands I used
are as follows. I added general output status and return codes.

No logs are created.






I am working on a domain admin account, Migration store has full admin permissions and the new install is a domain member with all apps installed with only domain and local admin accounts when I tried to load
the user info.

Any ideas what may be going wrong?

Edit: screen shot added

 

USMT 10 - issues with profile when migrating from Win7 to Win10


Hello,

Has anyone used USMT 10 to migrate from Win7 to Win10?


I have used USMT successfully in the past to move WinXP (32-bit) to Win7 Pro (64-bit). I downloaded the new ADK to get the v10 tools. I now have USMT 10 and was practicing the migration of Win7 Pro 64-bit users to Win10 Enterprise 64-bit. Just for completeness, I also tried Win7 Enterprise 64-bit -> USMT -> Win10 Enterprise 64-bit. The results were the same.

I have used the original MIG XML files previously and they did what I needed, so I intended to do the same here. My XML files are unmodified at this point, but I tried with a few modifications aimed at not bringing over Start Menu (shared & user specific) *.LNK files.I have had this failure with both the "no LNK files" and stock XML versions. I tested and the migration logs (scanstate and loadstate) both claim no error in the migration process. Reviewing the logs I see no critical errors or warnings.

The problem is that following the migration, the profiles that were migrated cannot use Start Menu, Cortana/Search, Notification Area (Action Center), or right click any icon pinned to the Taskbar. SearchUI.exe appears to not be running when I review Task Manager -> Details. Cortana is not listed under Processes.

A new user - someone who logs on without a migrated profile - is created properly and they work normally. Existing users - the tech profile that existed prior to the migration - work fine. It is only a failure within the migrated profiles. I have tried the suggested Start Menu repair actions (the Get-AppXPackage / AppXManifest.xml process) and multiple other suggestions. Nothing seems to repair this, and since I can create a new profile successfully or use a non-migrated existing profile, I have to believe it's a flaw in what I'm doing with USMT.


My scanstate script is: scanstate.exe \\system\migration_folder /i:migapp.xml /i:migdocs.xml /o /uel:90 /l:C:\scanstate.log /v:13

My loadstate script is: loadstate.exe \\system\migration_folder /i:migapp.xml /i:c:\intel\usmtfiles\miguser.xml /l:C:\loadstatelog /v:13

 

Windows 10 new Reset feature ?

Hi


MSDN page suggests that

Source : Deploy push-button reset features using ScanState (Windows Drivers)