New package: ASIX.AX88179DriverSetup version 2.0.3.0

[DandelionSprout]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue?

Manifests

• 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.10 schema?

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

---

Notes from me:

• An ARM64 driver also exists, but it is not part of the setup tool, and creating manifests for any of the standalone driver downloads on that page (e.g. https://www.asix.com.tw/en/support/download/file/1903) fails with the error "No supported installer(s) found in zip archive", as they contain only the driver .inf and not any executables.
• ASIX lists separate setup tools for Windows 11 and Windows 10; the latter is numbered as 2.0.2.0. I went with only the Windows 11 setup tool in this PR.

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-65-267997-20250624-1

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-65-267997-20250624-2

[stephengillie]

Verify:

• The scan step, which launches all EXEs, caused the validation VM to use about 20 GB of RAM.
  
  VCRedist might be a dependency.
  
  Since the application seems to display version 3.22.3.0, while the installer writes 2.0.3.0 to the Registry, should a DisplayVersion property be added to the manifest?

[DandelionSprout]

• "(…), should a DisplayVersion property be added to the manifest?"

I guess so, though it's not a property I've tried to use before.

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-65-267997-20250625-1

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-65-267997-20250625-2

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-65-267997-20250625-3

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-65-267997-20250625-4

[ItzLevvie]

@wingetbot run

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-65-267997-20250701-1

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.