microsoft / microsoft/winget-cli
On a remote computer the install command do not work correct bevore you run winget local on the remote Machine (0x8a15000f)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
I try to install software remote with invoke-command on an Computer with Windows 11
There is an error:
Unerwarteter Fehler beim Ausführen des Befehls:
0x8a15000f : Von der Quelle benötigte Daten fehlen
If you login once on the remote machine and do anything with winget, then the remote Install comand works
Steps to reproduce
Server:
Invoke-Command -ComputerName xxx -ScriptBlock { winget install -e --id GIMP.GIMP --scope machine --source winget}
you get the Error : 0x8a15000f :
Login on Remote Computer xxx
Winget list
Got back to the server
Invoke-Command -ComputerName xxx -ScriptBlock { winget install -e --id GIMP.GIMP --scope machine --source winget}
it will work
Expected behavior
The software GIMP should be installed on the remote computer xxx
Gimp is only one example, the problem exist also with other software
Actual behavior
you get an errror:
wehn you log in on the remote machine as an administrator and type any winget command (e.g. Winget list )
and start the remote command again, it will work without problems
Environment
Windows-Paket-Manager v1.7.10861
Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.
Windows: Windows.Desktop v10.0.22621.3447
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.22.10861.0
WinGet-Verzeichnisse
-----------------------------------------------------------------------------------------------------------------------
Protokolle %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\Local…
Benutzereinstellungen %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\Local…
Verzeichnis für portierbare Links (Benutzer) %LOCALAPPDATA%\Microsoft\WinGet\Links
Portables Linkverzeichnis (Computer) C:\Program Files\WinGet\Links
Portierbarer Paketstamm (Benutzer) %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portierbarer Paketstamm C:\Program Files\WinGet\Packages
Portierbares Paketstamm (x86) C:\Program Files (x86)\WinGet\Packages
Installationsprogrammdownloads %USERPROFILE%\Downloads
Links
-----------------------------------------------------------------------------------------
Datenschutzerklärung https://aka.ms/winget-privacy
Lizenzvereinbarung https://aka.ms/winget-license
Hinweise von Drittanbietern https://aka.ms/winget-3rdPartyNotice
Startseite https://aka.ms/winget
Windows Store-Nutzungsbedingungen https://www.microsoft.com/en-us/storedocs/terms-of-sale
Administratoreinstellung Status
-----------------------------------------------------
LocalManifestFiles Deaktiviert
BypassCertificatePinningForMicrosoftStore Deaktiviert
InstallerHashOverride Deaktiviert
LocalArchiveMalwareScanOverride Deaktiviert
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the two Invoke-Command sequences on Windows 11 using WinGet 1.7.10861 and the listed App Installer version, comparing the first remote install with the one after running winget list locally. Start from the remote-command behavior and the 0x8a15000f output; done means identifying and correcting the first-run failure so remote installs work without an interactive local WinGet command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, powershell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100