updated the documentation on winget-installed WAU - #1144
Conversation
> 1. Clarify the installation path for `winget` users (`C:\Program Files\Winget-AutoUpdate`). > 2. **Added details about the Scheduled Task (`\WAU\Winget-AutoUpdate`) that is automatically created upon installation.** > 3. Distinguish between `winget` and manual installation paths in the Configurations and Logs sections.
|
In a Pull Request I submitted, a third party attached a file in a comment, not as part of the proposed changes. |
|
[content removed] |
|
Account has been reported to GH support. |
|
From what I can tell from personal testing and personal experience, doing a fresh WAU install from Winget does not install the scheduling service at all; I've submitted the following to hopefully make it do: |
|
There was a problem hiding this comment.
🟡 Changes recommended
The README introduces a few verified inaccuracies/inconsistencies (scheduled tasks count, config/list placement guidance) plus typos that should be corrected before merging.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Updates README.md to better explain Winget-AutoUpdate (WAU) behavior when installed via winget, aiming to reduce confusion around install paths, configuration locations, log locations, and the scheduled task created during installation.
Changes:
- Expanded the winget installation section and added a new “Automation” subsection describing the scheduled task.
- Reworked parts of the Configurations and Logs documentation to distinguish installation methods and paths.
- Performed various formatting/structure edits across the README.
File summaries
| File | Description |
|---|---|
| README.md | Documentation updates for winget install path, scheduled task info, and config/log location guidance |
Review details
Suppressed comments (2)
README.md:59
- The new BlockList/AllowList intro is both redundant (the sections already exist below) and conflicts with the later guidance by stating the lists must be placed next to WAU.msi. This also uses list-item headings ("- ####") which can render oddly in Markdown.
- #### BlockList
You can exclude apps from update job (for instance, apps you want to keep at a specific version or apps with built-in auto-update):
Add (or remove) the apps' ID you want to disable autoupdate to 'excluded_apps.txt'. (File must be placed in the same folder as WAU.msi).
README.md:92
- Correct spelling of “priviledged” and clarify that the install directory log path applies regardless of install method (it’s determined by INSTALLDIR).
You can find logs in install location, in logs folder for priviledged executions.
- For user runs (Winget-Install.ps1) a log file will be created at `%AppData%\Winget-AutoUpdate\Logs` .<br>
- For winget installed users: `C:\Program Files\Winget-AutoUpdate\logs`
- Files reviewed: 1/1 changed files
- Comments generated: 4
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| When installed, WAU automatically registers a scheduled task to handle updates in the background. | ||
|
|
||
| - **Task Name:** `Winget-AutoUpdate` | ||
| - **Location:** `Task Scheduler Library > WAU` | ||
| - **Behavior:** It triggers based on the default configuration (typically at logon or on a daily schedule) to keep your applications up to date without manual intervention. |
| **Important:** The file location depends on your installation method: | ||
|
|
||
| - **Installed via winget:** `C:\Program Files\Winget-AutoUpdate\` | ||
| - **Installed via .msi installer:** File must be placed in the same folder as WAU.msi | ||
| <!-- or possibly `C:\support\Winget-AutoUpdate\` is the default install location !--> | ||
|
|
| ### When does the script run? | ||
| WAU runs by default, at logon. You can configure the frequency with options (Daily, BiDaily, Weekly, BiWeekly, Monthly or Never). | ||
|
|
||
| WAU runs ,by default, at logon. You can configure the frequency with options (Daily, BiDaily, Weekly, BiWeekly, Monthly or Never). |
| ### System & user context | ||
| WAU runs with system and user contexts. This way, even apps installed on User's scope are updated. Shortcuts for manually run can also be installed. | ||
|
|
||
| WAU runs with system and user contexts. This way, even apps installed on User's scope are updated. Shorcuts for manually run can also be installed. |
Hi, thank you for this great tool.
I noticed that when WAU is installed via winget, the folder structure and file paths (installation directory, config, and logs) differ from those described in the current README.md. This can be confusing for new users.
Proposed Changes
updated the documentation to:
\WAU\Winget-AutoUpdate) that is automatically created upon installation.I hope this helps other users!