Issue #1: SYSTEM context doesn't work / "Issue #2: No User-Context Trigger

[kjbears]

I am trying to deploy Winget-AutoUpdate via Intune. Now I've met several issues while trying to do so. I'll give a short description regarding my deployment process:

The image below shows the configuration of the deployment of Winget-AutoUpdate via the WAU.msi file under the Apps feature of Intune:

I also uploaded the ADMX and ADML files in order to control the configuration of the Registry values and keys via Intune - remotely.

Here are the Scheduled Tasks it has created:

Now I'll describe the issues I've encountered:

1. First of all, for some unknown reason, whenever winget-upgrade.ps1 is ran in the SYSTEM context (Winget-AutoUpdate scheduled task) it just keeps on failing... One of the issues happened because a proxy parameter was missing in the Test-Network.ps1 file under the functions folder. So I've added it at the correct place:

The SYSTEM context doesn't have access to the Proxy settings configured for the user in the Windows settings (Winkey --> proxy) and this is why it would fail and show an error like "No internet Connection". All traffic to the internet goes through the proxy in our organization so no wonder it failed. Can WAU be made to work reliably in SYSTEM context in proxy environments? Do I need to create a PS script to add the proxy configuration? However even after fixing this issue, it would still fail but for a different reason. It seems like the SYSTEM context doesn't have access to winget.exe... Ideally, I would like for Winget-AutoUpdate to work in SYSTEM context and run for all users even if they don't have admin privileges. I'll show you a snippet from the logs:

It says that the Prerequisites checked failed, though earlier it succeeded in SYSTEM context so I don't know what's causing this, but the main issue is this part:

"Failed when opening source(s); try the 'source reset' command if the problem persists."
"An unexpected error occurred while executing the command:
0x8a15000f : Data required by the source is missing"

I tried solving it by running the command mentioned above but it wouldn't help.

2. The second issue I've been trying to solve is how to configure Winget-AutoUpdate to run in user-context automatically via Intune. Since SYSTEM context has failed I thought maybe I could at least run it in User-Context so administrators could have their apps updated. But I haven't found a built-in way to configure this. It always runs only in SYSTEM context. I guess I could create a new scheduled task that runs it in the User-Context, but I was wondering if there is any better way to implement this. Does WAU officially support creating user-context triggers via MSI or ADMX?

In user context it works fine:

Additionally, I thought about using the Winget-AutoUpdate-Intune version since it contains an admx file that lets you configure the whitelist from Intune, but the msi file of that repo isn't signed and it shows a warning. Which msi file should I use?

Please help me fix these issues!

Best regards everybody,
Eden

[KnifMelti]

Hello there!
The WinGet fail I don't have any suggestions on.

But:
Great you could solve it with your Proxy!

With this being the only parameter: the result of the installation is this (from a maybe coming tool):

You then supply a whitelist locally:

In the Configuration settings you must enable Activate WAU GPO Management to be able to control WAU from GPO:

As you can see you can configure the whitelist in WAU too, but then you must point the list to GPO:

That you do in GPO itself:

The task responsible for noting that it should be GPO controlled is:

So until Activate WAU GPO Management is activated and that the Task has run it isn't controlled

[KnifMelti]

Forgot your second issue: install with USERCONTEXT=1 or edit the registry ([EDIT] or get your GPO working!)
https://github.com/Romanitho/Winget-AutoUpdate?tab=readme-ov-file#advanced-installation

[KnifMelti]

Can WAU be made to work reliably in SYSTEM context in proxy environments? Do I need to create a PS script to add the proxy configuration?

You can make a PR in this repo yourself with the code needed