السؤال Dism has stopped working

  • Tuesday, February 05, 2013 10:15 AM
     
     

    Hello,

    i have a well working MDT environment.

    Only when starting dism manually from command-prompt :

    Is there an option for repairing DISM without uninstall of ADK?

    In the eventlog:

    Faulting application name: Dism.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc394

    Faulting module name: Dism.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc394

    Exception code: 0xc0000005

    Fault offset: 0x0000000000016ccc

    Faulting process id: 0x1d44

    Faulting application start time: 0x01ce038ae21327bb

    Faulting application path: C:\Windows\system32\Dism.exe

    Faulting module path: C:\Windows\system32\Dism.exe

    Report Id: 208595c7-6f7e-11e2-9eb8-0050569a0005

    Thx


    • Edited by Mvd12345 Tuesday, February 05, 2013 10:24 AM
    •  

All Replies

  • Wednesday, February 06, 2013 6:58 AM
     
     
    Anybody?
  • Wednesday, February 06, 2013 8:36 AM
     
     

    a quick google shows that it might have to do with the program trying to access memory it shouldn't and there for crashes Or some known windows problem.

    try this hotfix to see if that solves your problem i have no idea of it is related but the only thing i could find.

    the other thing you can always try offcourse is reinstalling ADK even though you don't want to you might have to.

  • Wednesday, February 06, 2013 10:26 AM
     
     

    I have tried the hotfix, without result.

    Is there way to replace/reinstall DISM without reinstall of ADK?

    Thx

  • Wednesday, February 06, 2013 10:32 AM
     
     

    not that i know off since it is part of the ADK.

    whats the problem though with reinstalling it though? it should be no problem.

  • Wednesday, February 06, 2013 10:42 AM
     
     

    I have just reinstalled the "deployment tools" part of ADK:

    but still the same error :


    • Edited by Mvd12345 Wednesday, February 06, 2013 10:42 AM
    •  
  • Wednesday, February 06, 2013 10:55 AM
     
     
    Problem solved by copying dism.exe from a working environment to c:\windows\system32