New version: LieberLieber.LemonTree version 4.2.2

[aschoelzhorn]

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue? If so, fill in the Issue number below.
  • Resolves #[Issue Number]

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.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-132-338265-20260210-1

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-132-338265-20260211-1

[aschoelzhorn]

The installer works locally and winget validate + winget install --manifest both succeed. The automated test seems to fail for reasons I cannot reproduce. Could someone from the team review or rerun the validation?

[stephengillie]

Automatic Validation ended with:

Installation failed with exit code -2147467260
2026-02-11 05:41:03.600 [FAIL] C:__w\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(85)\WindowsPackageManager.dll!00007FFD04B775B6: (caller: 00007FFD04B78A32) LogHr(1) tid(1e24) 80D02013

Hex	Dec	Inverted Dec	Symbol	Description
80004004	-2147467260	2147500036	E_ABORT	Operation Aborted

(Automated response - build 1218.)

[aschoelzhorn]

@stephengillie
The piece of log does not help at all. Do you have the complete log file of the installation? Does the installation even start?
The error in "DODownloader.cpp" suggest an error when downloading?

We have no issues with the installer itself (locally, in out test environment, at our clients).
winget validate and winget install --manifest both succeed locally.

For me it seems that the issue is pipeline releated

[wingetbot]

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