Starting with version 1.4.0, WIM Witch can now import and apply Language Packs, Features on Demand, and Local Experience Packs. This feature set has been a constant request from the original release of WIM Witch, and I am really happy to have finally delivered it.
There are known bugs, which are listed at the end of the post. There are also unknown bugs, which are not. Consider the new feature set as “Preview” for a little while. This release also has some minor UI tweaks, which will be detailed later in the post.
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.
Applying LPs, LXPs, and FODs
To determine the correctly corresponding version of these objects, WIM Witch requires a WIM file to have been already selected on the Source WIM tab. This allows WIM Witch to autodetect which version and operating system to use, and modifies the options presented accordingly.
Click on the Customizations tab. This pane contains the LP, LXP, and FOD controls, and is now the home for the .Net 3.5 package option, OneDrive Client update, as well as Updates enablement.
Check the box next to the item type to be included. The Language Packs and the Local Experience Packs will prompt with the familiar Grid View windows, allowing the user to select which of the previously imported packages will be used.
The Features On Demand selection button provides a list of the Windows Capabilities for the given Window Version. Select the Demanded Features needed.
With all of the options selected for, it should look something like this:
From this point, the selected LPs, LXPs, and FODs are ready and will be injected during the build process. They are now the first packages to be processed by WIM Witch, with Software Updates coming later in the process.
The .Net, OneDrive, and Updates check boxes on the Customization tabs provide the same functionality as they did when the resided in their previous locations.
Known Bugs and FYIs
-I haven’t yet incorporated the new variables into the Save/Load functions, so any configurations created with LP, LXP, or FOD cannot be saved. This also impacts command line users as CLI functionality uses save files to generate WIMs. This missing functionality will be coming soon.
-The importation process for all three object types has very little error correction, and none regarding the files and folders it is importing. Ensure the correct folders are referenced during this process.
-I didn’t test with the 1809 and 1903 LP and FOD files as I didn’t have access to them. While I have made every effort to ensure proper functionality, I haven’t tested with the specific files myself. Please let me know if something goes sideways.
-Windows Server 2019 should work with this process, but I have not tested any of these functions with Server sources. Windows Server 2016 will not be made available as an option because the LXP changes were made with 1809 (see the next point).
-With the introduction of LXPs in 1809, I will not be supporting 1803 or earlier builds of Windows 10 and Server as I don’t have the time to build support for a deprecated process.
-The Grid View windows need to have titles added to them. For the time being, enjoy reading the code that generated the query that created the display you are selecting objects from. 😊
-The “Updates” tab has been renamed “Updates Store”. This tab still contains the OSDUpdate and OSDSUS module controls, as well as the Updates downloading functionality, but it no longer contains the “Enable Updates” check box. This all behaves like previous versions. I am really looking forward to overhauling the “Updates Store” tab in the future.
-The bug that caused some users issues with importing from ISO may be finally been rectified. I stumbled across the error while developing the new feature set and derived a solution. If you have had issues with this problem in the past, see if this build resolves it.
Let me know what you think!