Windows-To-Go creation tool (Wtgcreator.exe) does not recognise WIM file

Introduction

The Windows-To-Go creator tool (Wtgcreator.exe) is responsible for imaging a Windows-To-Go USB drive with a Windows Image (WIM) file.

This WIM file may be:

  • Taken from a Windows 8.1 original ISO image
  • A customised WIM image created using Configuration Manager or the Microsoft Deployment Toolkit (MDT)

To use the tool you simply:

  • Plug in your certified USB device
  • Start the Windows-To-Go Wizard
  • Highlight your USB key and click Next
  • Click ‘Add Search Location’ and provide a directory where the WIM file lives
  • Select the correct WIM and begin the imaging process

The problem

When running through the Windows-To-Go creator wizard, no custom WIM files (even though they exist) are listed which prevents imaging.

WTGCreator

Selecting a stock WIM file from the original ISO however works.

The Workaround

Use the DISM command to mount the WIM image to a temporary directory:

"DISM.exe /Mount-Wim /WimFile:C:\images\myimage.wim /index:1 /MountDir:C:\images\mount"

Close the WIM with the commit flag:

DISM.exe /Unmount-Wim /MountDir:C:\images\mount /commit

I don’t know why this works yet, but it does solve the immediate issue.

One interested thing to note is that the WIM file is now around 10MB larger.

Curious….

Advertisements

Missing Network Card when booting a MDT 2008 WinPE image within VMWare.

As per usual, make sure that you back everything up before making changes to your system. I am not responsible for your stuff ups!

I was attempting to deploy an image created with MDT 2008 (Microsoft Deployment Toolkit) to a VMWare virtual machine. After PXE booting my WIM image, Windows PE did not have a network card present that could talk to the deployment server (It worked first time using Citrix XenServer!)

Here is my test environment;

I have created two virtual machines on a test VMWare ESXi box.
VM One has Windows 2003, MDT 2008 and Windows Deployment Services.

VM Two is the VM I am attempting to build via MDT installed on VM one.

After mucking around with injecting the vmware drivers, changing the network card type and recreating WIM’s ad infinitum, I found out the the VMX file for the test VM was missing a couple of essential entries.

Adding the following lines worked for me;
ethernet0.startConnected = “true”
ethernet0.virtualDev = “e1000”
ethernet0.addressType = “generated”

I made the changes, uploaded them using the data store browser, started the VM, and voila!