Fix for Windows 7 deployments failing after upgrading to Windows ADK 10

If you upgraded your ConfigMgr 2012 R2 SP1 server to Windows 10 ADK, most likely to start testing Windows 10 deployments, you probably learned that some of the existing Windows 7 deployment no longer works. More specifically, it’s the computer refresh and computer replace scenarios that fails because an issue with loadstate on Windows 7 machines. The simple root cause is that loadstate requires additional files when run on Windows 7, files that are not in the default USMT package.

Disclaimer: This is not an official fix, and is probably not supported. This fix only works.

Update 2015-09-01: The official fix is here: (also about copy the files, but not all setup files).


Computer Refresh or Computer Replace to Windows 7 fails with the following error:

The program can’t start because DismApi.DLL is missing from your computer. Try reinstalling the program to fix this problem.

Task Sequence failing when deploying Windows 7.


The fix is easy, simply add the missing files to the USMT package in ConfigMgr 2012 R2 SP1. Either create a new package or add the missing files to the existing package.

If you want to update the default package, for x64 deployments, copy the entire contents of C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Setup\amd64\Sources to C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\User State Migration Tool\amd64 (Replace any existing files) Then update the package. Done!

Yep, select all files, it’s easier than trying to find out which ones that are needed for various USMT operations.

The amd64 folder of the USMT package, updated with the extra 126 MB of amd64 Windows Setup files. 133 MB in total.

Loadstate working again. 🙂

Happy Deployment, Johan

About the author

Johan Arwidmark

0 0 votes
Article Rating
Notify of
Inline Feedbacks
View all comments