Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is winget down at the moment? #3153

Closed
ZedNg opened this issue Apr 14, 2023 · 3 comments
Closed

Is winget down at the moment? #3153

ZedNg opened this issue Apr 14, 2023 · 3 comments
Labels
Command-Source Issue related to WinGet Source Issue-Bug It either shouldn't be doing this or needs an investigation.
Milestone

Comments

@ZedNg
Copy link

ZedNg commented Apr 14, 2023

Brief description of your issue

Been trying to run a winget import for the last 3 hours and it keep failing to get to the winget source. I tried going to the source from the browser and it says its down?

Steps to reproduce

Winget import

Expected behavior

Installing my list of apps.

Actual behavior

0x8a15000f : Data required by the source is missing

Environment

1.4.10173
Windows 10 Home
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label Apr 14, 2023
@keithzg
Copy link

keithzg commented Apr 14, 2023

I was able to make a system getting that exact same error message by running the following from an elevated PowerShell session (having used SSH to get into the Windows 10 Pro install in question), cribbed from #2434 (comment):

cd Downloads
Invoke-WebRequest 'https://cdn.winget.microsoft.com/cache/source.msix' -OutFile '.\Microsoft.Winget.Source.msix' -UseBasicParsing
Add-AppxPackage -Path 'Microsoft.Winget.Source.msix';

I can't really explain why that works, but it has worked on three different Windows machines for me now (two on 10, one on 11).

@stephengillie stephengillie added Issue-Bug It either shouldn't be doing this or needs an investigation. and removed Needs-Triage Issue need to be triaged labels Apr 14, 2023
@ZedNg
Copy link
Author

ZedNg commented Apr 17, 2023

I was able to make a system getting that exact same error message by running the following from an elevated PowerShell session (having used SSH to get into the Windows 10 Pro install in question), cribbed from #2434 (comment):

cd Downloads
Invoke-WebRequest 'https://cdn.winget.microsoft.com/cache/source.msix' -OutFile '.\Microsoft.Winget.Source.msix' -UseBasicParsing
Add-AppxPackage -Path 'Microsoft.Winget.Source.msix';

I can't really explain why that works, but it has worked on three different Windows machines for me now (two on 10, one on 11).

ya that worked... but that is so strange.

@ZedNg ZedNg closed this as completed Apr 17, 2023
@ZedNg ZedNg reopened this Apr 17, 2023
@denelon denelon added this to the v.Next-Client milestone Jun 5, 2023
@denelon denelon added the Command-Source Issue related to WinGet Source label Jun 10, 2023
@denelon
Copy link
Contributor

denelon commented Mar 6, 2024

This appears to have been a transient issue, and we're now on WinGet 1.7.

@denelon denelon closed this as completed Mar 6, 2024
@denelon denelon modified the milestones: v.Next-Client, 1.8 Client Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Command-Source Issue related to WinGet Source Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

4 participants