Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proper Exit Codes/Return Codes Documentation #2515

Open
OfficialEsco opened this issue Jun 11, 2022 · 4 comments
Open

Proper Exit Codes/Return Codes Documentation #2515

OfficialEsco opened this issue Jun 11, 2022 · 4 comments
Assignees
Labels
feature request feature request tracked We are tracking this work internally.

Comments

@OfficialEsco
Copy link

OfficialEsco commented Jun 11, 2022

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 #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.


microsoft/winget-cli#1824
microsoft/winget-cli#1873
microsoft/winget-cli#1883
microsoft/winget-cli#1904
microsoft/winget-pkgs#63886
microsoft/winget-pkgs#44812
microsoft/winget-pkgs#63311

AB#39989573

@OfficialEsco OfficialEsco added the feature request feature request label Jun 11, 2022
@ajtruckle
Copy link

Relates to my issue I think? #2473

@victorthoang victorthoang added the tracked We are tracking this work internally. label Jun 13, 2022
@victorthoang
Copy link

Thanks for the feedback! We've added this as a scenario on our backlog!

@caoimhebyrne
Copy link

Is there any update on this? @victorthoang - this would be quite useful.

@victorhuangwq victorhuangwq self-assigned this Jan 16, 2024
@victorhuangwq
Copy link
Collaborator

This issue is still being tracked, but as of now we do not have any updates about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request feature request tracked We are tracking this work internally.
Projects
None yet
Development

No branches or pull requests

6 participants
@victorhuangwq @ajtruckle @OfficialEsco @victorthoang @caoimhebyrne and others