J3L2404
1 Nickel

OptiPlex 5040 Build Failures With MDT 2013

We are unable to successfully deploy Windows 7 images using MDT 2013 (using the Windows 10 ADK) on OptiPlex 5040 systems. We are using the A01 driver cab file for our deployment. What is happening is MDT will boot off our boot USB and successfully deploy the .wim file, apply the unattend.xml and reboot. It will detect devices and reach 100% status on that, but then fail on the "setup is applying system settings" part of setup with the following error: "Windows could not configure one or more system components. To install Windows, restart the computer and then restart the installation."

The last few lines of setupact.log are this:

2016-01-25 17:23:52, Error                 CSI    00000006@2016/1/26:01:23:52.365 (F) d:\win7sp1_gdr\base\wcp\componentstore\com\store.cpp(360): Store corruption detected in function `anonymous-namespace'::QueryPendingXmlIdentifier expression: 0
  RegistryCorruption on resource [50]"\Registry\Machine\COMPONENTS\\PendingXmlIdentifier"[gle=0x80004005]
2016-01-25 17:23:53, Error                 CSI    00000007 (F) HRESULT_FROM_WIN32(14098) #130# from Windows::COM::CComponentStore_IAdvancedInstallerAwareStore::ResolvePendingTransactions(dwFlags = (DontFailIfPrimitivesPending|IndicatePrimitiveRollback), Progress = NULL, Phase = 0, Disposition = (unknown enumerant 0)[3]" | "0)[gle=0x80073712]
2016-01-25 17:23:53, Error                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

Looking in setuperr.log the following errors show up:

2016-01-25 17:23:52, Error                 CSI    00000006@2016/1/26:01:23:52.365 (F) d:\win7sp1_gdr\base\wcp\componentstore\com\store.cpp(360): Store corruption detected in function `anonymous-namespace'::QueryPendingXmlIdentifier expression: 0
  RegistryCorruption on resource [50]"\Registry\Machine\COMPONENTS\\PendingXmlIdentifier"[gle=0x80004005]
2016-01-25 17:23:53, Error                 CSI    00000007 (F) HRESULT_FROM_WIN32(14098) #130# from Windows::COM::CComponentStore_IAdvancedInstallerAwareStore::ResolvePendingTransactions(dwFlags = (DontFailIfPrimitivesPending|IndicatePrimitiveRollback), Progress = NULL, Phase = 0, Disposition = (unknown enumerant 0)[3]" | "0)[gle=0x80073712]
2016-01-25 17:23:53, Error                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2016-01-25 17:23:53, Error      [0x030149] CMI    Callback_CBS_Do_OnlineInstall:Calling startup processing failed 0x80073712
2016-01-25 17:23:53, Error      [0x030153] CMI    Callback_CMI_ConfigInstall: CBS startup processing re-run failed.

The same errors occur when doing a MDT build where it skips the driver installation step.

What's strange is that these systems build just fine using our old MDT 2012 (WinPE 3/Win7 ADK) using the same driver .cab and .wim files. Other Dell models are successfully building off this same image and MDT 2013 so it seems like something specific to the 5040 hardware model.

Tags (1)
0 Kudos
13 Replies
dmiadan
1 Nickel

RE: OptiPlex 5040 Build Failures With MDT 2013

Following.  

I am having trouble getting Windows 7 loaded onto a 5040 as well.  My image works great on about 20 models.  I see all the drivers come down from the A01 cab as well. 

Drivers load then my Task Sequence restarts and then Windows Crashes.  Any information on the Original OP would be helpful. 

Dan

0 Kudos
dmiadan
1 Nickel

RE: OptiPlex 5040 Build Failures With MDT 2013

I think it is a Hard drive Driver. 

Hard drive on this system is

NVMe PM951 NVMe Samsung.   I get that information by installing Windows 10. 

 

0 Kudos

RE: OptiPlex 5040 Build Failures With MDT 2013

I am having a very similar issue with this system. I use SCCM and it fails every time. Works on multiple other Dell models. Anyone have a suggestion??

0 Kudos
dmiadan
1 Nickel

RE: OptiPlex 5040 Build Failures With MDT 2013

This is not a complete answer but I thought I would share. 

At first my Task Sequence would restart and then crash.   No error was given. 

I installed this.  I found it somewhere on a Samsung board. 

www.microsoft.com/.../details.aspx

This got past where I was.  Now I am getting an error.     At least I have something to Google. 

Windows could not parse or process the unattend answer file for pass specialize.   The settings specified in the answer file cannot be applied.  The error was detected while processing settins for component [Microsoft Windows - Shell Setup]

0 Kudos
dmiadan
1 Nickel

RE: OptiPlex 5040 Build Failures With MDT 2013

Ok.  This worked.  

I created a new Windows & wim.  I use Win 7 Enterprise.

Then I installed Kernal Mode drivers.

User-mode driver https://support.microsoft.com/en-us/kb/2685813

And

KB2685811             

Kernel-Mode driver https://www.microsoft.com/en-us/download/details.aspx?id=38423

Then, I also installed. this.

https://support.microsoft.com/en-us/kb/2990941


 

Ran a capture and it worked.   The Specific piece you need is in the last one. 

support.microsoft.com/.../2990941

That is the one that has the definitions in it to get the 5040 to work. 

 

I had a problem with MY TS that's why I was getting the error for the parsing the unattend.  That didn't have anything to do with this problem.

 

Dan

0 Kudos
J3L2404
1 Nickel

RE: OptiPlex 5040 Build Failures With MDT 2013

Did you have to add it to your reference build and generate a new .wim file, or did you just install that update as part of your deployment task sequence?

0 Kudos
dmiadan
1 Nickel

RE: OptiPlex 5040 Build Failures With MDT 2013

Yes, I had to created a whole brand new Windows7.wim on an old computer. 

Because Windows wont load without it.   So I don't know how to just add it to my task sequence because as soon as Windows would take over it would crash.  You have to get it in before Windows will install.  

So, my steps.  

1. Install Windows 7 SP1 on an OptiPlex 755 (or some old machine with a minimum of Windows 7 drivers)

2. Install all Three Kernels.   KB 2685811, KB 2685813,  kb2990941  (the first two are for 7450s that are in my environment I include them because I used them and do not test without them)

3. Rerun a capture.

4. Of course load drivers for the Model using the Current Dell Cab. 

Hope that helps. 

Dan

RE: OptiPlex 5040 Build Failures With MDT 2013

I'm using Windows 8.1 Enterprise--do you think this will work the same way??

0 Kudos
dmiadan
1 Nickel

RE: OptiPlex 5040 Build Failures With MDT 2013

Well, that's a good question.  If you try and install Windows 8.1 directly onto the System.  And it will not load because it doesn't see the Hard Disk.  Then yes, it's exactly same issue.  If you can put a Windows 8.1 disk in and install Windows 8.1 without a hitch.  Then the definition is in there and it should work without it.  

When you run your task sequence, watch where it crashes.  What happens right before it goes down?  

Do all of your drivers install?

Can you retrieve and SMSTS.log? 

Dan

0 Kudos