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

[LNI-BE]

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

[KnifMelti]

Yes, you're right in that MSI best practice is major.minor.build with Product Code only changing when increasing major version.
But, in reality not many MSI packages follow that standard.
And the variations are endless how a MSI is compiled.
Most of the Product Code change is done with Major Upgrade methodology, which can be appropriate depending on the scope of the changes between versions.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.