Update version: Fangyuan025.Chaty version 1.8.3

[Fangyuan025]

• 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>? (authored per the 1.10.0 schema; no Windows machine available for local validation — relying on pipeline validation)
• Have you tested your manifest locally with winget install --manifest <path>? (see above — the installer is the signed Inno Setup build from the project's CI releases)
• Does your manifest conform to the 1.10 schema?

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-148-403170-20260716-1

[Fangyuan025]

@microsoft-github-policy-service agree

[stephengillie]

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Chaty\chaty.exe returned exit code: -1073741515

Hex	Dec	Inverted Dec	Symbol	Description
C0000135	-1073741515	3221225781	STATUS_DLL_NOT_FOUND	Possibly due to a missing dependency. (The most common dependency is Microsoft.VCRedist.2015+.x64 / .x86).

(Deterministic automation - build 1784.)

[stephengillie]

@wingetbot run

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-148-403170-20260716-2

[stephengillie]

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Chaty\chaty.exe returned exit code: -1073741515

Hex	Dec	Inverted Dec	Symbol	Description
C0000135	-1073741515	3221225781	STATUS_DLL_NOT_FOUND	Possibly due to a missing dependency. (The most common dependency is Microsoft.VCRedist.2015+.x64 / .x86).

(Deterministic automation - build 1784.)

[Fangyuan025]

Thanks for the triage @stephengillie. Added Microsoft.VCRedist.2015+.x64 as a package dependency — the exe links the dynamic CRT, so that matches the STATUS_DLL_NOT_FOUND on a clean image.

One more heads-up for validation: Chaty enables Vulkan GPU acceleration (llama.cpp backend), so the binary also imports vulkan-1.dll, which ships with GPU drivers rather than Windows itself. On a GPU-less validation VM the executable may still fail to launch even after the VCRedist dependency, while working normally on physical machines. Happy to follow whatever process you use for GPU-dependent apps.

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-148-403170-20260716-3

[stephengillie]

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Chaty\chaty.exe returned exit code: -1073741515

Hex	Dec	Inverted Dec	Symbol	Description
C0000135	-1073741515	3221225781	STATUS_DLL_NOT_FOUND	Possibly due to a missing dependency. (The most common dependency is Microsoft.VCRedist.2015+.x64 / .x86).

(Deterministic automation - build 1784.)

[Fangyuan025]

Updated the manifests to 1.8.3, which bundles the Vulkan runtime loader (vulkan-1.dll) next to the executable. Together with the Microsoft.VCRedist.2015+.x64 dependency added earlier, the app now starts cleanly on machines without a GPU driver — this should resolve the STATUS_DLL_NOT_FOUND launch failure seen in automated validation.

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-148-403170-20260717-1

[stephengillie]

Verify:

[wingetbot]

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