Major fix: Romanitho.Winget-AutoUpdate version 2.12.0

[Imre Eilertsen (DandelionSprout)]

📖 Description

Unless there's something I've monumentally missed out on, the WAU Winget package currently installs with a configuration that makes Winget Auto-Update fail to actually… well… auto-update.

So I've added additional InstallerSwitches based on the app's Readme to try to make sure that it does.

I also:

• Added 5½ tags.
• Replaced (c) → © for professionality.
• Added anti-Internal-Error-Dynamic-Scan measures.

✅ Checklist

• Signed the Contributor License Agreement
• Linked to an issue (if applicable)
  • Resolves #[Issue Number]

📦 Manifest Checklist

• Checked that there aren't other open pull requests for the same manifest update/change
• This PR only modifies one (1) manifest
• Validated manifest locally with winget validate --manifest <path> (validation guide)
• Tested manifest locally with winget install --manifest <path>
• Manifest conforms to the 1.12 schema

Note: <path> is the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

[wingetbot (wingetbot)]

Validation Pipeline Run WinGetSvc-Validation-146-401303-20260712-1

[wingetbot (wingetbot)]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

[Göran Axel Johannesson (KnifMelti)]

Unless there's something I've monumentally missed out on, the WAU Winget package currently installs with a configuration that makes Winget Auto-Update fail to actually… well… auto-update.

So I've added additional InstallerSwitches based on the app's Readme to try to make sure that it does.

Based on the README (https://github.com/Romanitho/Winget-AutoUpdate#when-does-the-script-run) WAU runs, by default, at logon.
This has been determined by its maker, Romanitho:

You really should have contacted him before this change that will affect this globalwide...

[Imre Eilertsen (DandelionSprout)]

I have consistently, over a period of more than a year, noticed that WAU, when installed completely fresh through Winget, does not install such a schedule by default.

[Göran Axel Johannesson (KnifMelti)]

If you click the little arrow down in the library to the left you'll se the WAU folder...

[Imre Eilertsen (DandelionSprout)]

…Oh.

Huh.

Well, there's a reason I often don't rule out "something I've monumentally missed out on", in case of situations like that (In fact I was genuinely unaware that Task Scheduler had app-specific subfolders). I concede on this and admit that you're right on this.

I'll submit a PR to revert the InstallerSwitches part soon enough.

[Göran Axel Johannesson (KnifMelti)]

I'll submit a PR to revert the InstallerSwitches part soon enough.

Or, take the discussion to its maker himself, Romanitho.
This could be a better standard...

[Imre Eilertsen (DandelionSprout)]

In similar circumstances this spring, often I would (or do) @ the app's admin if the admin was also the usual caretaker of the Winget package. Unfortunately as it would later turn out in this case, the «caretaker» part was not met, as v2.12.0 was first added to Winget by a user who was not associated with WAU that I know of (DaMn good B0t (@damn-good-b0t) if I saw right some hours ago).

Nevertheless, I know to learn from my blunders, I know how to take hints, and I'll certainly learn a lot from all this for the future.