Q. How can I convert a version .9 Windows Imaging format (WIM) file to a 1.0 WIM file?

A. For early users of Systems Management Server (SMS) 2003 and the Operating System Deployment feature pack, an early version (version 0.9 ) of the WIM was used, which is not compatible with the tools and technologies designed to deploy version 1.0 WIM files.
A number of options are available to recapture these .9 WIM files to the 1.0 format, but there is no direct conversion tool.
One option is to use SMS Operating System Deployment feature pack to deploy the 0.9 WIM file to a disk and then recapture the content of the disk using the new tools, such as imagex from the Vista Windows Automated Installation Kit (WAIK). It's important to not let the machine reboot after deploying the .9 image or the mini-setup wizard will run and set SID/GUID information on the installation making it unsuitable for future deployment.
As an alternative option Jason Galbreath created a version of imagex that works with the .9 version of WIM, which lets you deploy the .9 WIM to disk and then capture the disk to a 1.0 version WIM using the Microsoft imagex tool. Goto http://www.mountain-webs.com to download his imagex utility. Jason also created some scripts to clean up the .9 image of any SMS information if you are also migrating to System Center Configuration Manager (SCCM). The basic process of what you need to do manually is:

1. Export the 0.9 WIM
2. Mount the software registry hive from the extracted WIM. Here are some sample commands:
REG LOAD HKLM\WIMSYS <EXTRACT PATH>\windows\system32\config\software
REG DELETE "HKLM\WIMSYS\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\OSDWinlogon" /f
3. Remove the file: \windows\system32\osdwinlogon.dll.
4. Compress in WIM 1.0.
Below is a script to perform the process automatically. It takes two parameters: The first is the source WIM file name without the .wim extension and the second is the path to extract the WIM to. I recommend using a short path for the second parameter, so you don't run into any max path problems. I use X: for my operations so the command file will use X:\MNT.

ECHO Converting image: %1
ECHO This will CLEAR AND USE the %2\MNT folder.
REM Remove esisting MNT folder
RD /S /Q %2\MNT
REM Export WIM info into an XML file
ImageX09.exe /info %1.wim 1 %2\%1.xml
REM Export WIM image into MNT folder
ImageX09.exe /apply %1.wim 1 %2\MNT
REM Remove OSDWinLogon items from registry
ECHO Removing old OSD hooks.
REG LOAD HKLM\WIMSYS %2\mnt\windows\system32\config\software
REG DELETE "HKLM\WIMSYS\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\OSDWinlogon" /f

REM Remove OSDWinLogon.dll from file system
ECHO OSD registry hooks are gone.
DEL /F %2\mnt\windows\system32\osdwinlogon.dll
ECHO Removal of OSD hooks is complete.

REM Capture new WIM image
ECHO Extraction and updating complete, please verify file copy in %2\MNT and XML information in %2\%1.xml.
ImageX.exe /compress maximum /capture %2\MNT %2\%1-SCCM.wim %1 %1
ECHO Compression of the WIM is complete.

REM Remove MNT folder and XML file
ECHO Removing MNT folder.
RD /S /Q %2\MNT
DEL %2\%1-SCCM.wim
DEL %2\%1.xml
ECHO WIM Operation Complete

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.