microsoft / microsoft/winget-cli
Repair-WingetPackageManager deployment operations not marked as complete
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 Repair-WinGetPackageManager is called from within a script, the deployment operation of VCLibs is never marked as completed, causing the progress bars to remain on the screen when called within a script
Steps to reproduce
Within a .ps1 script, call Repair-WinGetPackageManager and ensure there are commands which will prevent the script from exiting after the repair has completed.
Install-PackageProvider -Name NuGet -Force | Out-Null
Install-Module -Name Microsoft.WinGet.Client -Force -Repository PSGallery | Out-Null
Repair-WinGetPackageManager
while ($true) {}
Expected behavior
VCLibs is marked completed after it is installed, and the progress bars disappear after Repair-WinGetPackageManager has completed
Actual behavior
Environment
Clean Windows Sandbox
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 with the Repair-WinGetPackageManager entry point and reproduce the issue using the provided .ps1 script in a clean Windows Sandbox. Observe the VCLibs deployment operation and progress bars while the script remains running. Done means VCLibs is marked complete and the progress bars disappear when Repair-WinGetPackageManager finishes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100