Romanitho / Romanitho/Winget-AutoUpdate

[Bug]: MSI product code changing during Update of WAU

Open
#1,031 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug stale
Dominant language
PowerShell
Stars
2k
Forks
194
Avg merge
22h 54m
Merged PRs (30d)
1

Description

The problem

WAU is changing its own MSI product code, e.g. between v2.5.2 ({4170A857-72E8-4A2D-9479-87E8EC28083C}) and v2.7.0 ({7D688100-F55E-48E2-BAF8-A9D568404E66}).
It's generally against MSI best practices to change the MSI product code for regular/minor updates, where a change of Version/DisplayVersion would be sufficient.
This behaviour causes several challenges, e.g. defining a reliable detection method in Intune or ConfigMgr, which should ideally also be able to execute a version comparision of the MSI. I am aware that not all software manufacturs take this matter serious and that there are alternate ways of detecting the software.

I changed detection to HKEY_LOCAL_MACHINE\SOFTWARE\Romanitho\Winget-AutoUpdate | Value: ProductVersion for now, in case anyone has the same issue.

What version of WAU has the issue?

2.7.0

What version of Windows are you using (ex. Windows 11 22H2)?

W11 24H2

What version of winget are you using?

1.11.430

Log information

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named in the report. Start by locating the MSI packaging configuration and compare the ProductCode and DisplayVersion metadata for WAU 2.5.2 and 2.7.0; done means regular updates retain the product code while the version changes, with the installer behavior verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.