microsoft / microsoft/winget-pkgs

[Package Issue]: Microsoft.EdgeWebView2Runtime

Open
#196,237 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Help-Wanted Issue-Bug Package-Metadata
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

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 value of the "ProductCode" Field in the Microsoft.EdgeWebView2Runtime.installer.yaml is no valid MSI Product Code:

Image

https://learn.microsoft.com/en-us/windows/win32/msi/product-codes

This Product Code will be written to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and is used to detect/uninstall applications by Software Management Systems.

So if there is no Product Code, or you don´t know it, please delete the field. We get an "application not found" after installation from our Software Management System because of this.

Steps to reproduce

no text

Actual behavior

no text

Expected behavior

no text

Environment
no text
Screenshots and Logs

no text

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

Open Microsoft.EdgeWebView2Runtime.installer.yaml and inspect the ProductCode field against the MSI product-code requirements linked in the issue. Confirm whether the value is valid; done means the manifest contains a valid ProductCode or omits the field when no valid code is known, followed by the repository's normal manifest validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
tooling
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.