Repository navigation
v2.5.83 - AWS CLI repair fixes
Fixes the AWS CLI repair instructions for machines where Winget reports a successful update but Chocolatey still fails.
Changes
- For the specific
Amazon.AWSCLI/awsclicase, the repair plan asks you to confirm the installed product, then offerschoco uninstall awscli -y --skip-autouninstaller --skip-powershellto remove Chocolatey's package record. You decide whether to run it. - Other AWS CLI failures point to
upd aws. Package IDs are checked before they appear in commands, and checksum failures require hash verification before a repair command is offered. - The updater now recognizes ordinary Winget success messages and remembers them after a reboot. Similar package names and preview editions are kept separate.
- The README starts with installation and the commands you'll actually use. Longer explanations are linked from there.
Testing
608 tests passed, along with the User/SYSTEM and launcher checks. The published installer also passed fresh-install and legacy-repair tests.
The interactive VM passed its checks after four update passes and three reboots. The headless VM completed five passes and three reboots, but deferred user-only updates and a Windows update that remained offered after installation. Both cleaned up their resume tasks and saved state. The overall VM result is PARTIAL, not a claim that everything was patched.
The Chocolatey test checked that uninstall scripts stayed suppressed and an external application file remained. It was not a live AWS publisher-rollover test. Full results, the initial launcher-exit caveat, and remaining coverage gaps are in the validation report.