none
MDT Deploy W7 Failure 5627 RRS feed

  • Question

  • Hi,

    I have a task sequence that I cannot get Windows 7 deployed to a specific set of hardware: HP DM1-4300 series laptops.
    Windows 10 deploys fine, likewise with Windows 8/8.1. 
    I assume this is a driver (mass storage?) issue. I can install vanilla Windows 7 from a USB with the aid of a network driver, for which my captured image is based on.

    I have separate driver profiles (specific to device) as well as the boot images only contain drivers for WinPE (that could be different to what is injected during the Preinstall phase.

    Can anyone decipher the logs and point me in the right direction? Many Thanks.

    https://karamuschool-my.sharepoint.com/personal/mstrickland_karamu_school_nz/_layouts/15/guestaccess.aspx?folderid=04f30a6c1c5e54be281fc9fd8ecaa56fe&authkey=AagDmXIMAXKfSsQZq1WTsfA

    [FAILURE ( 5627 ): -2146498547  0x800F080D: Run DISM.exe]
    [Command completed, return code = -2147467259]
    [Litetouch deployment failed, Return Code = -2147467259  0x80004005]
    Sunday, September 17, 2017 10:36 PM

All replies

  • You are running into a DISM error:

        Console > Error: 0x800f080d
    Console > The DISM log file can be found at X:\WINDOWS\Logs\DISM\dism.log

    Could you pull the DISM log from X:\Windows\Logs\DISM?


    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Monday, September 18, 2017 7:11 AM
  • Hi Anton,

    I included the DISM.log in the link above/below (sorry cant hyperlink with this account)

    There are two, I think I grabbed one from X and one from C as they were different sizes.

    https://karamuschool-my.sharepoint.com/personal/mstrickland_karamu_school_nz/_layouts/15/guestaccess.aspx?folderid=04f30a6c1c5e54be281fc9fd8ecaa56fe&authkey=AagDmXIMAXKfSsQZq1WTsfA

    Regards,

    Matt

    Monday, September 18, 2017 7:54 AM
  • I am seeing numerous errors in the dism.log, for instance:

    2017-09-15 12:41:47, Info                  CBS    Failed to find a matching version for servicing stack: C:\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_0bfc08bf3ea166ba\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2017-09-15 12:41:47, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

    As far as I can see you are deploying Windows 7 x64 using x86 boot image, right? Aside from some issues surrounding Windows 7 and x86 WinPE, I would recommend to always use x64 boot images for x64 OS's unless you have a reason not to.

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Monday, September 18, 2017 9:16 AM
  • Hi Anton,

    I can post x64 logs tomorrow but was received the same error using either x86 or x64.

    My x86 WinPE boot image was based on vanilla 10.0.14393.0 and x64 on 10.0.15063.0
    (I have imported the Vanilla Windows 10 ISO's for creating boot images)

    Do I need to try downgrading x64 image version and try again, incompatibility?

    Matt

    Monday, September 18, 2017 10:11 AM
  • There is no need to downgrade, especially because you seem to experience same kind of issues with both x86 and x64 boot images.

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Monday, September 18, 2017 11:23 AM
  • Ok I re-ran the deployment using x64 boot image, dism a few warnings then errors related to packages, possibly just cascaded errors not related?: I will try with packages disabled (IE11 and netfx3)

    2017-09-19 08:14:03, Warning               DISM   DISM OS Provider: PID=160 Unable to copy msxml6.dll from the client executable folder to the dismhost.exe folder. Relying on in-box version. - CDISMOSServiceManager::RunASICompatibilityShim
    2017-09-19 08:14:11, Warning               DISM   DISM Provider Store: PID=160 Failed to Load the provider: C:\MININT\Scratch\C5255562-9F8C-4A83-BE80-ED9B700DE8DE\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2017-09-19 08:14:12, Info                  CBS    Failed to parse the manifest from the buffer. [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2017-09-19 08:14:12, Error                 CBS    Failed to parse package manifest: \\?\C:\MININT\Scratch\3A71433E-985E-4FBC-9766-E1BBDCFFF5AC\update.mum [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2017-09-19 08:14:12, Info                  CBS    Failed to initialize internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2017-09-19 08:14:12, Error                 CBS    Failed to create internal package [HRESULT = 0x800f080d - CBS_E_MANIFEST_INVALID_ITEM]
    2017-09-19 08:14:12, Error                 DISM   DISM Package Manager: PID=160 Failed opening package. - CDISMPackageManager::Internal_CreatePackageByPath(hr:0x800f080d)
    2017-09-19 08:14:12, Error                 DISM   DISM Package Manager: PID=160 Failed to get the underlying CBS package. - CDISMPackageManager::OpenPackageByPath(hr:0x800f080d)
    2017-09-19 08:14:12, Error                 DISM   DISM Package Manager: PID=160 Failed to open package at location [\\10.1.1.31\Deploy$\Packages\OnDemandPack\amd64_Microsoft-Windows-NetFx3-OnDemand-Package_10.0.15063.0_neutral_31bf3856ad364e35_\microsoft-windows-netfx3-ondemand-package.cab]. - CPackageManagerUnattendHandler::Internal_InstallPackageFromSource(hr:0x800f080d)
    2017-09-19 08:14:12, Error                 DISM   DISM Package Manager: PID=160 Failed to install package from source [0] - trying next source location. hr = [0x800F080D] - CPackageManagerUnattendHandler::Internal_UnattendInstallPackage
    2017-09-19 08:14:12, Error                 DISM   DISM Package Manager: PID=160 Failed to Install the package [Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~10.0.15063.0]. - CPackageManagerUnattendHandler::Internal_UnattendInstallPackage(hr:0x800f080d)
    2017-09-19 08:14:12, Error                 DISM   DISM Package Manager: PID=160 Package failed to install [Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~~10.0.15063.0]. - CPackageManagerUnattendHandler::Internal_UnattendProcessPackage(hr:0x800f080d)
    2017-09-19 08:14:12, Error                 DISM   DISM Package Manager: PID=160 Failed to process package at node <package[0]>. - CPackageManagerUnattendHandler::Apply(hr:0x800f080d)
    2017-09-19 08:14:12, Error                 DISM   DISM Package Manager: PID=160 Failed to Apply the unattend. - CDISMPackageManager::Apply(hr:0x800f080d)
    2017-09-19 08:14:12, Error                 DISM   DISM Unattend Manager: PID=160 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:400 - CUnattendManager::Apply(hr:0x800f080d)
    2017-09-19 08:14:12, Error                 DISM   DISM Unattend Manager: PID=160 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:654 - CUnattendManager::InternalExecuteCmdLine(hr:0x800f080d)
    2017-09-19 08:14:12, Error                 DISM   DISM Unattend Manager: PID=160 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:603 - CUnattendManager::ExecuteCmdLine(hr:0x800f080d)
    2017-09-19 08:14:12, Error                 DISM   DISM.EXE: DISM Unattend Manager processed the command line but failed. HRESULT=800F080D
    2017-09-19 08:14:12, Info                  DISM   DISM Image Session: PID=160 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
    2017-09-19 08:14:12, Info                  DISM   DISM Provider Store: PID=160 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider

    Regards,

    Matt

    Monday, September 18, 2017 9:41 PM
  • Ok disabling packages works, currently in OOBE and installing software.

    But why are packages failing on this hardware/OS?
    I can post more logs if required.

    Matt


    Monday, September 18, 2017 10:51 PM
  • Just out of curiosity, where did you disable the packages?

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Tuesday, September 19, 2017 5:46 AM
  • Sure in Deployment Workbench > Deploy Share > Packages.

    dotnet framework 3 (both x86 and x64)
    ie11 x64

    Usually I don't include optional features in offline images and add those during the task sequence.
    (works for every other deployment, minus this single one using w7 on this hardware)

    Matt

    Tuesday, September 19, 2017 6:08 AM