The Microsoft.WinGet.CommandNotFound module is a feedback provider plugin for PowerShell. This feedback provider leverages the Windows Package Manager to provide suggestions for packages to install when a native command cannot be found.
The command-line predictor feature in PowerShell enables this module to display these WinGet packages as predictive suggestions.
The Microsoft.WinGet.CommandNotFound PowerShell Module is built on the IFeedbackProvider interface, which is available with PowerShell 7.4 or higher. To display prediction suggestions, you need PSReadLine 2.2.6 or higher.
- PowerShell 7.4 or above
- PSReadLine 2.2.6 or above
The following experimental features must be enabled:
PSFeedbackProviderPSCommandNotFoundSuggestion
They can be enabled by running the following commands:
Enable-ExperimentalFeature PSFeedbackProvider
Enable-ExperimentalFeature PSCommandNotFoundSuggestionNote
PSCommandNotFoundSuggestion is available by default on PowerShell 7.5 and above
PowerShell feedback providers and predictors are written in C# and registered with the PowerShell Subsystem Plugin Model. To learn more, see "How to create a feedback provider" and "How to create a command-line predictor".
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
You can configure your environment to build the module using the build.ps1 script.
.\build.ps1 -BootstrapAlso ensure PowerShell is configured properly as described in the Requirements section.
The module can be built by invoking the build.ps1 script directly. The script also allows for a -Configuration parameter for Debug and Release.
.\build.ps1 -Configuration DebugAfter building the module, it can be loaded from the src\bin\<Configuration>\net8.0 folder.
Import-Module .\src\bin\Debug\net8.0\Microsoft.WinGet.CommandNotFound.psd1Note
If a Microsoft.WinGet.CommandNotFound module is already loaded, you will not be able to load the newly built module.
You can open a new PowerShell session without a profile using pwsh -NoProfile, then try importing the newly built module to get around this issue.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.