Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Package Issue]: icsharpcode.ILSpy 11.2.0.10050 — incorrect ProductCode for x64 MSI

Closed Beginner friendly
  • Is something wrong?
#463,775 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
powershell, yaml
Domain
release

Research direction

Open the linked manifest at manifests/i/icsharpcode/ILSpy/11.2.0.10050/icsharpcode.ILSpy.installer.yaml and compare both ProductCode fields with the x64 MSI's Property table. Verify ARM64 independently and check whether it needs installer-specific metadata. Done means the manifest metadata matches the corresponding installer; the issue provides the x64 MSI URL and checksum.

Written by the indexing model from the issue text.

Description

Needs-Triage
Please confirm these before moving forward
  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue

Other

Brief description of your issue

The icsharpcode.ILSpy installer manifest for 11.2.0.10050 contains a ProductCode that differs from the official x64 MSI.

Both ProductCode and AppsAndFeaturesEntries.ProductCode contain:

{A12FDAB1-731B-4A98-9749-D4817E9698E2}

The ProductCode read directly from the x64 MSI's Property table is:

{A12FDAB1-731B-4A98-9749-D4817EA699EE}

Manifest: https://github.com/microsoft/winget-pkgs/blob/master/manifests/i/icsharpcode/ILSpy/11.2.0.10050/icsharpcode.ILSpy.installer.yaml

Steps to reproduce

  1. Download the x64 installer:

    winget download --id icsharpcode.ILSpy --exact --version 11.2.0.10050 --scope user --architecture x64 --source winget --skip-dependencies

  2. Inspect ProductCode in the downloaded MSI's Property table.

  3. Compare it with both ProductCode fields in the linked manifest.

Actual behavior

The manifest contains {A12FDAB1-731B-4A98-9749-D4817E9698E2}, while the verified x64 MSI contains {A12FDAB1-731B-4A98-9749-D4817EA699EE}.

Expected behavior

The manifest's ProductCode metadata should match the corresponding MSI. Only x64 was checked; ARM64 should be verified independently, with installer-specific metadata if necessary.

Environment
Windows Package Manager v1.29.380
Windows: Windows.Desktop v10.0.26300.9711
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.29.380.0
Screenshots and Logs

Official installer: https://github.com/icsharpcode/ILSpy/releases/download/v11.2/ILSpy_Installer_11.2.0.10050-x64.msi

The downloaded MSI's SHA-256 matches the manifest:

1113E636564F085D9DA14DD736E10F73AA463FC28C6CBB400BD58885DFFD4208

A separate scope-detection problem was observed as described in https://github.com/microsoft/winget-cli/issues/3011. No causal relationship between that problem and this ProductCode mismatch has been established.

Dominant language
No language data
Stars
11.2k
Forks
11.3k
Avg merge
2h 44m
Merged PRs (30d)
646

Getting set up

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.

More from microsoft/winget-pkgs

All issues in microsoft/winget-pkgs

Similar issues

More Release issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.