microsoft / microsoft/winget-cli
Unable to accept Terms of Transaction remotely
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
When attempting to run winget for the first time; winget prompts to accept Terms of Transaction stating the reason: The source requires the current machine's 2-letter geographic region to be sent to the backend service to function properly (ex. "AB").
On a local machine, you type 'y' and hit enter. However, when running remotely winget does not wait for the input response and simply returns the prompt reporting error: 0x8a150042: Error reading input in prompt
Steps to reproduce
Execute winget remotely on a machine that has not run winget previously using either PowerShellRemoteSession or a PowerShell script.
Expected behavior
Enter [Y] or [N] to answer input prompt and input is accepted.
Actual behavior
winget does not wait for the input response and simply returns the prompt reporting error: 0x8a150042 : Error reading input in prompt
Environment
Windows Package Manager v1.3.2691
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19045.2364
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.2691.0
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
Reproduce the first-run Terms of Transaction prompt by running winget remotely through a PowerShellRemoteSession or PowerShell script. Start at the CLI's prompt and input handling for remote sessions, then verify that Y/N input is accepted remotely without error 0x8a150042 while local behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100