共用方式為

MDT 2010: Incorrect wimgapi.dll version causing WIM mounting issues

  • 發行項

Today’s blog will cover an issue we have seen with Microsoft Deployment Toolkit 2010.  You may see one or more of the following error messages when generating or updating boot images and other actions in MDT that involve the Lite Touch Images:

  • Unable to mount the WIM, so the update process cannot continue.
  • Unable to load DLL 'wimgapi.dll'
  • Mount did not succeed

You can also run into errors when Windows System Image Manager tries to catalog an image.  This issue can occur because we are finding an incorrect version of WIMGAPI.DLL first in the path

Steps to Resolve

At a command run the following command

Where wimgapi.dll

For the first location listed in the page verify that the .DLL Version is correct.  If MDT 2010 is installed on Windows 7 or Windows Server 2008 R2 you should see wimgapi.dll in two locations because it ships with the operating system and with the Windows Automated Installation Kit (WAIK). 

C:windowssystem32wimgapi.dll
C:program fileswindows imagingwimgapi.dll

Both versions should be 6.1.7600.16385.  The version could be later than this if any updates have shipped that replace this file at a later date

Notes: 

  • This issue can occur if you installed a beta version of the WAIK or System Center Configuration Manager (SCCM)
  • You may find other versions in locations like Program Files(X86) or other directories.
  • If MDT is installed on Windows XP or Windows Server 2003 wimgapi.dll should only be found in C:Program FilesWindows Imaging
  • The version of WIMGAPI.DLL may be updated in later releases of the Windows AIK or updates to Windows. 

Scott McArthur
Senior Support Escalation Engineer
Microsoft Enterprise Platforms Support

Comments

  • Anonymous
    January 01, 2003
    G'day,I had encountered this issue while trying to run MDT using my Domain User account (Slight over sight on my behalf).  I ran MDT as my Domain Admin account which allowed the boot image update to complete.Kind Regards
  • Anonymous
    March 27, 2011
    I have this issue but i my solution was clean my temp. %temp%
  • Anonymous
    May 30, 2013
    Old post, but command prompt and use, "where"?  I never heard of a "where" command.  Can you please elaborate?
  • Anonymous
    May 30, 2013
    Belay my last.  I thought this was for Windows XP.
  • Anonymous
    April 28, 2015
    Too bad... didn't help for me. neither did cleaning the %temp% folder. Any suggestions would be very welcome!