none
OSD Windows 7 TS Failing Applying Driver Package / SCCM 1606 / ADK 1607 RRS feed

  • Question

  • Ever since upgrading to the current branch we have had issues with applying the driver packages for our Windows 7 laptops. What I've learned is our old boot image (ADK 1511) still works.  We are not experiencing any issues with our Windows 8.1 and 10 task sequences though.  Even more strange is on our desktops (M93P, M900) we do not have any issues running this specific Windows 7 task sequence.  So we are only having these problems on our laptops running Windows 7.  

    I am getting these errors on on our Lenovo ThinkPad series laptops running legacy bios mode (see below).  

    What we are currently running:

    • SCCM Current Branch 1606
    • Windows ADK 1607 (10.1.14393.0) 
    • MDT 2013 Update 2
    • Windows Server 2012 R2 Standard

    SMSTS.LOG

    <![LOG[Dism failed with return code -2147467259]LOG]!><time="13:51:34.475+300" date="08-26-2016" component="OSDDriverClient" context="" type="3" thread="628" file="sysprepdriverinstaller.cpp:548">
    <![LOG[AddPnPDriverToStore( pszSource, sTargetSystemDrive, sTargetSystemRoot, wProcessorArchitecture), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,658)]LOG]!><time="13:51:34.475+300" date="08-26-2016" component="OSDDriverClient" context="" type="0" thread="628" file="sysprepdriverinstaller.cpp:658">
    <![LOG[Failed to add driver to driver store. Code 0x80004005]LOG]!><time="13:51:34.475+300" date="08-26-2016" component="OSDDriverClient" context="" type="3" thread="628" file="sysprepdriverinstaller.cpp:658">
    <![LOG[InstallDriver( iInstallParams->sContentId, iInstallParams->sSource, iInstallParams->pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,557)]LOG]!><time="13:51:34.475+300" date="08-26-2016" component="OSDDriverClient" context="" type="0" thread="628" file="driverinstaller.cpp:557">
    <![LOG[ReleaseSource() for D:\_SMSTaskSequence\Packages\P010014D.]LOG]!><time="13:51:34.475+300" date="08-26-2016" component="OSDDriverClient" context="" type="1" thread="628" file="resolvesource.cpp:3880">
    <![LOG[reference count 1 for the source D:\_SMSTaskSequence\Packages\P010014D before releasing]LOG]!><time="13:51:34.475+300" date="08-26-2016" component="OSDDriverClient" context="" type="1" thread="628" file="resolvesource.cpp:3890">
    <![LOG[Released the resolved source D:\_SMSTaskSequence\Packages\P010014D]LOG]!><time="13:51:34.475+300" date="08-26-2016" component="OSDDriverClient" context="" type="1" thread="628" file="resolvesource.cpp:3928">
    <![LOG[pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,380)]LOG]!><time="13:51:34.475+300" date="08-26-2016" component="OSDDriverClient" context="" type="0" thread="628" file="osddriverclient.cpp:380">
    <![LOG[Failed to provision driver. Code 0x80004005]LOG]!><time="13:51:34.475+300" date="08-26-2016" component="OSDDriverClient" context="" type="3" thread="628" file="osddriverclient.cpp:380">
    <![LOG[Exiting with return code 0x80004005]LOG]!><time="13:51:34.475+300" date="08-26-2016" component="OSDDriverClient" context="" type="1" thread="628" file="osddriverclient.cpp:418">
    <![LOG[Process completed with exit code 2147500037]LOG]!><time="13:51:34.490+300" date="08-26-2016" component="TSManager" context="" type="1" thread="1380" file="commandline.cpp:1124">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="13:51:34.490+300" date="08-26-2016" component="TSManager" context="" type="1" thread="1380" file="instruction.cxx:814">
    <![LOG[Failed to run the action: Lenovo_T460s_w7_x64_R03. 
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="13:51:34.490+300" date="08-26-2016" component="TSManager" context="" type="3" thread="1380" file="instruction.cxx:921">

    dism.log:

    2016-08-26 13:51:34, Warning               DISM   DISM Provider Store: PID=368 Failed to retrieve the Provider Instance. - CDISMProviderStore::Internal_GetProvider(hr:0x80004005)

    2016-08-26 13:51:34, Error                 DISM   DISM Unattend Manager: PID=368 d:\win7sp1_gdr\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:654 - CUnattendManager::InternalExecuteCmdLine(hr:0x80004005)

    2016-08-26 13:51:34, Error                 DISM   DISM Unattend Manager: PID=368 d:\win7sp1_gdr\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:603 - CUnattendManager::ExecuteCmdLine(hr:0x80004005)

    2016-08-26 13:51:34, Error                 DISM   DISM.EXE: DISM Unattend Manager processed the command line but failed. HRESULT=80004005

    I've already attempted to recreate our driver packages that fail.  Any help is appreciated.  Thanks!

    Mike


    Friday, August 26, 2016 7:18 PM

Answers

  • Hi all,

    I ended up performing a rollback to ADK 1511 (10.1.10586.0) until Microsoft have resolved this issue, I logged a call with them and they are confirming this is now a known-error with this version of ADK on Windows 7 clients. 

    I found using the old boot images Windows 7 OSD was extremely slow.

    I'd suggest if there's no immediate reason(s) to upgrade to ADK 1607 then use version 1511  (10.1.10586.0) for now.

    Regards,

    Craig


    MCTS | MCITP | MCSA

    • Proposed as answer by Toffeenose81 Friday, October 14, 2016 9:41 AM
    • Unproposed as answer by Mike Snodgrass Thursday, October 20, 2016 8:47 PM
    • Marked as answer by Mike Snodgrass Thursday, October 20, 2016 8:50 PM
    Friday, September 23, 2016 8:20 AM

All replies

  • Hi,

    It sounds like it could be a bug or something similar, the ADK 1607 is not supported yet to use with Configuration Manager, there is no support statement released yet. And it sounds like there could be an issue with Windows 7 drivers...

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    • Proposed as answer by Kamala kannan.c Saturday, August 27, 2016 11:16 AM
    • Marked as answer by Mike Snodgrass Monday, August 29, 2016 6:32 PM
    • Unmarked as answer by Mike Snodgrass Thursday, October 20, 2016 8:46 PM
    • Unproposed as answer by Mike Snodgrass Thursday, October 20, 2016 8:46 PM
    Saturday, August 27, 2016 6:34 AM
  • Yes it could be a bug, it's a little bit confusing at the moment regarding this:

    https://social.technet.microsoft.com/Forums/en-US/939abe6e-35d0-4cf6-8c10-76c8674f207f/sccm-1602-with-win10-1607-task-sequence?forum=ConfigMgrCBOSD

    There was a "Yes" of Aaron Czechowski but not an official statement.

    Saturday, August 27, 2016 8:23 AM
  • Hi,

        Concur with Jörgen. I think the best way for you now is continue to use the old boot images until there're some public blogs/documentation from Microsoft announcing that it is supported to use with ConfigMgr.

    Best regards,

    Jimmy


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 29, 2016 7:27 AM
    Moderator
  • Agreed, a friend reminded me about this little workaround back in the CM07 days...

    Run Command Line in TS:

    dism.exe /Image:%OSDisk%\ /Add-Driver /Driver:. /Recurse

    Will hope that the announcement comes soon.  


    • Proposed as answer by Toffeenose81 Friday, October 14, 2016 9:42 AM
    Monday, August 29, 2016 6:45 PM
  • Hi Mike,

    Did you figure out what the problem was? I have the same issue with dism fails when applying device drivers on my windows 7 deployments. My windows 10 deployment works fine. If I choose the old boot image (The first v10 adk 1507). Then it works.

    My setup:

    Server 2012 R2
    SCCM 1606 (With hotfix)
    ADK 1607

    Thanks

    Regards

    Claus

    Thursday, September 15, 2016 3:49 PM
  • Hi all,

    Yes same problem here to, did you figure out the issue?

    Regards,

    Craig


    MCTS | MCITP | MCSA

    Monday, September 19, 2016 2:15 PM
  • I haven't had time to phone Microsoft yet and the workaround using dism I'm starting to like even more than the Driver Store, but hope to get ahold of them soon.  

    Monday, September 19, 2016 2:18 PM
  • The DISM Workaround could be done in this way:

    https://www.windows-noob.com/forums/topic/10856-sccm-2012-osd-apply-driver-packages-without-importing-them-to-the-database/

    • Proposed as answer by Toffeenose81 Friday, October 14, 2016 9:42 AM
    Monday, September 19, 2016 4:27 PM
  • Thanks - I'm using the previous boot images for now. I've logged with Microsoft premium support and on connect.

    I'll keep you posted

    Regards,

    Craig


    MCTS | MCITP | MCSA

    Tuesday, September 20, 2016 8:02 AM
  • Cool. Thanks.

    I'm also using a previous boot image until there is a fix for this issue.

    Regards

    Claus

    Wednesday, September 21, 2016 11:21 AM
  • Please remind me, if I uninstall previous ADK and install this ADK 1607, will my previous boot image be gone?
    Wednesday, September 21, 2016 5:39 PM
  • No your boot images within ConfigMgr will still be there.  If I remember right as well the default boot images get updated, so make sure the boot image you want to use isn't the default boot images.

    Wednesday, September 21, 2016 5:43 PM
  • I submitted a case to support.  I'll let you know what I find however I'd imagine they'll just say it is a known bug and look for a future update to the ADK shortly...hopefully.   We will see. 
    Wednesday, September 21, 2016 8:02 PM
  • I am too having this issue. SCCM version 1606. Applying driver packages fails. ADK Version 1602. Not sure if using ADK 1607 will work. If anyone has a boot image in which this works for now I would appreciate you sharing.

    Em


    • Edited by Gremlin78 Thursday, September 22, 2016 11:24 PM
    Thursday, September 22, 2016 11:23 PM
  • The default boot images dosent get updated. You have to run a powershell script to update them.

    /Claus

    Friday, September 23, 2016 6:12 AM
  • Can you share the script?
    Friday, September 23, 2016 8:16 AM
  • Hi all,

    I ended up performing a rollback to ADK 1511 (10.1.10586.0) until Microsoft have resolved this issue, I logged a call with them and they are confirming this is now a known-error with this version of ADK on Windows 7 clients. 

    I found using the old boot images Windows 7 OSD was extremely slow.

    I'd suggest if there's no immediate reason(s) to upgrade to ADK 1607 then use version 1511  (10.1.10586.0) for now.

    Regards,

    Craig


    MCTS | MCITP | MCSA

    • Proposed as answer by Toffeenose81 Friday, October 14, 2016 9:41 AM
    • Unproposed as answer by Mike Snodgrass Thursday, October 20, 2016 8:47 PM
    • Marked as answer by Mike Snodgrass Thursday, October 20, 2016 8:50 PM
    Friday, September 23, 2016 8:20 AM
  • See this post:

    https://blogs.technet.microsoft.com/enterprisemobility/2016/09/09/configuration-manager-and-the-windows-adk-for-windows-10-version-1607/

    Script:

    https://gallery.technet.microsoft.com/RegenerateBootImageWinPE10-f508f1e4

    /Claus

    Saturday, September 24, 2016 8:33 AM
  • Hi Graig,

    Have you heard any news regarding this issue?

    Thanks

    Regards

    Claus

    Wednesday, October 12, 2016 10:55 AM
  • Hi Claus,

    Sorry for the late reply, been one of those weeks here! ;-)

    Nothing yet, as soon as I hear anything I'll update this thread.

    Regards,

    Craig


    MCTS | MCITP | MCSA

    Friday, October 14, 2016 9:43 AM
  • I'd suggest if there's no immediate reason(s) to upgrade to ADK 1607 then use version 1511  (10.1.10586.0) for now.


    MCTS | MCITP | MCSA

    Old boot images, 1507 and 1511, does stretch gui resolution in UEFI mode. This affects UDI usage. I wish there would be a fix soon for 1607 boot image, so we could see, if this bug is fixed in 1607.
    Monday, November 7, 2016 11:43 AM
  • I have seen this problem on 2 different customers now running CM 1606

    The issue occurs with deploying Windows7 x86 or x64 with latest ADK 1607 as boot.. Rollback to MDT2013U2 bootimage based upon win10RTM seems to work

    The BootImage is MDT integrated in ConfigMgr

    The task sequence execution engine failed executing the action (Apply Driver Package - Precision 3510) in the group (Dell Precision 3510) with the error code 2147500037  Action output: ... pdriverinstaller.cpp,548) AddPnPDriverToStore( pszSource, sTargetSystemDrive, sTargetSystemRoot, wProcessorArchitecture), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,658) InstallDriver( iInstallParams->sContentId, iInstallParams->sSource, iInstallParams->pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,557) ReleaseSource() for D:\_SMSTaskSequence\Packages\XXX00275. reference count 1 for the source D:\_SMSTaskSequence\Packages\XXX00275 before releasing Released the resolved source D:\_SMSTaskSequence\Packages\XXX00275 pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,380) Exiting with return code 0x80004005 Dism failed with return code -2147467259 Failed to add driver to driver store. Code 0x80004005 Failed to provision driver. Code 0x80004005. The operating system reported error 2147500037: Unspecified error  

    errors in dism.log

    DISM   DISM Provider Store: PID=1440 Failed to retrieve the Provider Instance. - CDISMProviderStore::Internal_GetProvider(hr:0x80004005)

    DISM   DISM Unattend Manager: PID=1440 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:390 - CUnattendManager::Apply(hr:0x80004005)

    DISM   DISM Unattend Manager: PID=1440 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:603 - CUnattendManager::ExecuteCmdLine(hr:0x80004005)

    DISM   DISM Unattend Manager: PID=1440 d:\w7rtm\base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:654 - CUnattendManager::InternalExecuteCmdLine(hr:0x80004005)

     DISM   DISM.EXE: DISM Unattend Manager processed the command line but failed. HRESULT=80004005

    // Daniel


    Wednesday, November 16, 2016 1:49 PM
  • I am using "Create boot image using MDT" option. No problem at all applying driver packages for Windows 7 or Windows 10.

    SCCM 1606, ADK 1607, MDT 2013 Update 2 on site server, MDT 8443 (current) on management workstation.

    So the problem is apparently not universal.


    Gary Knigge

    Wednesday, November 16, 2016 6:01 PM
  • So the problem is apparently not universal.


    Gary Knigge

    I have this understanding, that this depends on a drivers and models you´re pushing. Some drivers works, some does not.... and it´s all around Windows 7.
    Thursday, November 17, 2016 7:36 AM
  • Yesterday i heard from Johan Arwidmark in a Windows 10 Session, that it is related to Windows 7 Deployments on SSD Systems.
    Friday, December 2, 2016 12:49 PM
  • Today i saw a Windows 10 Session with Johan and he suggested to add a "Restart Computer" Step before the "Apply Drivers" Step. This could be the solution for some scenarios.
    Wednesday, December 7, 2016 7:12 PM
  • Unfortunately the "Restart Computer" step does not work (at least not with the model I have tested). 

    The issue is definitely related to driver types. On a HP 650 G2 it works correctly (at least in my case) but on another model it fails (HP 440). If I remove all the drivers (except Network and Storage) it works. If I add the graphics driver to the driver package it fails... The only workaround for now is to use another ADK boot image.


    Nicolas Moreno


    Friday, December 9, 2016 1:20 PM
  • Now there are detailed workarround descriptions available:

    https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2016/12/28/apply-driver-package-task-fails-when-the-adk-is-upgrade-to-adk-10-1607/

    Wednesday, December 28, 2016 8:33 PM
  • Workaround 4 - if this happends only with Windows 7, use older boot images with W7 TS.
    Thursday, December 29, 2016 9:06 AM
  • Hello Mike,

    I had this problem and managed to solve it.

    To be able to reduce the Apply OS step in WinPE I had a step to set power plan to "High Performance".

    When I removed the power plan change step all machines were able to build successful again. 

    Tuesday, January 24, 2017 9:08 AM
  • Thanks Yavorc, we also apply that step. I will look into that.
    Tuesday, January 24, 2017 3:08 PM
  • They list several different ways of working around the issue--This resolved problems we were having with several different models of Dell computers imaging with Windows 7 x64
    Wednesday, February 1, 2017 4:08 PM
  • I see alot of people have decided to downgrade to the 1511 boot image in order to workaround this issue.

    Does anybody have some instruction on exactly how to do that?

    My site server is on CB 1606 with ADK 1607. Do I just uninstall ADK1607, install ADK1511, then run the PowerShell script (RegenerateBootImageWinPE10.ps1) to inject the CM binaries and drivers? Or is ther more to it?

    Thanks in advance!

    Wednesday, March 22, 2017 7:35 PM
  • If I can convince you to go one way or the other, I'd honestly recommend just using dism mentioned above (https://www.windows-noob.com/forums/topic/10856-sccm-2012-osd-apply-driver-packages-without-importing-them-to-the-database/)  I've been using this for months now and haven't had one single issue.  We use this method for all our OS builds now, not just Windows 7.  It's faster adding/importing drivers into ConfigMgr, takes up less space on your DPs, and you don't have to go backwards by downgrading.  and doing all those manual steps (I hate dealing with boot images when I don't have to)

    Or like Yannara said above, just go to the properties of your Windows 7 task sequence, and change the boot image to the previous if you still have it.  

    Just my two cents.

    Thanks


    Wednesday, March 22, 2017 9:19 PM
  • I see alot of people have decided to downgrade to the 1511 boot image in order to workaround this issue.

    Does anybody have some instruction on exactly how to do that?

    Always take backup of boot images before upgrading ADK. If you not, you might need to uninstall ADK 1607 and install 1511. Honestly, I don´t know for sure, will SCCM keep old boot images or not, when ADK is upgraded.

    N0w -most important thing to understand here is this: The boot image which are offered to PXE boot first will be the one which is _deployed_with_last_TS_inside.

    I would not downgrade to 1511 ADK, just dig up older boot image and use it with Win7 deployments or use WinPE based on ADK 8.1.


    Please remember to mark my post as an answer, if I really helped you out, or vote if usefull. Thank you!

    Wednesday, March 22, 2017 10:32 PM
  • Now there are detailed workarround descriptions available:

    https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2016/12/28/apply-driver-package-task-fails-when-the-adk-is-upgrade-to-adk-10-1607/


    Workaround 1 worked like a charm for me.
    Wednesday, July 5, 2017 11:00 AM