locked
Failure (5627) : 10737415 0xC0000135: Run DISM.exe RRS feed

  • Question

  • Dear All , 

    Kindly Assist causing of failure when deploy OS , i googling but cannot find the solution. 



    Best Regards, Hussain


    • Edited by ErMIH Monday, January 2, 2017 1:26 PM rev
    Monday, January 2, 2017 1:25 PM

Answers

  • During the Install Phase, MDT will apply the OS image using the dism.exe command.

    Additionally, MDT will run the dism.exe /Apply-Unattend command to inject drivers and *.MSU packages into the image *BEFORE* it boots into the OS for the first time.

    Most likely you have a corrupt driver or package being applied. Try removing all the packages and try again.

    Additionally, the attached bdd.log file from basebin above is *NOT* the same error as you present above.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Friday, January 6, 2017 1:46 AM
  • Now you have a DIFFERENT problem than the one you originally documented in the first post.

    The problem now is that you have chosen to format your drive as GPT, but you have not created the correct portioning format, right now MDT is creating two NTFS partitions, and GPT requires the system partition to be of type FAT32.

    Please create a *NEW* task sequence from scratch, you can see from the new task sequence what the partitioning configuration should be.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, January 9, 2017 4:54 PM
  • For this *LATEST* problem, MDT is trying to write the OS image to the smaller System Partition.

    Most likely you didn't restore the "Format and PArtition Disk" step to *EXACTLY* the way it, *INCUDING* putting the correct "OSDisk" variable for the "boot" partition where the OS goes.

    you must match the variable in the boot partition on this step with the variable used in the "install OS" step. 


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, January 16, 2017 5:53 PM

All replies

  • If you want someone to help troubleshoot it would be more helpful if you upload your bdd.log and then post a link to it.

    If this post is helpful please vote it as Helpful or click Mark for answer.

    Tuesday, January 3, 2017 5:26 PM
  • That is covered in the FAQ

    https://social.technet.microsoft.com/Forums/en-US/67eca878-b180-485e-a6bf-f14ae63d0c8f/how-to-video-how-to-find-the-correct-mdt-logs-bddlog-and-smstslog?forum=mdt

    Upload the log to OneDrive, Box, DropBox, something like that and share the link to the log file.

    Are you still using an old version of MDT? Because ImageX is no longer used.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Wednesday, January 4, 2017 2:36 PM
  • No one reads the FAQ.

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.

    Thursday, January 5, 2017 12:51 AM
  • Dear Dan , 

    BDD.Log file uploaded with given below link.

    BDD.LOG


    Best Regards, Hussain

    Thursday, January 5, 2017 9:55 AM
  • I'd suggest one thing which would fix the problem I see. Upgrade to a newer version of MDT. When you do that you will need to create new task sequences. That right there should fix your problem.

    It looks like you have your format and partitioning set to use GPT. Windows 8, I believe, requires UEFI when using GPT.

    If you upgrade to a newer MDT and create new task sequences, do not modify the tasks to format and partition as MDT has all the logic it needs to automatically handle BIOS or UEFI.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, January 5, 2017 2:25 PM
  • During the Install Phase, MDT will apply the OS image using the dism.exe command.

    Additionally, MDT will run the dism.exe /Apply-Unattend command to inject drivers and *.MSU packages into the image *BEFORE* it boots into the OS for the first time.

    Most likely you have a corrupt driver or package being applied. Try removing all the packages and try again.

    Additionally, the attached bdd.log file from basebin above is *NOT* the same error as you present above.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Friday, January 6, 2017 1:46 AM
  • Dear All ,

    No Change Same Err even changed format disk to GPT.

    Kindly advise .


    Best Regards, Hussain


    • Edited by ErMIH Monday, January 9, 2017 5:04 AM re
    Monday, January 9, 2017 5:03 AM
  • Your reply has nothing to do with what Keith said.  Can you try what Keith said?

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.

    Monday, January 9, 2017 5:16 AM
  • If  i am not wrong ,Deleted all Package from above shown picture .  is it Mr.Keith concern ?

    Best Regards, Hussain

    • Edited by ErMIH Monday, January 9, 2017 6:25 AM leb
    Monday, January 9, 2017 5:32 AM
  • Dear All , 

    BDD.Log file uploaded here , And Err Same 

    BDD.LOG


    Best Regards, Hussain

    Monday, January 9, 2017 10:02 AM
  • Now you have a DIFFERENT problem than the one you originally documented in the first post.

    The problem now is that you have chosen to format your drive as GPT, but you have not created the correct portioning format, right now MDT is creating two NTFS partitions, and GPT requires the system partition to be of type FAT32.

    Please create a *NEW* task sequence from scratch, you can see from the new task sequence what the partitioning configuration should be.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, January 9, 2017 4:54 PM
  • I'd suggest one thing which would fix the problem I see. Upgrade to a newer version of MDT. When you do that you will need to create new task sequences. That right there should fix your problem.

    It looks like you have your format and partitioning set to use GPT. Windows 8, I believe, requires UEFI when using GPT.

    If you upgrade to a newer MDT and create new task sequences, do not modify the tasks to format and partition as MDT has all the logic it needs to automatically handle BIOS or UEFI.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    As I mentioned earlier, create a new task sequence and do not make changes to the pre-created Format and Partition Disk tasks. It should look like this


    If this post is helpful please vote it as Helpful or click Mark for answer.


    • Edited by Dan_Vega Monday, January 9, 2017 5:03 PM
    Monday, January 9, 2017 5:03 PM
  • There is no change 

    BDD Log Uploaded 

    https://drive.google.com/file/d/0ByCIJdruNVU0MVJEcC1UNDRfTlk/view?usp=sharing

    Kindly review and advise .


    Best Regards, Hussain

    Wednesday, January 11, 2017 5:14 AM
  • Correct, there is no change in the output, then again, you are using the SAME task sequence as you did last time. DP_TC_64

    We can not verify for you that you did in fact modify the Task Sequence correctly.

    If you are still having problems, copy the file \\EDU-FP-10063\DeploymentShareV2$\Control\DP_TC_64\ts.xml file to your gdrive and we can verify.

    Otherwise it's more than likely you did not modify the correct file, or did not run the correct Task Sequence.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Wednesday, January 11, 2017 5:50 AM
  • Dear Keith ,

    I apologize for inconvenience , you are right every time running same task sequence and its our issue due to different model (Toshiba / Lenova /DELL etc.) , and I created new task sequence for Lenova but my IT admin was try to image for  Toshiba however i instruct our IT admin to try with Lenova as i created new task sequence . I will update you once we test with correct model.

    For my knowledge why two task sequence running  DP_TC_64 / BC_TC_64


    Best Regards, Hussain

    Wednesday, January 11, 2017 6:37 AM
  • Dear I uploaded with different Err

    BDD Logs


    Best Regards, Hussain

    Monday, January 16, 2017 5:04 AM
  • For this *LATEST* problem, MDT is trying to write the OS image to the smaller System Partition.

    Most likely you didn't restore the "Format and PArtition Disk" step to *EXACTLY* the way it, *INCUDING* putting the correct "OSDisk" variable for the "boot" partition where the OS goes.

    you must match the variable in the boot partition on this step with the variable used in the "install OS" step. 


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Monday, January 16, 2017 5:53 PM
  • Kindly find attached here and suggest . This is the one i did and tested .  Err as last post BDD.LOg


    Best Regards, Hussain

    Monday, January 16, 2017 6:52 PM
  • Setting is wrong.

    In picture #2 (Partition Name EFI), the variable "OSDisk" should NOT Be set.

    "OSDisk" should be set in picture #4 (Partition name "Windows")


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Tuesday, January 17, 2017 12:10 AM
  • Dear Keith , 

    Thanks for your support , I did the same and No Err but After imaging not boot

    BDD.Log

    https://drive.google.com/open?id=0ByCIJdruNVU0MW1ic3VGTkFVUGM

    Kindly review and advise .


    Best Regards, Hussain

    Tuesday, January 17, 2017 6:12 AM
  • Try a default task sequence.  

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.

    Tuesday, January 17, 2017 8:08 AM
  • Hi , Anyone can suggest why initialization not working even there is no Err in BDD.Log file.

    After imaging computer not booting as you find from my last post . Kindly assist what wrong with my MDT. I am struggling since long time but so far issue not fix . 

     

    Best Regards, Hussain

    Wednesday, January 18, 2017 5:20 AM
  • Yes, the configuration is still wrong, the BCDEdit.exe command is being executed against the wrong partition.

    It's becoming a lot of effort to fix the old task sequence, Instead I would do as Ty recommends and start again with a clean task sequence.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Wednesday, January 18, 2017 5:33 AM