DanielSchnabel.Chatterino version 2.3.2

[seriousm4x]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @seriousm4x,
During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches?

This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest.

Please investigate a fix and resubmit the Pull Request.

You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect then the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress.

[seriousm4x]

During the installation a window for the C++ runtime pops up, where you can choose to install C++ runtime or just close the window if you already installed it.

This causes the validation to fail. How should that be handled?

[denelon]

@seriousm4x if you would prefer, we can label the PR with "Blocking-Issue" and "Dependency" to keep the work you've done on the manifest, When we implement those pesky, blocking issues, we will attempt to approve the PRs.

[seriousm4x]

sounds good to me