[Package Issue]: Installation Validation fails for PureSync installer without diagnostic log

Nobody has claimed this yet.

### Please confirm these before moving forward

- [x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [x] I have not been informed if the issue is resolved in a preview version of the winget client.

### Category of the issue

Installation issue.

### Brief description of your issue

"No logs after 5 retries."
although with winget install --manifest ...
a log file is written properly

### Steps to reproduce

start a PR for PureSync

### Actual behavior

I have added a PR for PureSync 8.6.0:
https://github.com/microsoft/winget-pkgs/pull/425099

It concludes with error during installation validation.
But there is no info what error, or any details.
It has been posted:
"No logs after 5 retries."
but no more info or details (and I have askeed several times for help / more details in the PR thread.)

My installation works fine with
winget install --manifest ...
with the exact same manifest file I commited and the same installation file which is downloaded from the give URL.
And a log file is created properly.

So, how to get a detailes error description or info what eactly is not working, or how to solve that?
The exact command line parameters (for install and uninstall) would be useful.

(The installation exe is created with advanced installer)

Thank you

### Expected behavior

installation should work unattened fine as it does here o a test system (Win 11 25H2)

### Environment

```raw
Windows-Paket-Manager v1.29.290
© 2026 Microsoft. Alle Rechte vorbehalten.

Windows: Windows.Desktop v10.0.26200.9168
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.29.290.0
```

### Screenshots and Logs

_No response_

Start by reviewing PR 425099 and reproducing its installation-validation failure with the PureSync manifest and `winget install --manifest ...`. Compare the validation run with the reported local installation, then identify what diagnostic output is available; done means the failure exposes actionable details or the validation succeeds for the manifest.

Written by the indexing model from the issue text.