In a “simple” environment:
· For Windows Server 2008, Windows Server 2003, Windows Vista, and Windows XP, MDT locates WIMGAPI.DLL in C:\Program Files\Windows Imaging, which should be in the system PATH. WIMGAPI.DLL should not reside in C:\Windows\system32: It will be present in the C:\Program Files\Windows AIK directory tree, but MDT rarely uses it from that location.
· For Windows 7 and Windows Server 2008, MDT typically picks up WIMGAPI.DLL from C:\Windows\system32 (always in the path). The version of this WIMGAPI.DLL must match the version (build) of the operating system.
· On a 64-bit operating system, MDT always uses the x64 WIMGAPI.DLL file; only that file should be in the system PATH. On a 32-bit operating system, MDT always uses the x86 WIMGAPI.DLL file; only that file should be in the system PATH. (Other products, such as Configuration Manager, use the 32-bit version of WIMGAPI.DLL, even on a 64-bit operating system, but they manage and install that version.)
Problem: When attempting to update a deployment share, the user will be informed that the mounting of one or more .wim files did not succeed.
Possible Solution: Open a Command Prompt window and run where WIMGAPI.DLL. For the first entry in the list (the first location found by searching the path), ensure that the Version property matches the build of the Windows Automated Installation Kit (Windows AIK) that is installed. On Windows 7 or Windows Server 2008 R2 machines, ensure that the property also matches the operating system build number.