Open florian-de opened 3 months ago
@florian-de
Based on the logs, I see the WinGet version and the OS version:
2024-08-30 09:31:21.441 [CORE] WinGet, version [1.8.1911], activity [{E3D0EAC1-8071-452C-9321-F65596B67114}]
2024-08-30 09:31:21.443 [CORE] OS: Windows.Desktop v10.0.22631.4037
The error you correctly identified is:
2024-08-30 09:31:25.959 [CLI ] Failed to extract archive with code -2147417851
We'll have to look into exactly what that error is from the library we're using, and ideally, we can find a better way to expose a human readable error out of that if it makes sense and isn't a generic exception.
After taking a second look, I don't see that the private source returned any results:
2024-08-30 09:31:22.539 [REPO] Sending http GET request to: https://customerrepo00.azurewebsites.net/api/packageManifests/WFCD.WFInfo
2024-08-30 09:31:22.539 [REPO] Http GET request details:
GET / HTTP/1.1
Content-Type: application/json
User-Agent: winget-cli WindowsPackageManager/1.8.1911 DesktopAppInstaller/none
Version: 1.4.0
2024-08-30 09:31:22.568 [REPO] Response status: 204
2024-08-30 09:31:22.568 [REPO] Response details:
HTTP/1.1 204 No Content
Date: Fri, 30 Aug 2024 07:31:21 GMT
2024-08-30 09:31:22.568 [REPO] No results were returned by the rest source for package id: WFCD.WFInfo
Can you run the command again and specify the source by name to eliminate some of the other output related to the "msstore" source and the "winget" source?
It looks like the private source isn't returning a manifest for the query.
I think since the community repository has a package for WFCD.WFInfo, that might be what is getting downloaded.
@denelon
Thank you very much for your responses.
I did include a private WinGet source, but I didn't specify the source in the WinGet command. However, the WFCD.WFInfo package is indeed being pulled from the community repository. The purpose was to demonstrate that the same extraction error occurs with a public WinGet package containing a ZIP file, as it does with a private one. The goal was to show that the error is consistent across both scenarios.
@denelon
I have now read that for winget in system context the extraction method was set to TAR by default.
Can I define this in a settings.json when installing winget in the system context. If so, where is this settings.json. I couldn't find it when winget was installed as system.
Only founds this for WinGet installation in user context:
https://github.com/microsoft/winget-cli/blob/master/doc/Settings.md
Are you not able to modify the settings in the system context?
"installBehavior": {
"archiveExtractionMethod": "tar"
}
https://github.com/microsoft/winget-cli/blob/master/doc/Settings.md#archive-extraction-method
Cant find this path when Running in System Context
Are you not able to modify the settings in the system context?
"installBehavior": { "archiveExtractionMethod": "tar" }
https://github.com/microsoft/winget-cli/blob/master/doc/Settings.md#archive-extraction-method
Hello everybody,
I am also having this issue, specially with Teamviewer update, and I tried to configure the extraction method for both system and user context but it didn't help, and I still get the same issue.
I tried also deleting all versions of the package downloaded into C:\Windows\Temp\WinGet\defaultState but didn't help neither.
I have even try to unzip the file myself and run again the update, but it tries to unzip the file anyway.
Is there anything else that I could try?
Best regards
Cant find this path when Running in System Context
For me this file is in %LocalAppData%\Microsoft\WinGet\Settings\defaultState
Brief description of your issue
When attempting to install WinGet packages that contain zip files as the System User during a Packer Image Build, the extraction process fails, leading to an empty extracted folder. This issue occurs only with zip-based packages; other packages install successfully.
Steps to reproduce
Steps to reproduce:
Expected behavior
The zip package should be extracted and installed successfully
Actual behavior
The package is downloaded, but the extraction fails with the following error:
Environment