Start a Conversation

Unsolved

This post is more than 5 years old

376911

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.

 

 

November 5th, 2013 03:00

Not only.

When I download the Chipset Driver for the ST2E im getting a Windows 8.1 "Bluescreen".
Error: Problem loading Driver  \Driver\WudfRd for the Device HID\SMO91D0&Col01\4&1d42b6ad&0&0000.

There must be another issue as well with the Chipset Driver for Windows 8.1 and Latitude ST2E.

Can I use another Chipset Driver?

 

1.1K Posts

November 5th, 2013 09:00

The A06 Chipset for the ST2/ST2E is needed for the recent BIOS updates.  What version of BIOS are you running?  If it is an earlier release, I would suggest updating it to see if that gets the chipset drivers sorted out.

November 5th, 2013 23:00

A05, We will upgrade to A06 and see if this is working.

March 19th, 2014 12:00

I'm also getting that black screen problem (MDT2013 with Windows 8.1 so PE 5)

Did you ever figure out what it was?

March 20th, 2014 01:00

Can you post a little more information about the error? Do you have Log files?

March 20th, 2014 13:00

Hard to get the log files as the problem happens after initial system reboot so before I can access the device remotely. From testing on a manual build (install Clean 8.1 from USB and then use device manager to apply the drivers one by one, the Intel MSIC register driver SEEMED to cause the screen to go black instantly but on a second run (this time installing drivers starting from the bottom of the list in device manager) it was another Intel component that did it. I have been able to build up a working tablet using the installer version W82WB2_A07_Setup_MVD9Y_ZPE manually, but injecting these into the MDT build still results in a black screen. I am only injecting the ST2 drivers for this build.

March 21st, 2014 03:00

This is what i did. I installed one ST2 without ConfigMgr (in my case instead of MDT) and I was able to figure out the faulty Driver in the Dell cab file. Do you have the latest cab? I'ts a while ago, but i guess the faulty Driver in my case was on of the Atom Processor Driver. Can you download the Drivers from Intel instead of using the Dell once? Or try your taskseqeunce without the Atom processor to see if those are causing your issue.

March 23rd, 2014 14:00

Definitely something in Chipset - if installed as part of the build = black screen, if installed manually afterwards, no problem. Have tried multiple variations of drivers (older, newer, even different manufacturers) but same outcome. Will have to work around this.
No Events found!

Top