Last week the Windows team released a revision to the Windows 10 Technical Preview. As many of you discovered, this new build does not play nicely with MDT 2013 Update 1 Preview. While the MDT Preview properly detects that Windows version 10 is in fact greater than 6 we had a number of bugs regarding the five digit build number (10041).
You may have also noticed that the Windows ADK for Windows 10 Technical Preview is no longer available on the Microsoft Download Center.
Here is your one-stop shop to get this all working again.
MDT Updated Content
Attached to this post (down below my name) is MDT1503.zip that includes the following files. Extract them and replace into the specified folders:
<InstallationDirectory>\Templates (by default the installation directory is C:\Program Files\Microsoft Deployment Toolkit)
(NOTE: any existing task sequences built on these templates will not include the revisions. Therefore, we recommend that you recreate any task sequences for deploying Windows 10 based on either of these templates.)
<InstallationDirectory>\Templates\Distribution\Scripts (so that any new deployment share picks up the updated scripts)
<DeployRoot>\Scripts (in other words, the Scripts directory of your deployment share)
Windows ADK for Windows 10 Technical Preview
The Windows 10 ADK is now available through the Windows Insiders program. Here is how to get it.
- Go to the Windows 10 hardware development site.
- Click "Download Windows 10 kits, tools, and code samples".
- Sign in (or "Get Started" if you are not already an insider).
- Under the "For developers" and "Build great hardware" headers, click "Install the hardware development kits".
- Under the "Customize, assess, and deploy Windows" header, click "Download the Windows ADK for Windows 10 Technical Preview".
Even if you previously installed the Windows 10 ADK from the Download Center, that was build 9933 so you need to upgrade the ADK to version 10041.
Use the right Windows PE
As of today, the 10041 OS build is digitally signed differently than the 10041 ADK build. This poses a problem when trying to use DISM to inject optional components from the ADK into the boot.wim from the OS source. (When you have a matching Windows OS in the deployment share MDT uses the boot.wim from that source. When they don't match MDT uses winpe.wim from the ADK.) To resolve this, we have to manually modify the deployment share settings to force it to pickup the Windows PE image from the ADK.
- Open Notepad, then open <DeployRoot>\Control\settings.xml (where <DeployRoot> is the path of your Deployment Share, C:\DeploymentShare by default)
- Find the <Boot.x86.UseBootWim> and <Boot.x64.UseBootWim> settings and change both values to False. For example:
(You will need to completely update the deployment share, but keep reading as there's one more thing you need to do first.)
There is a bug in the 10041 ADK where the Windows PE image does not include MSHTML.DLL which is required for the WinPE-HTA optional component, which MDT is dependent on for all of the beautiful deployment wizardry. Here is how to address that.
- Create an extra files folder for each architecture, for example: "C:\ExtraFiles\x86" and "C:\ExtraFiles\x64".
- On the properties of your deployment share, Windows PE tab, enter the path to the extra files folder created in step 1 (for example: C:\ExtraFIles\x86) into the Extra directory to add field. Repeat for the x64 platform.
(P.s., there's a fun MMC bug here if you open this tab and then click to another window, the MMC will stop responding and the processor spikes. You've been warned. Alternatively, manually edit the Settings.xml file to specify the paths in the <Boot.x86.ExtraDirectory> and <Boot.x64.ExtraDirectory> settings.)
- In each of the folders, create "Windows\System32\en-us" structures, for example: "C:\ExtraFiles\x86\Windows\System32\en-us" and "C:\ExtraFiles\x64\Windows\System32\en-us"
- Copy the MSHTML.DLL from C:\Windows\System32 of a 64-bit Windows installation (build 10041) to "C:\ExtraFiles\x64\Windows\System32". Copy the MSHTML.DLL.MUI file from C:\Windows\System32\en-us to "C:\ExtraFiles\x64\Windows\System32\en-us".
- Copy the MSHTML.DLL from C:\Windows\System32 of a 32-bit Windows Installation (or from the C:\Windows\Syswow64 folder of a 64-bit installation) to "C:\ExtraFiles\x86\Windows\System32". Copy the MSHTML.DLL.MUI file from C:\Windows\System32\en-us (or C:\Windows\Syswow64\en-us) to "C:\ExtraFiles\x86\Windows\System32\en-us".
- Update your deployment share (completely).
With all of these workarounds in place your MDT 2013 Update 1 Preview experience can continue with Windows 10 Technical Preview build 10041.
— Aaron Czechowski, Senior Program Manager
This posting is provided "AS IS" with no warranties and confers no rights.