Unable to mount the WIM, so the update process cannot continue.

Answered Unable to mount the WIM, so the update process cannot continue.

  • Thursday, September 06, 2012 6:28 AM
     
     

    Hi , I am getting this error message when I try to update deployment share for AMD x64. I have MDT in a separate server and WDS in separate server. once the WIM is updated , I map the other server and update the boot image to the WDS to deployment.

    This  is the error message.

    === Making sure the deployment share has the latest x86 tools ===

    === Processing LiteTouchPE (x86) boot image ===

    Building requested boot image profile.
    Determining if any changes have been made in the boot image configuration.
    Loading the existing boot image profile for platform x86.
    Calculating hashes for requested content.
    Changes have been made, boot image will be updated.
    Windows PE WIM D:\Deployment Shares\AMD\Boot\LiteTouchPE_x86.wim will be used.
    Unable to mount the WIM, so the update process cannot continue.

    === Completed processing platform x86 ===

    === Making sure the deployment share has the latest x64 tools ===

    === Processing Generic (x64) boot image ===

    Building requested boot image profile.
    Determining if any changes have been made in the boot image configuration.
    Loading the existing boot image profile for platform x64.
    Calculating hashes for requested content.
    Changes have been made, boot image will be updated.
    Windows PE WIM D:\Deployment Shares\AMD\Boot\Generic_x64.wim will be used.
    Unable to mount the WIM, so the update process cannot continue.

    === Processing LiteTouchPE (x64) boot image ===

    Building requested boot image profile.
    Determining if any changes have been made in the boot image configuration.
    Loading the existing boot image profile for platform x64.
    Calculating hashes for requested content.
    Changes have been made, boot image will be updated.
    Windows PE WIM D:\Deployment Shares\AMD\Boot\LiteTouchPE_x64.wim will be used.
    Unable to mount the WIM, so the update process cannot continue.

    === Completed processing platform x64 ===


    === Processing complete ===

    Please help,

    Thanks

All Replies

  • Friday, September 07, 2012 2:32 PM
     
     
    I encountered the problem once and that was when I use to update the deployment share with the option "Optimize the boot image updating process." Can you try using the option "Completely regenerate the boot images." That is my only choice now to ensure nothing is left behind. Don't forget to update WDS with the new boot images.

    Please remember to click “Mark as Answer” on the post that helps you. This can be beneficial to other community members reading the thread.

  • Friday, September 07, 2012 6:45 PM
     
     Answered
    Try and mount the wim manually with imagex. If you get an error with access denied or file not found then it is most likely a antivirus program blocking the access. Last time I had this issue I uninstalled Checkpoint VPN, SuperAntiSpyware and Malwarebytes.
    • Marked As Answer by snrrk Monday, September 10, 2012 1:15 AM
    •  
  • Sunday, September 09, 2012 9:49 AM
     
     
    Please check if any policy blocking the permission to mount the image.
  • Wednesday, September 12, 2012 2:31 AM
     
     

     Thanks every one, 

    I have un installed antivirus and updated the deployment share. But after deployment, when I deploy I am getting the error...

    "ZTI Error - Unhandeled Error returned by LTIApply: the subsystem needed to support the image type is not present"

    Any clue to help me out in this ??

    Many thanks,

  • Wednesday, September 12, 2012 6:31 AM
     
     

     Thanks every one, 

    I have un installed antivirus and updated the deployment share. But after deployment, when I deploy I am getting the error...

    "ZTI Error - Unhandeled Error returned by LTIApply: the subsystem needed to support the image type is not present"

    Any clue to help me out in this ??

    Many thanks,


    You are missing the setup files for the correct arch you're in. In MDT workbench; Import a full set of Windows source files for the WinPe arch your are booting from.
  • Wednesday, September 12, 2012 6:06 PM
     
     
    I too am having this error. This is a fresh server 08 box with nothing else running on it, checked all the listed responses and I'm still having that issue. when I try to mount it using imagex I get the error "windows sim was unable to generate a catalog. Details: a required privilege is not held by the client" 
  • Thursday, September 13, 2012 7:18 AM
     
     

    Hi,

    I replaced the OS completely and updated. Now I found the x86 wim file is bigger than the x64 bit...

    Any clue?

  • Thursday, September 13, 2012 9:18 AM
     
     

    Hi,

    I replaced the OS completely and updated. Now I found the x86 wim file is bigger than the x64 bit...

    Any clue?

    Is it the WinPe you're refering too?

    It could be that you have more drivers injected in the x86 than the x64.

    It could be that you are using Windows AIK for one WinPe and Windows 7 RTM for the other.

    It could be that you have selected to integrate Dart or some other component for x86 but not for x64.

    Do a complete rebuild of WinPe. Then check the output to see what is different.

  • Thursday, January 10, 2013 7:52 AM
     
     

    Hi,

    had exactly the same problem!

    Check privillages,

    had the same problem after a lockdown ran:

    ntrights.exe -u "Administrators" -r SeChangeNotifyPrivilege

    changed it back by running:

    ntrights.exe -u "Administrators" +r SeChangeNotifyPrivilege

    Chris