Skip to content

Commit

Permalink
Add section for exit codes in troubleshooting
Browse files Browse the repository at this point in the history
  • Loading branch information
mdanish-kh committed Jul 30, 2023
1 parent 1d73bc2 commit fbc6a67
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions hub/package-manager/winget/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,10 @@ If you need more comprehensive log files, that provide the complete communicatio

A list of known issues with sources and behaviors is kept up to date in the [Windows Package Manager Client repository](https://www.github.com/microsoft/winget-cli). If you encounter issues when using the winget tool, go [here](https://github.com/microsoft/winget-cli/tree/master/doc/troubleshooting) for troubleshooting.

## Exit codes

The winget tool returns exit codes to indicate success or failure of the command. A table of exit codes and their meanings is populated in the [Windows Package Manager Client repository](https://www.github.com/microsoft/winget-cli). If you want to know what an exit code means, go [here](https://github.com/microsoft/winget-cli/blob/master/doc/windows/package-manager/winget/returnCodes.md) to find out.

### Scope for specific user vs machine-wide

Not all installers support installing in “user” scope vs. “machine” scope consistently.
Expand Down

0 comments on commit fbc6a67

Please sign in to comment.