Follow by Email

Sunday, 11 October 2015

Windows 7 deployment fails during a computer refresh or replacement

 

image

Symptoms

Windows 7 deployment fails when you are refreshing or replacing a computer. In this situation, you may receive the following error message:

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

Cause

This problem occurs because of missing dependencies on the Loadstate.exe component on Windows 7-based computers.

Resolution

To fix this issue, use one of the following methods:

  • When you install the Windows Assessment and Deployment Kit (Windows ADK), select the Deployment Tools feature in addition to USMT. This will fix the issue.
  • If you can't install the Windows ADK on the system that's running Loadstate, install the Windows 10 ADK on another system (and make sure that you also install the Deployment Tools feature). Then, follow these steps:
    1. On the system that has ADK installed, you will see this folder:

      C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM

    2. Copy the following binaries from that folder to the folder that contains Loadstate.exe:
      • dismapi.dll
      • api-ms-win-downlevel-advapi32-l1-1-1.dll
      • api-ms-win-downlevel-kernel32-l1-1-0.dll
      • api-ms-win-downlevel-kernel32-l2-1-0.dll
      • api-ms-win-downlevel-ole32-l1-1-1.dll
      • api-ms-win-downlevel-user32-l1-1-1.dll
      • api-ms-win-downlevel-version-l1-1-0.dll
More information

For example, if you want to update the package for x64 deployments, copy the files in step 2 of the "Resolution" section from
C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Setup\amd64\Sources to the following folder:

C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\User State Migration Tool\amd64

Then, update the package.

 

Applies to

  • Windows 7 Enterprise
  • Windows 7 Professional
  • Windows 7 Ultimate

Refer to :-https://support.microsoft.com/en-us/kb/3084782

No comments:

Post a Comment