microsoft / microsoft/winget-cli
Dedicated HRESULT for Elevation Failure
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
Currently, when using WinGet's COM APIs to install an application that requires elevation, the resulting HRESULT is E_ABORT, same as any other "cancelation". It would be helpful to know from the result that the issue was elevation in particular.
Proposed technical implementation details
I would either have a dedicated HRESULT for elevation failure or use the Extended Error to indicate the reason for the E_ABORT
Contributor guide
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.
Research direction
Start by reviewing the WinGet COM API installation result handling, focusing on where elevation failures currently become E_ABORT. Compare the dedicated HRESULT and Extended Error proposals, and define completion as allowing callers to distinguish elevation failure from other cancellations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100