DISM.EXE error while applying unattend.xml during LTI deployment with MDT 2013 - Reproducible bug

The problem I am about to describe doesn't exist with MDT 2010 update 1, MDT 2012, or MDT 2012 update 1 when using the either WAIK or ADK.  I have not attempted to reproduce this problem with older versions of MDT or pre-release versions of MDT 2013.  The problem definitely exists with MDT 2013 RTM.

This is the same problem as Inconsistent DISM.EXE error when applying unattend.xml during LTI deployment - Possible bug!, but this is more concise and provides details on how to reproduce the problem. 

Status as of 2014-03-30 (Previous workaround deemed unusable - core bug still present)

Keith Garner determined that DISM.EXE was failing while processing the <offlineServicing> section in the unattend.xml file.  Removing this section resolves the issue, but this section is needed to inject drivers into the image during WinPE and is needed  The presence of this section didn't cause any problems with previous releases of MDT/ADK - it is likely an interoperability bug within the DISM.EXE tool.  See replies below for details.

Confirmed the problem applies to deploying Windows 8.1 as well.

Problem:

When deploying Windows 7 Pro x64 w/SP1 and enabling/disabling features using unattend.xml, deployment often (almost 100% of the time) fails with this dialog:

Steps to reproduce ("bare-metal"):

1. Create a new, clean virtual machine (I used VMware Workstation)
2. Boot the VM with the Windows 7 x64 Pro w/SP1 Volume Licensing DVD
3. Install Windows with default options, OOBE choices:
   • User name = Tony
   • Computer name = Tony-PC
   • Password = tony
   • Windows Update = recommend settings
   • Time zone = Eastern
   • Location  = Work network
4. Install VMware Tools and reboot
5. Configure Internet Explorer using express settings
6. Configure Windows Update to get updates for other Microsoft products
7. Apply all available Windows Updates*
8. Install ADK for Windows 8.1 (http://www.microsoft.com/en-us/download/details.aspx?id=39982)
   • Installs .NET Framework 4.5 automatically
   • Accept all default installation choices
9. Install MDT 2013 x64 (http://www.microsoft.com/en-us/download/details.aspx?id=40796)
   • Accept all default installation choices
10. Apply all available Windows Updates again*

*When installing Windows Updates:

• Select all important updates, except Internet Explorer 11
• Select all optional updates, except Bing Bar, Bing Desktop, Security Essentials, and Silverlight.

Launch MDT Workbench:

1. Create a new deployment share
   • Accept all defaults:  C:\DeploymentShare, DeploymentShare$, etc.
2. Import Operating System:
   • Full set of source files
   • Source Directory = CD drive containing the Windows 7 x64 Pro w/SP1 Volume Licensing DVD.
   • Accept remaining defaults
3. Create a new task sequence:
   • ID = Test
   • Name = Test
   • Template = Standard Client Task Sequence
   • OS = Windows 7 Professional
   • Key = Do not specify at this time
   • Settings:
     • Full name = Tony
     • Organization = Tony
     • IE Home Page = about:blank
   • Admin password = tony
4. Update Deployment Share, and completely regenerate the boot images.

From another new, clean virtual machine:

1. Boot from the "C:\DeploymentShare\Boot\LiteTouchPE_x64.iso" file from MDT computer.
2. Run the Deployment Wizard, and enter credentials (tony, tony, . )
3. Launch the created Task Sequence (accept defaults, click keep clicking ‘next’):
   • Computer name = autogenerated
   • Join a workgroup = WORKGROUP
   • Do not move user data and settings
   • Do not restore user data  and settings
   • Locale and time = accept defaults
   • Do not capture an image

At this point, the deployment will succeed every time.

Now, edit the task sequence and edit the unattend.xml:

1. Add the Foundation Package to the answer file
2. Edit the foundation Package:
   • Disable MediaPlayback > MediaCenter
3. Save file and close task sequence.

Deploy the task sequence again using the directions above (for each attempt, I used a new, unused VM), and it will fail nearly every time!

Notes:

• Enabling/Disabling features via unattended.xml is a supported and documented process.
• I suspect a bug with DISM.EXE v6.3 while operating on Windows 6.1 images.
• I realize that adding"Install Roles and Features" and/or "Uninstall Roles and Features" task sequence items may be a workaround for this problem (I haven't tried it), but it is not asolution to the problem.