- Windows 11 introduces winapp CLI, a command-line tool for developers.
- Supports Electron, .NET/Win32, CMake, Python, and other frameworks.
- Simplifies app creation without Visual Studio or MSBuild.
On Windows 11, Microsoft has introduced the Windows App Development CLI (winapp CLI) to make it easier for developers to bring apps to the operating system.
Developers have long faced challenges with fragmented platforms, complex packaging, and inconsistent APIs, and this tool is designed to streamline the process, removing barriers for developers who want to create apps for Windows 11 without relying on Visual Studio or MSBuild.
The public preview of the Windows App Development CLI (winapp CLI) is now available. It supports cross-platform frameworks such as Electron, .NET/Win32, CMake, or Python, enabling developers to build apps more efficiently.
In this guide, I’ll outline the steps to install the Windows App Development command-line tool on Windows 11.
Install winapp on Windows 11
To install the Windows App Development command-line tool on Windows 11, follow these steps:
-
Open Start.
-
Search for Command Prompt or PowerShell, right-click the top result, and select the Run as administrator option.
-
Type this command to install the winapp tool on Windows 11 and press Enter:
winget install Microsoft.winappcli --source winget

Once you complete the steps, the command-line tool will install on your computer.
If you want to get started quickly, run this in your project root to generate initial configuration and resources:
winapp init

As you run the command, you’ll see on-screen instructions to set up the development environment, including package and publisher names, version, description, SDK setup, and more.
You can run this command to recreate the configured environment state, useful when cloning a project or syncing across machines:
winapp restore
It’s also possible to run this command to update packages and dependencies to the latest versions, based on your configuration:
winapp update
Other useful commands that you’ll be using include:
winapp create-debug-identity my-app.exe: Adds a temporary Package Identity to your executable for debugging features.winapp manifest update-assets path/to/logo.png: Generates or modifies the AppxManifest.xml file for your app.winapp cert generate: Generates and manages development certificates used for signing and local testing.winapp sign path/to/package.msix: Creates an MSIX package from your build outputs.winapp pack .\build\output --cert devcert.pfx: Creates the MSIX package ready for distribution.
You can use this GitHub page to learn more about usage commands.