Unsolved
This post is more than 5 years old
2 Posts
0
377100
September 26th, 2013 10:00
Dell driver cabs not working in Windows 8.1 Enterprise Images
I have been using the Windows 8 Driver CABs in my SCCM 2007 Task Sequences to image E6420 laptops, and it has been working fine. So far I have been using a WIM OS image file that is based on Windows 8.0 Enterprise x64.
I just created a new .wim image file of Windows 8.1 Enterprise x64, and when I try to image a E6420 using my task sequence and the new 8.1 WIM, the task sequences fails to install the drivers correctly. I'm wondering if anyone at dell has had a chance to test the Windows 8 driver cabs with the new 8.1 image and SCCM?
It's showing this error:
= Error: 0xc0000135 An error occurred while attempting to start the servicing process for the image located at C:\. For more information, review the log file. The DISM log file can be found at C:\_SMSTaskSequence\PkgMgrTemp\dism.log Dism failedwith return code -1073741515 Failed to add driver to driver store. Code 0xc0000135 Failed to provision driver. Code 0xc0000135
The dism log file shows:
2013-09-23 14:50:25, Info DISM DISM WIM Provider: PID=556 [D:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2013-09-23 14:51:26, Error DISM DismHostLib: Failed to create DismHostManager remote object. Checking for dismhost.exe exit code.
2013-09-23 14:51:26, Info DISM DismHostLib: Found dismhost.exe exit code.
2013-09-23 14:51:26, Error DISM DISM Manager: PID=556 Failed to create Dism Image Session in host. - CDISMManager::LoadImageSession(hr:0xc0000135)
2013-09-23 14:51:26, Warning DISM DISM Manager: PID=556 A problem ocurred loading the image session. Retrying... - CDISMManager::CreateImageSession(hr:0xc0000135)
2013-09-23 14:52:28, Error DISM DismHostLib: Failed to create DismHostManager remote object. Checking for dismhost.exe exit code.
2013-09-23 14:52:28, Info DISM DismHostLib: Found dismhost.exe exit code.
2013-09-23 14:52:28, Error DISM DISM Manager: PID=556 Failed to create Dism Image Session in host. - CDISMManager::LoadImageSession(hr:0xc0000135)
2013-09-23 14:52:28, Error DISM DISM Manager: PID=556 Failed to load the image session from the temporary location: D:\_SMSTaskSequence\PkgMgrTemp\A9B8E9AF-19EC-489F-B0A5-4D523BCBED6F - CDISMManager::CreateImageSession(hr:0xc0000135)
2013-09-23 14:52:28, Error DISM DISM.EXE: Could not load the image session. HRESULT=C0000135
2013-09-23 14:52:28, Error DISM DISM.EXE: Unable to start the servicing process for the image at 'D:\'. HRESULT=C0000135
2013-09-23 14:52:28, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
minhtu
18 Posts
0
October 12th, 2013 17:00
hey guy.DELL still does not release drivers for win 8.1.And divers for win 8 will not worked on win 8.
�
DELL-Warren B
1.1K Posts
0
October 14th, 2013 13:00
Windows 8.1 drivers will be released after Windows 8.1 GA (this Friday).
minhtu
18 Posts
0
October 14th, 2013 17:00
thanks Warren Byle so much
Endersc
2 Posts
0
October 16th, 2013 09:00
Thanks, I will wait for them to come out and test them then.
flymolo2k
1 Message
0
October 18th, 2013 12:00
The GA is here and we are still waiting for 8.1 cabs.
Dustin Hedges
1 Rookie
•
96 Posts
0
October 25th, 2013 14:00
New driver CABs for the 9020 and 9020 AIO are available now.
officechris
9 Posts
0
October 25th, 2013 14:00
Same issues here, although if you set it to "Continue on Failure" Windows 8.1 does load, no issues, no drivers missing. Tested on SCCM 2012 SP1 /w CU3, Windows 8.1, on Optiplex 2020AIO.
officechris
9 Posts
0
October 25th, 2013 17:00
Still getting the same errors during applying driver package. Using OSD on SCCM 2012 SP1 /w CU3 deploying 8.1 image to 9020 AIO using the new 8.1 AIO Driver CAB.
DELL-Warren B
1.1K Posts
0
October 28th, 2013 11:00
Can you provide any details on which driver is causing the issue? Does leveraging "continue on error" provide an interim workaround?
officechris
9 Posts
0
October 29th, 2013 08:00
Yes, choosing "Continue On Error" does get me into the OS, and from what I see everything is working (nic, sound, video, webcam, etc). So nothing terribly broken, however I see 3 missing drivers in device manager.
PCI Serial Port -
Device PCI\VEN_8086&DEV_8C3A&SUBSYS_05A71028&REV_04\3&11583659&0&B0 was configured.
Driver Name: null
Class Guid: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device Id:
Outranked Drivers:
Device Updated: false
PCI Simple Communications Controller
Device PCI\VEN_8086&DEV_8C3A&SUBSYS_05A71028&REV_04\3&11583659&0&B0 was configured.
Driver Name: null
Class Guid: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device Id:
Outranked Drivers:
Device Updated: false
SM Bus Contoller
Device PCI\VEN_8086&DEV_8C22&SUBSYS_05A71028&REV_04\3&11583659&0&FB was configured.
Driver Name: null
Class Guid: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device Id:
Outranked Drivers:
Device Updated: false
Let me know if you have other log files you want me to dig into. The task sequence progress reports the Apply Driver Package step as "Failed" with a "Failed to Provision Driver. Code 0xc0000135"
officechris
9 Posts
0
October 29th, 2013 08:00
One last thing, if I take those 3 devices that did not install, do a "Update Driver", then simply point it at my 8.1 Driver Package directory, all 3 devices install just fine.
They are...
Intel AMT - SOL (COM3)
Intel Management Engine
Intel 8 Series / C220 Series SMBus Controller
officechris
9 Posts
0
October 29th, 2013 10:00
x64 bit
DELL-Warren B
1.1K Posts
0
October 29th, 2013 10:00
are you installing x86 or x64 Windows 8.1?
alschneiter
5 Posts
0
November 5th, 2013 01:00
Same issue here with SCCM 2012 SP1 CU3 and Latitude Tablet 10 ST2E.
We used the CAB file for Windows 8 / tried a new driver pack with the new deployed Windows 8.1 drivers but we expect the same issue. Error code in the Tasksequence as follow:
The task sequence execution engine failed executing the action (Dell Latitude 10 ST2 Win8.1) in the group (Drivers) with the error code 3221225781
Action output: ... nstaller.cpp,549)
AddPnPDriverToStore( pszSource, sTargetSystemDrive, sTargetSystemRoot, wProcessorArchitecture), HRESULT=c0000135 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,659)
InstallDriver( iInstallParams->sContentId, iInstallParams->sSource, iInstallParams->pBootCriticalInfo ), HRESULT=c0000135 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,557)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\S01002F6
reference count 1 for the source C:\_SMSTaskSequence\Packages\S01002F6 before releasing
Released the resolved source C:\_SMSTaskSequence\Packages\S01002F6
pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=c0000135 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,380)
Exiting with return code 0xC0000135
Dism failed with return code -1073741515
Failed to add driver to driver store. Code 0xc0000135
Failed to provision driver. Code 0xc0000135.
Aftrer the TS I tried to install the driver manually. The driver for the processor IPC with SCU fails during the install and I'm getting a black screen on the Tablet.
So I tried a driver pack without this atom processor driver. Same issue during the tasksequence.
Any help on that?
Thanks,
Al
HansL1337
1 Message
0
November 5th, 2013 02:00
Problem is the WinPE Image in SCCM2012. This won't let you install the drivers in Windows 8.1. You can install 2012 R2 or build manually a WinPE 5 Image:
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/