I am experiencing some inconsistent behavior when it comes to OSD and driver package injection. We are using explicit driver packages for each model of machine, and applying those packages based on WMI queries in the task sequence.
Frequently, we are seeing failures when injecting drivers, which result in BSOD after the first reboot (these are SCCM 2012R2+MDT 2013 task sequences).
In the smsts.log we have these entries:
Setting %SystemRoot% to "E:\WINDOWS" OSDDriverClient 7/18/2014 10:17:18 AM 1184 (0x04A0) Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "amd64" OSDDriverClient 7/18/2014 10:17:18 AM 1184 (0x04A0) Added list item with key value '1' OSDDriverClient 7/18/2014 10:17:18 AM 1184 (0x04A0) Writing configuration information to E:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 7/18/2014 10:17:18 AM 1184 (0x04A0) Successfully saved configuration information to E:\_SMSTaskSequence\PkgMgrTemp\drivers.xml OSDDriverClient 7/18/2014 10:17:18 AM 1184 (0x04A0) Setting temporary directory to 'E:\_SMSTaskSequence\PkgMgrTemp'. OSDDriverClient 7/18/2014 10:17:18 AM 1184 (0x04A0) Calling Package manager to add drivers to the offline driver store. OSDDriverClient 7/18/2014 10:17:18 AM 1184 (0x04A0) Command line for extension .exe is "%1" %* OSDDriverClient 7/18/2014 10:17:18 AM 1184 (0x04A0) Set command line: "X:\windows\system32\dism.exe" /image:"E:" /windir:"WINDOWS" /apply-unattend:"E:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"E:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 7/18/2014 10:17:18 AM 1184 (0x04A0) Executing command line: "X:\windows\system32\dism.exe" /image:"E:" /windir:"WINDOWS" /apply-unattend:"E:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"E:\_SMSTaskSequence\PkgMgrTemp\dism.log" OSDDriverClient 7/18/2014 10:17:18 AM 1184 (0x04A0) Process completed with exit code 2147500037 OSDDriverClient 7/18/2014 10:17:20 AM 1184 (0x04A0) uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,548) OSDDriverClient 7/18/2014 10:17:20 AM 1184 (0x04A0) Dism failed with return code -2147467259 OSDDriverClient 7/18/2014 10:17:20 AM 1184 (0x04A0) AddPnPDriverToStore( pszSource, sTargetSystemDrive, sTargetSystemRoot, wProcessorArchitecture), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,658) OSDDriverClient 7/18/2014 10:17:20 AM 1184 (0x04A0) Failed to add driver to driver store. Code 0x80004005 OSDDriverClient 7/18/2014 10:17:20 AM 1184 (0x04A0) InstallDriver( iInstallParams->sContentId, iInstallParams->sSource, iInstallParams->pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,557) OSDDriverClient 7/18/2014 10:17:20 AM 1184 (0x04A0) pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,380) OSDDriverClient 7/18/2014 10:17:20 AM 1184 (0x04A0) Failed to provision driver. Code 0x80004005 OSDDriverClient 7/18/2014 10:17:20 AM 1184 (0x04A0) Exiting with return code 0x80004005 OSDDriverClient 7/18/2014 10:17:20 AM 1184 (0x04A0)
In the dism.log I have these entries:
2014-07-18 10:17:20, Info CBS Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/SOFTWARE' from path '\\?\E:\Windows\System32\config\SOFTWARE'.
2014-07-18 10:17:20, Info CBS Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/SYSTEM' from path '\\?\E:\Windows\System32\config\SYSTEM'.
2014-07-18 10:17:20, Info CBS Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/SECURITY' from path '\\?\E:\Windows\System32\config\SECURITY'.
2014-07-18 10:17:20, Info CBS Loading offline registry hive: SAM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/SAM' from path '\\?\E:\Windows\System32\config\SAM'.
2014-07-18 10:17:20, Info CBS Loading offline registry hive: COMPONENTS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/COMPONENTS' from path '\\?\E:\Windows\System32\config\COMPONENTS'.
2014-07-18 10:17:20, Info CBS Loading offline registry hive: DEFAULT, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/DEFAULT' from path '\\?\E:\Windows\System32\config\DEFAULT'.
2014-07-18 10:17:20, Info CBS Failed to open the registry root: n/a, key: Microsoft\Windows NT\CurrentVersion\ProfileList. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2014-07-18 10:17:20, Info CBS Failed to query for path to user profiles directory. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2014-07-18 10:17:20, Info CBS Failed to load the default user profile registry hive. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2014-07-18 10:17:20, Error DISM DISM.EXE: DISM Unattend Manager processed the command line but failed. HRESULT=80004005Are there any other logs I can look at to determine why dism is having these registry issues? The cbs.log on the hard drive is not current. The setupapi.offline.log only lists the successful driver injections, so it isn't much help.
Where can I get more detail on what is happening here?