New package: NVIDIACorporation.NVIDIAapp version 1.0.14.0

[Barradel]

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• This PR only modifies one (1) manifest
• 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.6 schema?

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

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[og-mrk]

There's a warning in the Azure Pipeline, which indicates that Silent and SilentWithProgress is not sprcified for exe InstallerType, maybe look into other installer types found in the repo's docs, to be exact, the ones found inside doc/manifest/schema/1.6.0 folder.

But the main reason for why this fails is probably because this app expects Nvidia GPU to be available in the system. Otherwise, the Install will fail. Therefore, it's highly a hardware issue, further investigation should be taken by Contributors and Maintainers, if any of which have the time to spare on testing this PR.

[stephengillie]

Automatic Validation ended with:

Installation failed with exit code -1978335226
2024-03-02 09:18:04.212 [CLI ] ShellExecute installer failed: 3858759680

(Automated response - build 857.)

[Barradel]

Hi @stephengillie ! Like said @og-mrk, this fails is probably because this app expects Nvidia GPU to be available in the system.

[stephengillie]

Hi @Barradel,

Unfortunately yes, this appears to be the case:

• This sounds like a very similar situation to New package: Nvidia.NvidiaApp.Beta version 10.0.0.499 #140756

[og-mrk]

Hello @stephengillie, thanks for responding to this issue.
I'm wondering on a workaround.. Could we add ExpectedReturnCodes and some Context for User when this happens?
like the code snippet below

ExpectedReturnCodes:
  - InstallerReturnCode: 3858759680
    ReturnResponse: systemNotSupported

Or do we have to wait for winget-cli support for hardware to be implemented?

[Barradel]

Hello @stephengillie, thanks for responding to this issue. I'm wondering on a workaround.. Could we add ExpectedReturnCodes and some Context for User when this happens? like the code snippet below

ExpectedReturnCodes:
  - InstallerReturnCode: 3858759680
    ReturnResponse: systemNotSupported

Or do we have to wait for winget-cli support for hardware to be implemented?

Good idea!

[stephengillie]

Hi @og-mrk and @Barradel,

That's an interesting proposal - it might make a good Issue - to unblock Hardware labeled PRs by adding a warning when the hardware is not present. A problem here is that if the installer won't install in the validation pipeline, then it can't have Defender and other scans performed on it, which is a critical part of our process. Here is the Issue for upgrading the validation pipeline VMs to include OpenGL:

• Support OpenGL for package validation. #12906