FAQ

Behind the scenes stuff

How long does it take for the configuration to be applied?

Winget-AutoUpdate-Configurator relies on ADMX backed policies. So everytime Microsoft Intune syncs your device your settings should be applied to the systems registry. As soon as the Intune synchronization cycle is finished the configuration will be applied by the Winget-AutoUpdate-Configurator configuration task.

Are there log files?

Yes. There are two important log files:

• %PROGRAMDATA%\WinGet-AutoUpdate-Configurator\WinGet-AutoUpdate-Configurator.log: This file contains the logs from the WinGet-AutoUpdate-Configurator.
• %PROGRAMDATA%\Winget-AutoUpdate\logs: Here you find the Logs from WinGet-AutoUpdate.

New location with version 1.02.0003

With version 1.02.0003 and higher you can collect log files using Intune Collect Diagnostics from the device page. The logfiles are located in the folder FoldersFiles windir_temp_computername_log within the zip file and named:

• %COMPUTERNAME%-winget-autoupdate-configurator.log: This file contains the logs from the WinGet-AutoUpdate-Configurator.
• %COMPUTERNAME%-winget-autoupdate-updates.log: Here you find the Logs from WinGet-AutoUpdate.

Some applications fail to update. What can I do?

Please check out the original Winget-Autoupdate project since this issue since this project is only "consuming" WAU. These kind of issues reside within Winget-Autoupdate itself.

Why is WAU not updating itself?

Part of this project is code integrity. This means all files within this project are signed by using an authenticode signature. This way you can make sure that no malware or other stuff was injected into the code. If WAU would update itself the signatures will become invalid and would not run in environments that enforce code integrity. But WAU is serviced by WAUaaS so it will be patched with new releases of WAUaaS.