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.

Since upgrading from MDT 2012 to MDT 2013 Update 1 we have been having a bunch of issues, but this one is the most important right now. To test this, I have installed a brand new copy of Windows 10 Enterprise on a separate computer. On this fresh copy of Windows 10, I installed Win 10 ADK and MDT 2013 Update 1 and created a brand new deployment share. I created a HyperV image of a brand new Windows 7 x64 SP1 installation, captured it with the new MDT, and then tried to deploy with the new MDT.

However, when deploying this image, after the first reboot post the OS install phase, the computer gives the following black screen error right after BIOS:

Pretty much at my wits end with this, I have been trying to get the split wim  setting to successfully complete with more than 1 wim file included in the selection profile.

Currently the sweetspot is 1 wim file, always completes, if I add another os wim to the selection profile I 100% get a failure as per the screenshot.

I have had this issue since the feature has been introduced in the various incarnations of MDT 2013 U1\U2.

I am running the latest , greatest versions of MDT, pretty much tried every permitation to get it to work and have wasted days of my life testing this feature.

It would be great if someone could definatively say more than one wim in the selection profile will complete sucessfully.

Cheers

Ewen.

Hello all,

I'm Trying to make an UEFI offline media USB with MDT 2013 Update 2

The .wim size that I want to deploy is 4.32GB although I've set "SkipWimSplit" to False in :

•  %DeployRoot%\Controls\Settings.xml
•  %MediaRoot%\Content\Deploy\Controls\Settings.xml

MDT just copy my .wim file without splitting it but I can't copy it after on a FAT32 USB drive.

What should I do to make it work ?

Creating my image via hyper-v.

Using model specific driver deployment.

My Dell deployments seem to work just fine, but I can't get a single HP one to work, and I'm having trouble finding anything useful. I've tried rebuilding the base image to no avail.

The image gets written to the system in WinPE, drivers get added, DISM gets processed, and then it reboots for the next step and I get that black screen.

I've been trying to work on this for too long and I'm pulling my hair out - someone please. Anyone. Help!

Hello,  we've been having issues with deploying Windows 10 since it first became available.  It's becoming increasingly problematic as more users request Windows 10, deployments only succeed about 50% of the time.  The other 50% of the time, the task sequence fails at random points during the State Restore phase.  

All that is happening during the state restore is pretty much the norm, some applications are set to install, it sets some variables, joins the domain and restarts.  Windows 7 deployments have no issues with these tasks, Windows 10 is highly unpredictable. Currently the only solution I have for the help desk guys is to reimage the machine until it succeeds.  

Now when it fails, the only actual 'error' I can find in any logs is in the smsts.log.  I decided to make every single step in the State Restore phase of the task sequence continue on error so I can get a better idea of what it is doing.  It'll start the State Restore phase normally, but after several steps in it'll skip a whole lot of steps, then it'll successfully do other steps, then skip some more.  Each machine I've seen succeeds and skips completely different steps, and they all skip with the error of 'Incorrect Function'.  Any type of step will fail with this error also.  Though since most of the steps are for application installs, they apply mostly to those, but it also will randomly fail on 'run command line' steps, and also 'set task sequence variable' steps.  

For testing purposes I have been reimaging a Dell Latitude E7440 and Latitude E7450.  MDT version is current 2013 Update 2, however this problem was also present in Update 1.  My troubleshooting has resorted to my last ditch effort of recreating an entirely new deployment share using the latest MDT build, creating a bare bones windows 10 image to deploy and test and the results are the same as the normal production deploymentshare.  Reimaging these two laptops will literally either half the time fail out at some random time, or will process all steps successfully.  

Logs from two different deployments:

http://1drv.ms/1Po41sF

The smsts.log is literally littered with random steps that either succeed or fail.  the ZTIApplications.log doesn't provide any log information regarding the applications that succeeded or failed.  Likewise, ZTISetVariable.log has no information about the variables it couldn't set, and the ZTIDomainJoin.log has no information (or wasn't even created), as well with ZTIGroups.log and ZTIUserState.log.  These failures are only randomly occurring in the State Restore phase, after the image has been loaded on the drive and the OS boots up and logs in.  The error for any script it's calling in Incorrect Function, I don't know what it's doing and ran out of things to try and do to make it work.  And it's gotta work correctly...  this is all the information I can think to provide, but do let me know if more information would be useful.  

Thanks!

HI All

Have built a new MDT 2013 server upon a windows 2012 box, currently getting the following error when deploying Windows 7 image only all Win 8.1 and 10 images deploy fine. Can any one help with ?

FAILURE (5624): 1392 Run DISM: /Apply-

Image /ImageFile:\\HUYTONSC\DeploymentShare$|Operating Systems\Win 7 x32 Sp1 July 2015\Win 7 x32 Sp1 July 2015.wim index:1 /ApplyDir.F:
Litetouch Deployment Failed, Return Code -2147467259 0x800004005

Have tested the same images on a MDT 2010 server running Server 2k8 and also in a lab setup before hand and they all performed as expected and deployed fine.

Applied the MDT 2013 update 2 hoping that would resolve but it didnt, have also deleted and re added the images they work for 1 deployment and then fail there after

Banging my head on the table right now

Cheers

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

Hopefully, I can get some feedback on this topic.

We're currently using MDT for win 7 deployment, while create new win10 reference image the captures file size was 3.4MB from vm client. We do not have issue with win 7 wim file.

Window 10 ADK, MDT 2013 update 2, win10 th2

Hey guys,

Our computer naming convention includes the OS version. How can I get the OS version being applied?

I thought I could determine the OS by the which TasksequenceID was selected(W7 TS =  W7), however I didn't not have any success.

In my TS I specify the WSUS server. I enable to install updates before applications and after applications.

I can watch the TS during the image deployment show its running the updates, but its quick, like it doesn't find any. 

Even the BDD log shows its set the WSUS server properly and the client is configure hit it.

The ZTIWindowsudpate logs show the following: I'm not sure why its trying to hit the internet when the WSUS server is specified??? After the image is laid down I can go to HKLM:Software\Policies\Microsoft\windows\windowsUpdates and see that the two values point to my WSUS server (WUServer, WUStatusServer).  I'm stuck.  Any help would be appreciated.  This used to work fine. 

Right after the image is down I can run a update manually using MS site and it pulls a couple dozen updates....

<![LOG[Begin Windows Update. Reboot=[true]  Retry=[true]  Count = 2]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Property MSIT_WU_Count is now = 3]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Property SMSTSRebootRequested is now = ]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Property SMSTSRetryRequested is now = ]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Configuring client to use WSUS server <a href="http://mywsusserver.fqdn:8530]LOG]!><time="15:04:34.000+000">http://mywsusserver.fqdn:8530]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="15:04:34.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Windows Update Agent verion 8 found, OK to continue]LOG]!><time="15:04:39.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.9.9600.18094]LOG]!><time="15:04:39.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Microsoft Update Service:  Enabled = False]LOG]!><time="15:04:39.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0]]LOG]!><time="15:04:39.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Start Search...]LOG]!><time="15:04:39.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Error searching for updates: Not Connected to Internet? (-2145107924)]LOG]!><time="15:04:41.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Restore NoAutoUpdateKey to <empty>.]LOG]!><time="15:04:41.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[ZTIWindowsUpdate processing completed successfully.]LOG]!><time="15:04:41.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"><![LOG[Event 41001 sent: ZTIWindowsUpdate processing completed successfully.]LOG]!><time="15:04:41.000+000" date="01-30-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">

Below is my unattend.xml. I cannot get the default admin profile to copy over for all new domain users. Windows 7 was a breeze, but for Windows 10 it simply ignores it. This is quite frustrating for enterprise users. Any ideas?

I am having great difficulty deploying a windows 10 image to our Surface PRO 4 tablets. 

I have created the offline media just fine. What is the proper step to format a usb? 

I have tried FAT32 and NTFS to no avail. I have also tried MBR and GPT partition scheme to no avail.

My wim file is greater than 4GB so FAT32 will not work. SECURE BOOT is disabled on the surface pro 4. I am having trouble booting the tablet from USB. I need help! 

Holding the down button and then power does not work at all!!

Updated 12/22/2015 (MDT 2013 Update 2)

Videos & Extra Content

How to Debug missing Drivers in MDT Litetouch

How to find the right MDT log files (bdd.log/smsts.log) to debug problems.

How to debug problems in Windows Setup (Panther)

Getting Started

What is MDT?

MDT is a product made by Microsoft to assist in the Deployment of Windows. It sits on top of other Microsoft technologies and tools like the WAIK/ADK, USMT, PXE/WDS, WSIM, Windows OOBE setup, and System Center Configuration Manager, and provides a single interface and environment for these tools. It’s fully supported by Microsoft, and has a well-established community of IT Professionals that use it.

What is the current version of MDT?

The current version is "MDT 2013 Update 2" Build "6.3.8330", and supports deployments of Windows 7 and newer (including Windows 10), and Windows Sever 2008 R2 and newer, and Configuration Manager 2012.  Link:http://www.microsoft.com/en-us/download/details.aspx?id=50407, you can see the announcement here: http://blogs.technet.com/b/msdeployment/archive/2015/12/22/mdt-2013-update-2-now-available.aspx.

Previous versions include "MDT 2013 Update 1" Build 6.3.8298.0, and "MDT 2013" Build 6.2.5019.0.

Where can purchase MDT?

MDT is available for FREE!  Download from: http://www.microsoft.com/deployment

Why would I use SCCM if MDT is free? Why use MDT if I already have SCCM?

MDT is a light weight Task Sequencing environment, it can deploy windows, or other simple tasks. Configuration Manager is a complete management system for your clients. Operating System Deployment (OSD), is only one of the many tasks that SCCM can do. Additionally, MDT has several “enhancements” to the stock Configuration Manager environment. If you are experienced with the standard MDT LiteTouch Task Sequence then the MDT/SCCM ZeroTouch Task Sequence will be easy.

What is LTI/ZTI/UDI?

MDT has several ways in which you can deploy images:

• LiteTouch (LTI) is the term used to describe the MDT deployment process from the user’s perspective where there is small amount of user interaction at the start, and the remainder of the process is automated. (Confusingly…) MDT LTI process can be fully automated (skipping the wizards) to behave like a ZeroTouch process.
• ZeroTouch (ZTI) is the term used to describe a Configuration Manager (SCCM) deployment with MDT extensions. From the user’s perspective, the procees is fully automated (Zero Touching). (Confusingly…) MDT ZTI can be made to prompt the user for information through UDI.
• User Driven Installation (UDI) is a User Interface toolkit included in MDT that can be added to the Configuration Manager (SCCM) OSD process.
• HeavyTouch (not a common term) can be used to describe the full Windows OOBE (Out of Box Experience), with no MDT or SCCM additions.

Where can I find out more information on MDT?

• MDT itself actually has some great documentation. Variables are defined, all scripts are listed, and includes several walk through guides. Take a look.
• There are several books on MDT deployment (Internet search for: MDT Book).
• Several companies provide training sessions for MDT, SCCM and more.
• MDT is always covered at the big Microsoft IT Conferences for Windows like TechEd.
• Most Windows Desktop Deployment Consultants will be familiar with MDT and SCCM, including Microsoft’s own Consulting Group.
• There are also tools and (hydration) kits available to quickly build out MDT evaluation environments. (Search for: Windows POC Kit)
• Additionally, this forum is a great place to ask questions and get involved.

Forum guidelines 

Be Nice. Help out. Remember, there are always new people here who need help getting started.

What is cloning? What are Images? What is SysPrep?

Starting with Windows Vista, Microsoft has been moving towards the common industry model of disk imaging. That means once a machine has been setup into a desired “golden” state ( Applications Installed, Files Copied, Settings Configured ), the disk is copied to an archive file (disk image) so it can be applied to other machines (cloned).  Of course if you were to take a hard disk from one machine to another it shouldn’t work, the computer name needs to change, device drivers need to be re-enumerated, and the OS need to verify the hardware for licensing. The official way to prepare a machine for cloning is to run the SysPrep.exe tool just before the capture or move. Images are stored in several archive files used by Microsoft: *.wim files are compressed archives used by the Retail Windows Installation DVD’s, *.vhd/*.vhdx files are a generic container used by Hyper-V to emulate a physical disk.

How many times can I SysPrep the same machine (image)?

For Windows Vista and above: Three.

In Windows XP, it was common to take an OS image, install new applications, apply patches, sysprep, and re-use. Then when new applications and patches came out, you would take the latest OS image, and repeat the process. A Windows XP image may have been syspreped dozens of times. Over and over again.

However this image (un)management model was broken in Windows Vista, you could only sysprep a machine a maximum of three times (due to licensing changes). MDT has become a popular alternative to create images:

• Add all of your Applications to the MDT console (with silent install switches)
• Add any *.reg (registry modifications)
• Create a create a task sequence with the Windows “retail” DVD image or Volume License (VL) files directly from Microsoft.
• Then run the Task Sequence on a blank virtual machine, and export the captured result back to the MDT server.
• MDT can even contact the Windows Update Service to download all the latest patches for your operating system.

If you are able to automate your application installs and registry settings, you have a consistent, repeatable imaging process. When Microsoft comes out with new critical patches, all you need to do is re-run the automated install in your virtual machine. Easy!

What are Fat Images? What are Thin Images? Hybrid?

MDT can be used in two different scenarios, Imaging and Deployment.

• Imaging is the process of creating a new *.wim file that contains common Applications, Settings (and sometimes common Drivers). MDT can install the OS, Applications, Registry Settings, Patch using Windows Update, Sysprep, and save the contents to a single *.wim file in a single automated process.
• Deployment is where MDT or SCCM can install a retail *.wim file or use a captured *.wim file to install on the end user’s machine. MDT can also install additional Applications, Configuration Settings, Migrate User Files and Settings, Drivers and more.

Should an Application be installed into the core image, or be installed at deployment? Examples:

• Fat - If you have an environment where all the machines are identical (hardware, applications and setting), then a Fat Image could be optimal. Very little (or nothing) is done at deploy time.
• Thin - If you have an environment where the machines are all different (hardware, applications, and settings), then it would be best to keep the core image as small (or thin) as possible, and perform an intelligent job of installing the required applications, settings and drivers per machine. A very thin image could be one that only contains Microsoft Hotfix patches.

How do I make registry settings I set in HKEY_CURRENT_USER available after I Sysprep?

When you make changes to the HKEY_CURRENT_USER registry key during your task sequence in MDT, it only makes changes for the local “Administrator” account. When you sysprep, by default those changes are discarded. It is possible to tell sysprep to make the local “Administrator” account the default user profile using CopyProfile. Check out these excellent blog posts describing some of the issues.

http://blogs.technet.com/b/deploymentguys/archive/2009/10/29/configuring-default-user-settings-full-update-for-windows-7-and-windows-server-2008-r2.aspx

http://blogs.technet.com/b/askcore/archive/2010/07/28/customizing-default-users-profile-using-copyprofile.aspx

How to customize the Start Screen in Windows 8+

Windows provides a limited set of interfaces to modify the Start Screen programmatically(or via script). The best solution to make a Start Screen the way you want is to manually prepare the screen in the full OS with the local Administrator account, SysPrep and then use CopyProfile to ensure that the Start Screen for the Administrator is applied to all new users. For more information see:http://technet.microsoft.com/en-us/library/jj134269.aspx
(Personally I prefer the AppsFolderLayout.Bin method in this article).

Religious Wars 

Warning: asking the following topics may produce different answers from different users. (Provided here as humor).

• Sector Based Imaging vs File Based Imaging - *.vhd is sector based, *.wim is file based. MDT mostly uses *.wim files.
• Fat images vs Thin Images  - See Above
• Structured Driver Installation vs Chaos – http://channel9.msdn.com/Events/TechEd/NorthAmerica/2012/WCL307
• Single Partition vs Multiple Partitions for Disk 0 –Don’t put data on D: drive.

What to do when things go wrong?

First off, don’t panic. Remember, Windows Deployment is a large and complex system.

If you are new to MDT and Windows deployment, now would be a good time to familiarize yourself with some of the troubleshooting tools and techniques. Michael Niehaus and Keith Garner (both former Program Managers and Developers on the MDT project) provided a good overview at TechEd 2011 here: https://www.youtube.com/watch?v=J3d6PWZyutY . The content is valid for Windows 7 and above, and Windows Server 2008 R2 and above.

If you still have problems and wish to ask the forum, please be clear and specific. If the problem is on the client machine, can you share the relevant log files? Generally we don’t recommend adding the log files to the Technet Form post, bdd.log and smsts.log files can get quite large. Instead, use a public web service like SkyDrive. Create a public share, copy the log files there, and send a link to the folder.

What Log files should I share?

If you get to the end of the Windows Deployment, and you get the red [salmon] summary screen, share the bdd.log file. Typically found in c:\windows\temp\deploymentlogs (requires elevation to see this folder).

If the bdd.log file says that there was an error in the task sequence (error 0x80040005), then the task sequencer failed, share the smsts.log file too.

If you get an error during Windows Setup, share the panther logs. See article KB927521 for more information.

The Log files are hard to read!

MDT and SCCM log files are in a proprietary ML format. Use the cmtrace.exe tool provided in System Center Configuration Manager 2012 (SCCM) to view these log files formatted. This tool is a must have for any SCCM or MDT administrator.

Future FAQ items (Help contribute)
How can I customize MDT?

• What are Key/Vaule pairs in MDT (Cs.ini/database/webservice/wizard)
• How to write a VBScript/Powershell Script 
• How to debug scripts in MDT
• How to Extend the wizard
• http://channel9.msdn.com/Events/MMS/2012/CD-B412

What are the known issues of MDT 2013

How to debug/fix common problems:

• Issues with partitions and other disk issues.
• How to add a network driver to MDT.
• Errors within Windows Setup (Panther logs).
• Follow along with a full MDT OS Installation. With labels.

(Do not add any new questions to this post, they will be deleted! Create a new thread).

I've added the Lenovo SCCM driver package to MDT 2013 Update 1.

We've pushed out a build and all is fine and drivers are installed from DriverGroup001 except for the Intel Chipset drivers which are missing.

Lenovo SSCM driver package readme advises "Intel AMT driver, Intel Chipset, Intel Thunderbolt driver, Lenovo Monitor driver are not included in this package because .inf installation is not supported."

We installed the Intel Chipset drivers using .exe downloaded from Lenovo but how do I add the chipset driver to MDT "Out-of-Box Drivers"?

I've extracted the .exe which contains a setup.exe but if I extract that there are no .inf files.

I'm looking for some help here.  I'm using deployment workbench.

I have created a model custom image and created a custom wim file.  I have imported it into deployment workbench with source files in operating systems. 

I have created a task sequence pointing to that operating system.  When I do properties of the task then into the OS info then edit Unattend.xml, it gives me an error of "the specified image file did not contain a resource section". 

In addition, when I try to deploy this image to a computer, it fails.  I get the error:  Make sure the required files are available--setup failed to applying image\\server share...wim rc=31.  I'm wondering if this has to do with the issue above?  And not having an unattend.xml file.

I have deployed this image wim via Windows deployment services successfully.  Now I'm trying to integrate WDS with Deployment Workbench with this image wim and it fails. 

Any pointers would be great.

Rod

Greetings,

Let me first start with saying that SCCM will be ready to go in 2 to 3 months (waiting on paper work approvals etc) so I can only work with what I've got.

I only have MDT (they won't even let me use WDS but they will once SCCM is set).

For remote sites, I used the "Litetouch OEM Task Sequence".  This is used via USB flash drives and also by building a drive which becomes a self contained deployment share.

All runs great, however, I have to add, Windows 8.1 and Windows 10.

The "master" drive I use is a 60GB drive.  This makes it very quick when duplicating disks.

The issue, I duplicate a 60GB drive to a bunch of drive that are 250, 500GB etc, and those drives have the 60GB partition and the rest becomes unallocated spate.

I took care of extending the drive before when it was only Windows 7, by running Diskpart once it booted into the desktop and extending using the letter drive "C"

I can no longer get to the desktop because the drive runs out of space before it reaches it.

I'm thinking to Extend the drive, before the OS is applied probably in the install phase.

I was thinking to use DiskPart which fails, although I would like to extend the drive based on the label name "OSDisk". To ensure that I don't accidentally mess up a another unknown drive plugged in (its it could also be labels as OSDisk but less changes of this)

When I call diskpart I've used the following command line sequence step

cmd.exe /c %DeployRoot%\Scripts\Diskpart.exe /s %DeployRoot%\Scripts\Extend.txt

%DeployRoot%\Scripts\Diskpart.exe /s %DeployRoot%\Scripts\Extend.txt

Diskpart.exe /s %DeployRoot%\Scripts\Extend.txt

But none work and all have an generic errors.

If I run it manually form WinPE it successfully extends.

Question:

How should I run diskpart?

With PS Resize-Partition, I'm told that I can extend using the label name, howver, the help does not say I can.  How can I use PS to extend the drive?

Is there another method like WMIC?

Thank you

Hi,

I have a really annoying problem after i updated MDT 2013 U1 to MDT 2013 U2.

I uninstalled MDT 2013 U1 and installed MDT 2013 U2 instead and updated my deploymentshares and updated the boot images in WDS.

Now when i try to boot into my deploymentshare it gets stuck when it is loading the LiteTouchPE_x64.wim image. After like 20 seconds i get an error message "Windows failed to start. A recent hardware or software change might be the cause". Status: 0xc0000001. Info: A required device isn't connected or can't be accessed.

I have tried the following:

- Uninstall Windows ADK 8.1

- Updating Windows ADK 10 to version 1511

- Try on a different computer

- Put the LiteTouchPE_x64.ISO image to a USB key and boot from it.

- Try on a virtual machine with the LiteTouchPE_x64.ISO (HERE IT WORKS!)

- Tried to use WinPE 10 drivers instead of WinPE 5.0 drivers

- Tried changing the Maximum Block Size to 1024

I have tried Google and it doesn't seems like any other had this problem before.

Do you guys have a solution for me? it would be much appreciated. Because it is in our production environment.

https://social.technet.microsoft.com/Forums/getfile/778592

https://social.technet.microsoft.com/Forums/getfile/778594