none
WinPE-MDAC-Package Error: 0x80070005 RRS feed

  • Question

  • Hi,

    I received below error when I update Deployment Shared in MDT 2013.  It looks like the update completed and created new LiteTouchPE_x64.ISO and LiteTouchPE_x64.wim.  However, when I used VM to boot from this ISO, it stopped at X:\windows\system32 in command prompt.  Any idea?

    [===========================67.3%=======                   ] 
    [===========================69.5%========                  ] 
    [===========================71.7%=========                 ] 
    [===========================74.0%==========                ] 
    [===========================74.0%==========                ] 
    [==========================100.0%==========================] 
    An error occurred - WinPE-MDAC-Package Error: 0x80070005
    Error: 5
    Access is denied.
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    Exit code = 5
    DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\winpe-mdac.cab, rc = 5.
    Added component winpe-mdac
    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0
    Image Version: 10.0.10586.0
    Found 1 driver package(s) to install.
    Installing 1 of 1 - E:\MDT\Out-of-box Drivers\Net\Ax88772_3.10.3.13_3B1780F670228607377C2CE99F7C5B227CE5C2E3C34F59637D3289A906CFDCE6\Ax88772.inf: 
    INFO: DISM has skipped driver signature check because the version of running OS and that of target OS do not match.
    Error - An error occurred. The driver package could not be installed. 
    For more information, check for log files in the <windir>\inf folder of the target image.
    Error: 5
    Access is denied.
    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    Exit code = 5
    DISM /Add-Driver failed, rc = 5.
    Injected driver ASIX Net Ax88772.inf 3.10.3.13
    

    An error occurred - WinPE-MDAC-Package Error: 0x80070005
    Error: 5

    Thursday, April 28, 2016 10:59 PM

Answers

  • I figured out the problem. It is related to McAfee virus scan version I am running on my computer. It needs to update to newer version.

    Thanks,

    Brandon.

    Friday, April 29, 2016 1:42 AM