Setting up multiple Windows devices in a business or lab environment can often feel like a daunting task, especially when it comes to the manual configuration of each machine. Enter the Windows Configuration Designer, a tool designed to simplify this process by allowing users to create provisioning packages that automate device setup. From Wi-Fi settings to local accounts and domain joins, this tool streamlines the configuration process.
While the Windows Configuration Designer is readily available through the Microsoft Store, which suits many users, those who prefer a more streamlined approach may find command-line installations to be a cleaner alternative. For those who enjoy scripting deployments or wish to bypass the Store entirely, winget emerges as a faster and more efficient option, eliminating the need to sign into a Microsoft account.
What Windows Configuration Designer Actually Does
The Windows Configuration Designer, also referred to as ICD or Imaging and Configuration Designer, is Microsoft’s dedicated tool for creating provisioning packages. These packages, saved as .ppkg files, contain configuration settings that can be applied to Windows devices during or after the initial setup.
In practical terms, this means you can pre-configure essential elements such as network settings, local user accounts, device names, domain or Azure AD enrollment, installed certificates, and Start menu layouts for Windows 11 or 10. Instead of navigating through multiple wizards on each machine, a single run of the provisioning package takes care of everything.
The tool is not pre-installed on Windows systems, as most home users do not require it. It is primarily intended for IT administrators and deployment scenarios. While Microsoft includes it in the Windows Assessment and Deployment Kit (ADK), it can also be downloaded individually from the Store. However, it’s important to note that when searching for Windows Configuration Designer using the winget command, it must be enclosed in double quotes to appear correctly.
How to Install Windows Configuration Designer Using winget
Now, let’s delve into the installation process, which is quite straightforward. Here’s a step-by-step guide to ensure a seamless experience.
Step 1: Opening Your Terminal as Administrator
You can utilize either Command Prompt or PowerShell for this task. Personally, I prefer PowerShell, as it’s where I conduct most of my administrative work. To open it, simply right-click the Start button and select “Terminal (Admin)” on Windows 11, or search for PowerShell and run it as Administrator on Windows 10.
Step 2: Checking if Winget is Available
Most recent versions of Windows 11 come with the Winget package manager pre-installed. To confirm its availability, you can run the following command:
winget --versionStep 3: The Installation Command
Since Windows Configuration Designer is accessible via the Microsoft Store, it can also be installed using winget. Here’s how:
Here’s the command:
winget install "Windows Configuration Designer"Alternatively, you can use:
winget install --id 9NBLGGH4TX22 --source msstoreExplanation:
--source msstore→ Forces Winget to utilize the Microsoft Store9NBLGGH4TX22→ (optional) Microsoft Store Product ID for Windows Configuration Designer
Using the ID is often preferable, as package names can change, leading to potential confusion. The ID remains constant.
What Happens During Installation
Upon executing the command, Winget will locate the package in its repository, download it, and initiate the installation process. Progress indicators will appear in the terminal, and while the installer operates quietly, you may encounter a UAC prompt if you did not start as an administrator.
The download size is approximately 30 to 50 MB, making it relatively quick on a decent internet connection. The installation typically completes in under a minute, with Winget confirming success or reporting any errors encountered.
Do note that you may need to accept source agreements during your first use of Winget. A simple “y” will suffice to proceed.
How to Verify the Installation
To ensure that Windows Configuration Designer is installed and functioning correctly, follow these steps:
Click Start and type “Windows Configuration Designer.” If the app appears in the search results, click it to launch. The application will open to a project selection screen, allowing you to create new provisioning packages or access existing ones.
Command Line Verification
Alternatively, you can verify the installation via Winget:
winget list --name "Windows Configuration Designer"This command will display installed packages matching that name. If Windows Configuration Designer appears in the output, the installation was successful.
Version Check
Within the application, you can check the version of Windows Configuration Designer. This is particularly useful for confirming compatibility with specific Windows versions or ADK tools.
Alternative Installation Methods
While Winget is a robust option, there are alternative methods for installation that may suit your needs better.
Microsoft Store
For a straightforward approach, open the Microsoft Store app and search for “Windows Configuration Designer.” A simple click on Install will suffice. However, this method comes with some downsides, including account requirements and limited scripting capabilities.
Windows Assessment and Deployment Kit (ADK)
If your deployment work is extensive, you may already have the Windows ADK installed. Windows Configuration Designer is included as an optional component, providing a comprehensive toolkit for image management, USMT, and other deployment utilities. This route is advisable only if you require the additional ADK tools.
Offline Installation Limitations
True offline installation of Windows Configuration Designer can be challenging. The standalone app from the Store relies on MSIX packaging with dependencies that necessitate online activation. For air-gapped environments, the full ADK is the preferred option, as it can be downloaded once and installed offline.
When Winget Is the Best Choice—And When It’s Not
Each tool has its unique advantages. Here’s a breakdown of when to opt for Winget versus other alternatives.
Use winget when:
- You seek a quick, scriptable installation without the hassle of Store UI
- You are configuring multiple machines and desire consistent deployments
- You prefer command-line tools and want to avoid Microsoft account sign-in
- You need to document or audit your installation process
- You are working in a VM or test environment where clean installs are frequent
Use the Microsoft Store when:
- You are performing a one-time install on a machine where you are already signed in
- You favor graphical interfaces and do not mind a few extra clicks
- Automatic updates through the Store are a priority for you
Use the full ADK when:
- You require other ADK components such as DISM tools, USMT, or Windows PE
- You are operating in an offline or air-gapped environment
- Your organization has standardized on the ADK for deployment workflows
Frequently Asked Questions
Is Windows Configuration Designer free? Yes. It is a complimentary tool from Microsoft, accessible through the Store, Winget, or as part of the Windows ADK, with no licensing fees involved.
Does Winget require a Microsoft account? No. This is one of Winget’s key advantages, as it operates independently of any Microsoft account sign-in.
Can I use this on Windows Server? Winget is not officially supported on Windows Server editions, although it may work with manual installation of the App Installer package. For Server environments, the ADK is typically the better option.
Will Winget keep the app updated automatically? Not automatically. Users can check for updates by running “winget upgrade” and manually updating specific packages. The Store version, however, manages updates automatically.
What if I need to uninstall it later? You can uninstall it by running winget uninstall “Windows Configuration Designer” or through Settings > Apps, similar to any other application. Both methods are effective.