Hopefully this is a quick one!  I've been slowly moving from thin images to thick images for the deployment speed and I've come across a strange problem.

I have used MDT 2012 to capture and deploy a 7 Pro 64bit image and straight after the OS installation the TS will reboot and I'll just get a black screen with a mouse.  No matter how long I leave it it will just sit there.

If I restart the PC manually the OS loads fine and the TS continues as if nothing happened.

The MDT logs don't show any errors or anything,  the Windows event logs don't show anything (other than a single error showing that the PC was shutdown unexpectedly).  I've rebuilt the image twice and deployed to our test model and a virtual machine with the same result.  I originally thought it might be driver related but the VM has a completely different driver set etc.

There is only a couple of applications installed onto the thick image (and we have created these images before for our laptops using the same application list with no issues).

Any ideas?

Thanks!

I tried to enable Bitlocker (manually) after a deploy, even though it gives me the option to save the recovery-key, but after I restart the laptop, the bitlocker screen comes up (after POST) and asks me to put the recovery key. Strange part is, it doesn't recognize the key at all. 

Any help is appreciated. 

Thank you!

Hi

Environment: Windows server 2008 R2(VM), 2GB RAM, WADK 8, MDT 2012 SP1

When I try to build a boot ISO using either MDT or ImageX, I receive an error when DISM is used to add packages.

Processing 1 of 1 - Adding package WinPE-HTA-Package~31bf3856ad364e35~x86~~6.2.9200.16384
An error occurred - WinPE-HTA-Package Error: 0x80070005

Error: 5

Access is denied.

This repeats for all WINPE packages being added by DISM. 

I have rebuilt the server and reinstalled but the same affect. I have tried running it as admin, editing rights and making the name of the packages lower case but cannot seem to get anywhere. Any help would be great.

 MDT 6.3.8330.1000 , ADK 10, windows 10 enterprise

Hi,

   I have few request to create custom image to join workgroup name like WRK123 with local administrator password P@ssw0rd123.

I have setup my customsetting ini 

SkipDomainMembership=YES
SkipAdminPassword=YES
AdminPassword=P@ssw0rd123
joinworkgroup = WRK123

But everytime it join workgroup, uses as Workgroup and different password.

I have also change unattend.xml file for password under

7 oobeSystem > amd64_Microsoft-Windows-Shell-Setup__neutral_31bf3856ad364e35_nonSxS >userAccounts>adminsitratorPassword. no luck.

any thoughts??

orion

Hi guys,

I've been banging my head against the wall trying to figure this one out but can't seem to make any progress.  Here's the situation:

I am attempting to create a Windows 10 x64 Enterprise Reference Image using a single task sequence that drops the image down, installs our software, suspends to allow me to customize the admin profile, and then captures the wim.  Everything works great as far as installing Windows 10 and the applications, and even the modifications I make to the admin profile (mainly just reorganizing the start menu) work great.

The problem is that the Sysprep and Capture part of the task sequence seems to be removing the default Edge and Store items on the taskbar.  Now I know that taskbar customizations do not carry over using CopyProfile in the unattend.xml but these are the default items that Windows uses and I'm not tinkering with them.  I can't figure out why they are getting removed.  I have checked the deployment logs and can't seem to find any clues.

Stranger still, if I choose not to perform the sysprep and capture step of the Reference Image task sequence and let it complete fully then start a Litetouch deployment and use a standalone Sysprep and Capture task sequence, the taskbar items remain intact. 

So while I do have a workaround, my question here is mainly for my own sanity.  Has anyone else encountered this or know what is causing the default taskbar items to disappear when using the reference image task sequence?  I am using MDT 2013 Update 2, perhaps this is a new bug?

Thanks.

Hi!

I am trying to figure out how to use MDT to deploy Windows 8.1 on the new trashcan Mac Pro's.

This is what I've done so far.

Disabled the default Format and partiton step with the property DONOTFORMATANDPARTITION=YES just to get rid of errors at the end, i have alos tried to remove the Volume entries in this step with out the above mentioned property.
In this step i have also set the Disk type to GPT and checked the Create Extra 'Active' Partition

Created a custom answer file to diskpart with the following command
sel dis 0
sel par 4
format fs=ntfs quick override
active
exit

Running my custom diskpart step after the default one.

Changed the default Install Operating System step to install on disk 0 partition 4.

All seems to work fine until the computer reboots and i should start windows to continue with the deploy.
Instead of booting windows it boots into OSX.
I've tried to change the start disk with the OS utility, but it gives the error "The bless tool was unable to set the current boot disk."

Ive tried the exact same thing on a older Macbook Pro, and this works flawless. It seems that Apple dropped some legacy support in the new EFI firmware on the new Mac Pro.

If i try to use bless with the --legacy parameter it tells me "Legacy mode is not supported on this system". I used legacy to boot windows on the older Macbook Pro.

Anyone got this working or have any suggestions?

I am using MDT 2013. I have custom Wizard Pane which generates Computer Name to be used for deployment and it assigns it as OSDComputerName variable. What I want to do is to determine if that computer exist in the AD Domain or not and if it does then warn the user. I have installed Web Services AD.ASMX and configured it on the deployment server. However, I have three questions:

1. I do not know how to specify parameter value OSDCompuertName

2. how to get return values from the servoce (True or False)

3. where do I put in Authentication credentials for webservice to query AD.

Here are the lines from my Customsettings.ini for WebService

Here is the vbscript I am trying to use:

<job id="MDTMenu_name">
<script language="VBScript" src="..\ZTIUtility.vbs"/>
<script language="VBScript" src="..\ZTIDataAccess.vbs"/>
<script language="VBScript">

Dim oService
Dim oXML

Set oService = New WebService
oService.IniFile = "CustomSettings.ini"
oService.SectionName = "GetComputerName"

Set oXML = oService.Query

If oXML Is Nothing Then
    oLogging.CreateEntry "Unable to call UserGetName web service.", LogTypeWarning
    WScript.Echo "Not Found" & vbcrlf
Else    
    WScript.Echo oXML //?? WILL THIS RETURN TRUE OR FALSE?
End If

</script>
</job>

Thanks,

DT

I'm using MDT 2013 Update with the latest 1511 Windows 10 ADK. Previously everything was working until I updated to MDT 2013 Update 1 to Update 2 and Windows 10 ADK to version 1511.

After I run the task sequence and first reboot occurs the machine stops in this error:

Info: The action could not be completed because the Bitlocker Drive Encryption key required to unlock the volume could not be obtained.

I'm deploying Windows 7 Enterprise x64.

When I attempt to update the Operating System images in MDT from our WDS server, I get the following error:

VERBOSE: Performing operation "import" on Target "Operating system".
import-mdtoperatingsystem : Unable to enumerate images on WDS server CHLWDS01.  This may occur if the server is not
configured to run WDS or if the WDS service is not running.
At line:1 char:1+ import-mdtoperatingsystem -path "DS001:\Operating Systems" -WDSServer "WDSSERVER" ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (:) [Import-MDTOperatingSystem], Win32Exception+ FullyQualifiedErrorId : System.ComponentModel.Win32Exception,Microsoft.BDD.PSSnapIn.ImportOperatingSystem

This only began after I have installed the MDT 2013 Update 2 (we were on Update 1 previously).

Thanks,

MRaybone

Hey Guys,

We want to start including the assettag in our computer names. This is easy enough by using the %assettag% variable in the customsettings.ini, but I need to accommodate machines that don't have an assettag configured. I was planning on using the first 6 of the serial number if there is no asset tag, but I am sure how to check if the assettag variable is empty

Any help you can provide would be appreciated, thanks

Dave 

I have MDT 2013 Update 1 and Windows 10 ADK. When capturing a reference image I run in to this. There is disk space on destination drive and it succesfully writes about 5 gigabytes of data to wim file before this error is thrown. What could be wrong? 

I have upgraded from MDT 2010 to MDT 2012.  After the upgrade, the PC's continue to work fine, the tools folder exists, and the install of applications occurs without a hitch.  The Dual Boot Macs are a completley different story though.  The install goes fine, but the Tools folder does NOT get copied to the machine and the computer errors out after the install of Windows during it's first boot into Windows when it logs in.

Here are the errors in LiteTouch.Log

<![LOG[Property ResourceDrive is now = C:]LOG]!><time="13:19:13.000+000" date="05-30-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceDrive = C:]LOG]!><time="13:19:13.000+000" date="05-30-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[FindFile: The file TsmBootstrap.exe could not be found in any standard locations.]LOG]!><time="13:19:13.000+000" date="05-30-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[FAILURE ( 5208 ): Unable to find the SMS Task Sequencer.  The deployment will not proceed.]LOG]!><time="13:19:35.000+000" date="05-30-2012" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">

Here are a few of the errors out of BDD.Log

<![LOG[FindFile: The file TsmBootstrap.exe could not be found in any standard locations.]LOG]!><time="13:19:13.000+000" date="05-30-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[FAILURE ( 5208 ): Unable to find the SMS Task Sequencer.  The deployment will not proceed.]LOG]!><time="13:19:35.000+000" date="05-30-2012" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.0.2223.0]LOG]!><time="13:20:06.000+000" date="05-30-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Again, it works on our NON-MAC computers, but ONLY fails on Dual Boot Mac's.  It seems to be related to the Tools folder and it not being there, and the install of the actual OS works fine.

Matthew

Trying to get MDT to deploy windows 8.1 on a bootcamp partition.

The boot Camp partition is partition # 4

Issues is MDT keeps failing with:

FAILURE (7813): False: Verify there are partitions defined in this task sequence.

I have DONOTFORMATPARTITION=yes DestinationDisk=0 and DestinationPartition=4 in customsettings.ini

Format & partition task continue on error.

When looking in the Logs I see that is is assigning drive C to partition #3, (which is really partition #4)

The logs show that ZTIDisk is setting partition #1 as Partition #0

When I do diskpart there is no partition 0 just 1,2,3,4

what odd is this is not happening with my Windows 7 boot camp task sequence.

Hello everyone,

We have 2 OS : french and english.

Within a Taskseq, we have 2  Operating systems: English and French. In MDT/Database/Computer we give a Role to each Computer. This Role is given as Options: UserLocale equals the keyboard layout. So if it's fr-ma, then it should install the French Os. And that goes wrong. It will always install the English OS. It is normal, cause the unattend.xml is default English OS.  What is the best way to do. Read in some papers it is not good to have 2 Os in your TS. Who has some tips. tanx Rik

Hello all,

I recently decided to start fresh with the latest MDT2013, ADK10 and Server 2012r2. I also created a brand new deployment share, so configurations are minimal at this point.

My task sequence list doesn't seem to be updating in the deployment wizard.

First I captured an updated version of an image, and upon deploying the image, I was surprised to see the previous version was deployed! I booted my sysprepped machine that I had captured, and it was the new version. I checked what OS was being installed in the task sequence, and the new one was listed.

I tried adding a new task sequence and a new folder, neither of them showed up.

Lastly I tried renaming one of the current task sequences. the name didn't change.

I have Skiptasksequence=NO in customsettings. It's obviously connecting to my deployroot or I would get an image menu. I've tried refreshiong with F5 AND rebooting the client machine all together. same thing. I have no idea what could be causing this!

Any help will be greatly appreciated. Thanks,

I have been having alot of trouble trying to deploy Win 7 Pro on MDT 2013 Update 1 (6.3.8298.1000) as i cannot do diskpart. The TS does not even reach the stage of copying of the WIM image.

Mt MDT error is:

Litetouch deployment failed, Return Code = -2147467259 0x80004005

I have followed various forum threads using methods like:

- adding empty "format disk" TS before the diskpart TS (MDT error will have an additional error saying no valid partition selected)

- using the DONOTFORMATANDPARTITION=YES

- open a new deployment share and re-add image and TS

- Read about the drive letters jumping around and assigned drive letter "C" in diskpart script

All these methods didnt work. Funny thing is, all the methods threw the same error code.

My diskpart script is as follows: diskpart /s "SCRIPTROOT\diskpart.txt" (start in is empty)

SELECT DISK 0
SELECT PARTITION 2
FORMAT FS=NTFS LABEL="OS" QUICK
ACTIVE
EXIT

My MDT logs:

https://onedrive.live.com/redir?resid=8A2AF7F0CAC03D65!474&authkey=!AGVUkAbkej8nuIA&ithint=folder%2clog

I'm currently running MDT 2013 Update 1 on a Windows 2012 R2 with WDS. I imported the OS files, drivers for Surface and created Task Sequence. I boot Surface Pro 3 into PXE and select my task and all works fine, it even loads the OS but when it tries to capture the image as the second phase it always fails with "Expected image state is Image_State_Generalize_Reseal_to_OOBE, actual image state is Image_State_Complete, sysprep did not succeed. Failure 6192, Litetouch deployment failed, return code = -2147467259 0x80004005"

I try capturing the image using a Sysprep and capture, connected to Deployment share and ran LiteTouch.vbs and wizard comes up and it starts to run thru the task but it fails in the same error. Driving me nuts and not sure why it's happening. I need to complete this image ASAP and I'm wondering if I'm hitting a MDT 2013 bug.

thanks in advance. 

I am trying to incorporate Bitlocker during my Deployment. 

This is what the CS.ini looks like:

[Settings]
Priority=Default
Properties=Type,MyCustomProperty

[Default]
_SMSTSORGNAME=Corp - Build Lab
UserDataLocation=NONE
OSInstall=Y
AdminPassword=P@ssw0rd
TimeZoneName=W. Europe Standard Time

WSUSServer=http://NLWUSSV02:8530
SLSHARE=\\REMCORPMIG01\Logs$\%ComputerName%
SLShareDynamicLogging=\\REMCORPMIG01\Logs$\%ComputerName%
UDDIR=%ComputerName%

ApplyGPOPack=NO

TimeZoneName=W. Europe Standard Time

JoinDomain=corp.Corpgroup.local
DomainAdmin=JoinAccount
DomainAdminDomain=corp.Corpgroup.local
DomainAdminPassword=P@ssw0rd

BDEInstall = TPM
BDERecoveryKey = AD
BDEInstallSuppress=NO
BDEWaitForEncryption=FALSE
BDERecoveryKey=AD


SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=YES

SkipSummary=YES
SkipRoles=YES

The deployment start, the OS installs and after the first reboot the Task Sequence just stops, no error message.

The logs show an error but i do not even get the usual HTA page at the end of a deployment with errors

This is the last lines of the BDD.log

Validating connection to \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:12 PM	0 (0x0000)
SMS Task Sequencer already found on C:\MININT\Tools\X64	LiteTouch	2/4/2016 4:57:12 PM	0 (0x0000)
Mapping server share: \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:12 PM	0 (0x0000)
RUN: regsvr32.exe /s "C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x64\Microsoft.BDD.Utility.dll"	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)
Found Existing UNC Path Y: = \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)
DeployRoot = \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)
FAILURE (Err): 429: CreateObject(Microsoft.BDD.Utility) - ActiveX component can't create object	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)

For the moment the TPM is not activated, it waits for State Restore in the Task Sequence, i have a Bitlocker group folder with Task sequence variable BDEInstallSuppress not equals YES

In this folder i have a couple of applications using cctk version 3.0 that set a BIOS password, enable TPM and activate it.

The OS drive was once encrypted so i have ran diskpart and used the clean command already

Could that be an issue with UAC? 

I ran a successful build task sequence on a VM to capture a custom WIM. When I try to deploy it, it gets 43% through the applying OS portion and fails with this message. I'm attaching the DISM log. Could their be an update that is causing this because I've went through and built it a second time.

2016-02-03 20:41:04, Info                  DISM   PID=2032 TID=1052 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
2016-02-03 20:41:04, Info                  DISM   PID=2032 TID=1052 DismCore.dll version: 10.0.10586.0 - CDISMManager::FinalConstruct
2016-02-03 20:41:04, Info                  DISM   PID=2032 TID=1052 Successfully loaded the ImageSession at "\\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64" - CDISMManager::LoadLocalImageSession
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Manager: PID=2032 TID=1052 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM.EXE:
2016-02-03 20:41:04, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2016-02-03 20:41:04, Info                  DISM   DISM.EXE:
2016-02-03 20:41:04, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.10586, Running architecture=amd64, Number of processors=2
2016-02-03 20:41:04, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.10586.0
2016-02-03 20:41:04, Info                  DISM   DISM.EXE: Executing command line: "\\CORPIMGSRV00.net\Dev-Windows$\Servicing\X64\DISM.exe"  /Apply-Image /ImageFile:"\\CORPIMGSRV00.net\Dev-Windows$\Operating Systems\Image - Win8.1 x64 - Q1 2016\IMG-WIN81-X64(2-2-2016-725).wim" /Index:1 /ApplyDir:C:
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Loading Provider from location \\CORPIMGSRV00.net\Dev-Windows$\Servicing\X64\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Connecting to the provider located at \\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Loading Provider from location \\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64\WimProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Connecting to the provider located at \\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Loading Provider from location \\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64\VHDProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Connecting to the provider located at \\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:04, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Loading Provider from location \\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64\ImagingProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:05, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Connecting to the provider located at \\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-02-03 20:41:05, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:05, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Loading Provider from location \\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:05, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Connecting to the provider located at \\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-02-03 20:41:05, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Provider has not previously been encountered.  Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:05, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Loading Provider from location \\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64\FfuProvider.dll - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:05, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Connecting to the provider located at \\CORPIMGSRV00.northamerica. .net\Dev-Windows$\Servicing\X64\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
2016-02-03 20:41:05, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2016-02-03 20:41:05, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2016-02-03 20:41:05, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
2016-02-03 20:41:05, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: WimManager
2016-02-03 20:41:05, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: WimManager.
2016-02-03 20:41:05, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: VHDManager
2016-02-03 20:41:05, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
2016-02-03 20:41:05, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
2016-02-03 20:41:05, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2016-02-03 20:41:05, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2016-02-03 20:41:05, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FfuManager
2016-02-03 20:41:05, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Getting Provider GenericImagingManager - CDISMProviderStore::GetProvider
2016-02-03 20:41:05, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2016-02-03 20:41:05, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Getting Provider WimManager - CDISMProviderStore::GetProvider
2016-02-03 20:41:05, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Provider has previously been initialized.  Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
[2032] [0x8144012d]
2016-02-03 20:44:56, Warning               DISM   DISM WIM Provider: PID=2032 [UncompressFile:(1116) -> file corrupted in block at offset 00000193D68C3F1A] C:\Windows\Installer\2b106.msp (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
[2032] [0x80070570] ResExtract:(472): The file or directory is corrupted and unreadable.
[2032] [0x8144012d]
2016-02-03 20:44:56, Warning               DISM   DISM WIM Provider: PID=2032 [ResExtract:(474) -> UncompressFile failed] C:\Windows\Installer\2b106.msp (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
[2032] [0x81440133]
[2032] [0x8144012d]
2016-02-03 20:44:58, Warning               DISM   DISM WIM Provider: PID=2032 [UncompressFile:(1116) -> file corrupted in block at offset 00000193D68C3F1A] C:\Windows\Installer\2b106.msp (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
[2032] [0x80070570] ResExtract:(472): The file or directory is corrupted and unreadable.
[2032] [0x8144012d]
2016-02-03 20:44:58, Warning               DISM   DISM WIM Provider: PID=2032 [ResExtract:(474) -> UncompressFile failed] C:\Windows\Installer\2b106.msp (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
[2032] [0x81440133]
[2032] [0x8144012d]
2016-02-03 20:44:59, Warning               DISM   DISM WIM Provider: PID=2032 [UncompressFile:(1116) -> file corrupted in block at offset 00000193D68C3F1A] C:\Windows\Installer\2b106.msp (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
[2032] [0x80070570] ResExtract:(472): The file or directory is corrupted and unreadable.
[2032] [0x8144012d]
2016-02-03 20:44:59, Warning               DISM   DISM WIM Provider: PID=2032 [ResExtract:(474) -> UncompressFile failed] C:\Windows\Installer\2b106.msp (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
[2032] [0x81440133]
[2032] [0x8144012d]
2016-02-03 20:45:01, Warning               DISM   DISM WIM Provider: PID=2032 [UncompressFile:(1116) -> file corrupted in block at offset 00000193D68C3F1A] C:\Windows\Installer\2b106.msp (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
[2032] [0x80070570] ResExtract:(472): The file or directory is corrupted and unreadable.
[2032] [0x8144012d]
2016-02-03 20:45:01, Warning               DISM   DISM WIM Provider: PID=2032 [ResExtract:(474) -> UncompressFile failed] C:\Windows\Installer\2b106.msp (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
[2032] [0x81440133]
[2032] [0x8144012d]
2016-02-03 20:45:02, Warning               DISM   DISM WIM Provider: PID=2032 [UncompressFile:(1116) -> file corrupted in block at offset 00000193D68C3F1A] C:\Windows\Installer\2b106.msp (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
[2032] [0x80070570] ResExtract:(472): The file or directory is corrupted and unreadable.
[2032] [0x8144012d]
2016-02-03 20:45:02, Warning               DISM   DISM WIM Provider: PID=2032 [ResExtract:(474) -> UncompressFile failed] C:\Windows\Installer\2b106.msp (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
[2032] [0x80070570] RestoreFileData:(2804): The file or directory is corrupted and unreadable.
[2032] [0x80070570] RestoreFileData:(2831): The file or directory is corrupted and unreadable.
[2032] [0x80070570] RestoreFileDataCallback:(1810): The file or directory is corrupted and unreadable.
[2032] [0xc144012e]
2016-02-03 20:45:02, Error                 DISM   DISM WIM Provider: PID=2032 C:\Windows\Installer\2b106.msp (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallback
[2032] [0x80070570] ProcessWimQueueNode:(96): The file or directory is corrupted and unreadable.
[2032] [0x80070570] DequeueWimData:(304): The file or directory is corrupted and unreadable.
[2032] [0x80070570] ImageWorkerThread:(203): The file or directory is corrupted and unreadable.
[2032] [0x80070570] GetImageErrorCode:(2833): The file or directory is corrupted and unreadable.
[2032] [0x80070570] RestoreFileNodeList:(1936): The file or directory is corrupted and unreadable.
[2032] [0x80070570] RestoreFilesCallback:(3638): The file or directory is corrupted and unreadable.
[2032] [0x80070570] EnumImageDataEntries:(1047): The file or directory is corrupted and unreadable.
[2032] [0x80070570] RestoreAllData:(985): The file or directory is corrupted and unreadable.
[2032] [0x80070570] WIMApplyImageInternal:(704): The file or directory is corrupted and unreadable.
2016-02-03 20:45:02, Error                 DISM   DISM WIM Provider: PID=2032 TID=1052 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1046 - CWimManager::Apply(hr:0x80070570)
2016-02-03 20:45:03, Error                 DISM   DISM Imaging Provider: PID=2032 TID=1052 base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:2500 - CGenericImagingManager::InternalCmdWimApply(hr:0x80070570)
2016-02-03 20:45:03, Error                 DISM   DISM Imaging Provider: PID=2032 TID=1052 base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:535 - CGenericImagingManager::ExecuteCmdLine(hr:0x80070570)
2016-02-03 20:45:03, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2016-02-03 20:45:03, Info                  DISM   DISM.EXE:
2016-02-03 20:45:03, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
2016-02-03 20:45:03, Info                  DISM   DISM.EXE:
2016-02-03 20:45:03, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2016-02-03 20:45:03, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2016-02-03 20:45:03, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2016-02-03 20:45:03, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2016-02-03 20:45:03, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2016-02-03 20:45:03, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2016-02-03 20:45:03, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2016-02-03 20:45:03, Info                  DISM   DISM Provider Store: PID=2032 TID=1052 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider