WinGet can install the Open-Shell package by its exact package ID. First inspect the package metadata and source so a similarly named result is not selected accidentally. The repository package version can differ from a pre-release on GitHub.
What to do
- Open Windows Terminal and confirm winget is available. Run the show command for Open-Shell.Open-Shell-Menu with exact matching and the winget source.
- Review the displayed publisher, version, and installer URL before proceeding. A package name alone is not enough to establish that you have selected the intended application.
- Run the install command and follow the applicable prompts. For the first PC, an interactive installation makes component selection and elevation easier to understand than an unattended override.
- Open the installed menu settings and verify the resulting version. Apply a built-in menu style and check that Start opens under the intended Windows user.
winget show --id Open-Shell.Open-Shell-Menu --exact --source winget
winget install --id Open-Shell.Open-Shell-Menu --exact --source winget --interactiveCheck the result
Use the installed-app entry or the settings dialog to confirm installation. A package-manager message is not a substitute for testing the menu after sign-in.
Limits & precautions
This guide does not assume a particular WinGet manifest version is current. Read the output on your PC; stop if the ID or download origin does not match the project.
Questions & answers
What package ID should I inspect?
Open-Shell.Open-Shell-Menu is the project package ID used in the cited installation discussion.
Does WinGet always select a preview?
No. Package repository availability and GitHub release channels are separate.
Sources & scope
Documentation checked October 30, 2026. These instructions are documentation-led, not a claim of hands-on testing on your Windows build.