issues
search
microsoft
/
winget-command-not-found
WinGet Command Not Found is a PowerShell 7 module to help you install missing packages. With this module, you will be recommended relevant WinGet packages whenever an unrecognized command is entered.
MIT License
19
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
If not connected to the Internet, Powershell v7.4.3 might failed to start with the `Winget.CommandNotFound` installed.
#12
neville-studio
opened
1 week ago
1
`Microsoft.WinGet.CommandNotFound` version 1.0.3.0 fails to install
#11
kborowinski
closed
2 weeks ago
1
Handle unhandled exceptions in WarmUp()
#10
carlos-zamora
closed
3 weeks ago
0
`Microsoft.WinGet.Client.Engine` throws `Failedtocreateinstance`
#9
carlos-zamora
closed
3 weeks ago
0
Unhandled exception in WarmUp() method on PowerShell exit
#8
kborowinski
closed
3 weeks ago
2
Error not properly handled. Powershell will exit - [process exited with code 3762504530 (0xe0434352)]
#7
KDAM71
closed
3 weeks ago
6
Update README with experimental features and proper module name
#6
carlos-zamora
closed
1 month ago
0
Force version to be 1.0.2.0
#5
carlos-zamora
closed
1 month ago
0
Increase version and remove non-existent release notes
#4
carlos-zamora
closed
1 month ago
0
Can't retrieve suggestions when PowerShell installed from MSIX or Microsoft Store
#3
carlos-zamora
opened
1 month ago
0
Action required: migrate or opt-out of migration to GitHub inside Microsoft
#2
microsoft-github-policy-service[bot]
closed
1 month ago
3
Initial release of the source code
#1
carlos-zamora
closed
1 month ago
3