Skip to content

updated the documentation on winget-installed WAU - #1144

Open
natsuwater wants to merge 2 commits into
Romanitho:developfrom
natsuwater:readme-for-winget
Open

updated the documentation on winget-installed WAU#1144
natsuwater wants to merge 2 commits into
Romanitho:developfrom
natsuwater:readme-for-winget

Conversation

@natsuwater

Copy link
Copy Markdown

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:

  • Clarify the installation path for winget users (C:\Program Files\Winget-AutoUpdate).
  • Distinguish between .msi installation and winget installation paths in the Configurations and Logs sections.
  • Add some details about the Scheduled Task (\WAU\Winget-AutoUpdate) that is automatically created upon installation.

I hope this helps other users!

> 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.
@natsuwater

Copy link
Copy Markdown
Author

In a Pull Request I submitted, a third party attached a file in a comment, not as part of the proposed changes.
The file appears to disguise an executable ELF binary as a text file or shell script and may raise security concerns.

Repository owner deleted a comment from tejavanka74-max Apr 21, 2026
@tejavanka74-max

tejavanka74-max commented May 19, 2026

Copy link
Copy Markdown

[content removed]

@AndrewDemski-ad-gmail-com

Copy link
Copy Markdown
Contributor

Account has been reported to GH support.

@DandelionSprout

Copy link
Copy Markdown

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:

@KnifMelti

Copy link
Copy Markdown
Collaborator

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

microsoft/winget-pkgs#401303 (comment)

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 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.

Comment thread README.md
Comment on lines +32 to +36
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.
Comment thread README.md
Comment on lines +47 to 52
**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 !-->

Comment thread README.md
### 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).
Comment thread README.md
### 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants