MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Proper Exit Codes/Return Codes Documentation
@Lakshmisha-KS is already working on this.
Since Feb 12, 2025.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem?
Since WinGet have gotten some popularity we've seen quite a few issues with the WebView2 installer, the most common one is requiring the terminal to be run as Administrator.
However we have no clue what any of the random Exit codes means because it is not Documented as you guys claimed in https://github.com/MicrosoftEdge/WebView2Feedback/issues/981
Describe the solution you'd like
Create a clear documentation of the exit codes for Microsoft Edge and WebView2.
For example what does exit codes 2147748098, 2147747880 and 2147748109 mean?
- Administrator Required
- downgrade
- alreadyInstalled
- packageInUse
- InstallInProgress
- fileInUse
- missingDependency
- diskFull
- insufficientMemory
- noNetwork
- contactSupport
- rebootRequiredToFinish
- rebootRequiredForInstall
- rebootInitiated
- cancelledByUser
- blockedByPolicy
And any Custom exit codes.
https://github.com/microsoft/winget-cli/issues/1824
https://github.com/microsoft/winget-cli/issues/1873
https://github.com/microsoft/winget-cli/issues/1883
https://github.com/microsoft/winget-cli/issues/1904
https://github.com/microsoft/winget-pkgs/issues/63886
https://github.com/microsoft/winget-pkgs/discussions/44812
https://github.com/microsoft/winget-pkgs/issues/63311
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.