WIM Witch is a utility that can be used to update and modify WIM files for Windows deployment scenarios. She currently supports the following:
- Integration into Configuration Manager
- Apply Software Updates
- Apply Drivers
- Apply Autopilot Profiles
- Apply Registry Keys
- Apply Default App Association
- Apply Start Menu Layout
- Apply Language Packs, Local Experience Packs, and Features on Demand
- Apply .Net 3.5
- Remove in-box provisioned apps apps
- Create content for ConfigMgr Upgrade Package
- Create updated bootable ISO
- Pause build process for manual customization
- Run custom PowerShell scripts for additional functionality
- Command line support for automation tasks
WIM Witch supports servicing Windows 10, Windows Server 2016 and 2019 images. For more information, please read the documentation listed in the Documentation Tab.
To Install WIM Witch, open PowerShell and run the following command:
Save-Script -Name WIMWitch -Path [folder to save file in ex: "c:\temp"]
Then run the downloaded WIMWitch.PS1 as an admin and follow the prompts.
- When switching from Update Existing Image to New Image on the ConfigMgr tab, the list box for DP’s is not cleared. The entries can be removed with the remove button, but it may be advisable to close WIM Witch and reload if the list box does not clear as desired.
- The path field on the Make It So tab does not allow the user to browse for a UNC path. I’ll be working on this as the current workaround is a little hokey.
- Source path for Features On Demand contain an extra “”. This does not cause a problem, and will be cleaned up in the future
Found a bug? Tweet or DM me! @TheNotoriousDRR
WIM Witch can be installed on Windows 10, 2012 R2. Server 2016, and Server 2019.
PowerShell v5.1 is required.
The script will need to be run “As Administrator”
Windows 10 ADK / Deployment Tools – Only required if building ISO’s
Running WIM Witch on Server 2012 R2
If using Server 2012 R2, PowerShell may need to be upgraded. This can be done by installing version 5.1 of the Windows Management Framework.
If using Server 2012 R2, PowerShell may have trouble connecting to the PowerShell Gallery due ended support for TLS 1.0/1.1. Please see the following article to resolve the issue.
Installing WIM Witch
WIM Witch can now be installed from the PowerShell gallery. Use the following command to get it:
save-script -name wimwitch -path [your download folder] -force
To get started, simply run the script with Administrative rights. WIM Witch will start a pre-flight check to see if its folders exist in the folder that the script was run. If it doesn’t detect any of its folders, it will start the installation routine.
At the prompt, select “Y” for “yes” or “N” for “no”. If “N” is selected, WIM Witch will then ask for the folder that it should install to.
Sometimes the browse window loses the focus and becomes “hidden” behind active screens. If the window doesn’t spawn, minimize all windows to find it.
WIM Witch will create several folders and will copy itself to the path specified. Once this operation is complete, WIM Witch will exit. Please then run WIM Witch from the newly installed location.
Upon starting, WIM Witch will always check to see if its folder structure is present and will replace any folder that is missing.
Importing WIM and .Net 3.5 Files
WIM Witch provides a mechanism to import Install.wim and .Net 3.5 files into its folder structure. When applying .Net 3.5 to an image, prior importation will be required as WIM Witch cannot download the .Net files Microsoft directly. Importing Install.wim files is optional, but may be beneficial.
To import, start on the “Import Tab”
Press the “Select” button and browse to the ISO file that contains the files that should be imported. It should be noted that WIM Witch cannot import from an already mounted image; only ISOs. Once the ISO file is selected, check the box for the items that should be imported. If “Install.wim” is checked, the field to supply the name for the imported “Install.wim” file will now be accessible. Provide a unique name for the file. .Net 3.5 Binaries do not require any additional configuration.
Once the proper check boxes and fields have been completed, click “Import” to start the process.
During the importation of the .Net binaries, if the required subfolders do not exist, WIM Witch will create them automatically.
Import ISO Binaries
To get started, the binaries for the ISO will need to be imported. On the Import WIM tab, simply put a check mark in the ISO/Upgrade Packaged check box, select a source ISO, and then click import. This will copy all the files in the ISO, except the WIM file which should be imported with the Import WIM function. WIM Witch will determine if the ISO is Windows 10 or Server, and which version.
Start WIM Witch and select the “Import LP+FOD” tab. Select the type of import (Language Pack, Local Experience Pack, or Features On Demand), the Windows OS, and the corresponding version that you wish to import. At this time, WIM Witch is unable to determine the corresponding version of Windows from these binaries alone, so an accurate selection of the intended version is required.
Once the required data points have been entered, click the “Select” button to browse to the source.
LP,LXP, and FOD importation does not import directly from a ISO file like the WIM importation process does. The ISO file will need to be mounted or extracted for WIM Witch to import.
Importing Language Packs
Select Language Packs in the Object Type drop down, then select the version of Windows. Then, click the “Select” button.
Browse to the \x64\langpacks folder in the Language Pack media and select this path. WIM Witch does not support x86 images, so ensure x64 is selected.
Once the folder has been selected, the path will be queried for content and the result will be displayed in a Grid View window.
Select the Language Packs that will be needed for image creation, then click OK.
The selected files will be displayed in the “Selected Items” window on the “Import LP+FOD” tab. Ensure the files have a CAB file extension. Click the Import button to begin the importation process.
Importing Local Experience Packs
To import Local Experience Packs, select Local Experience Pack in the Object Type drop-down, along with the corresponding OS and Version number. Once configured, click the “Select” button and browse to the LocalExperiencePack source folder. Ensure the LocalExpereincePack folder is selected and not one of its many subfolders.
Once the source path has been selected, a Grid View will be displays a list of the Local Experience Packs that can be imported from the source. Select the needed packs and click OK. The LXP’s will be displayed in the Selected Items window in the Import “LP+FOD” tab.
Click the “Import” button to start the importation process.
Importing Features On Demand
To import Features on Demand, change the Object Type to Features on Demand and select the corresponding OS and Version. Click the “Select” button to select the import source folder.
Select the root of the mounted ISO or source folder.
Unlike the Language Packs and Local Experience Pack, WIM Witch does not provide the user with an option to select packages. Instead it copies the entire contents of the Features On Demand source to its import folder.
Click Import to start the importation process. There are a lot of files that will be copied, so this process will take longer than the other types.
Starting at the “Source WIM” tab, click the “Select” button. Browse to the WIM file that will serve as the base for the image build.
After selecting the WIM file, a Grid View window should appear:
Select the edition / index of Windows 10 that will be used. Click “OK”.
WIM Witch will take a small amount of time to analyze the selection and extract relevant information. When the processing is complete, the fields will be populated.