-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
v1.7.10582 upgrade --all
fails without any errors or output
#4219
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
|
I manually deleted |
Facing the same issue (also version v1.7.10582). Deleting pinning db did not resolve the issue. |
Try to reset Winget? With PowerShell: Get-AppxPackage -Name 'Microsoft.DesktopAppInstaller' | Reset-AppxPackage |
Ran into the same issue today, too. I'm also on version However, doing a |
Thanks @o-l-a-v, the reset worked 👍 |
I ran into this yesterday on one computer, and again today on another computer.
I deleted the pinning.db, and that didn't change anything. Then I tried resetting the packaged as show above, and that solved the problem. Update --all now installs the listed updates. |
I tried it, but I get this error:
It's like I don't have Reset-AppxPackage |
Did you try with Windows PowerShell 5.1 (powershell.exe) too? Edit: Also found this when searching:
Seems According to this: You can do the following instead: Add-AppxPackage -DisableDevelopmentMode -Register (
[System.IO.Path]::Combine((Get-AppxPackage -Name 'Microsoft.DesktopAppInstaller').'InstallLocation','appxmanifest.xml')
) Edit 2: I tried above command, but Winget did not get reset. Edit 3: Made a workaround that seems to do the same as |
How to reset WingetNote This will reset all Winget settings. Warning Use Windows PowerShell 5.1 (powershell.exe), not PowerShell Core (pwsh.exe). How to find what Windows build you're onOpen run prompt, CMD, pwsh or PowerShell. Type Or use If on Windows 11 (build >= 20215)# After Windows insider build 20215
Get-AppxPackage -Name 'Microsoft.DesktopAppInstaller' | Reset-AppxPackage If on Windows 10 (build < 20215)# Before Windows insider build 20215
## Get app in question
$App = Get-AppxPackage -Name 'Microsoft.DesktopAppInstaller'
## Delete app data
$AppDataDir = [string] [System.IO.Path]::Combine(
[System.Environment]::GetFolderPath('LocalApplicationData'),
'Packages',
$App.'PackageFamilyName'
)
[System.IO.Directory]::GetDirectories($AppDataDir).ForEach{
$null = [System.IO.Directory]::Delete($_,$true)
}
## Re-register / reinstall application
Add-AppxPackage -DisableDevelopmentMode -Register -Path (
[System.IO.Path]::Combine($App.'InstallLocation','appxmanifest.xml')
) |
I am getting errors with the add-AppxPackage command:
though as far as I can tell, msstore and winget are down:
trying msstore in browser gives: This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<script/>
<Message>No HTTP resource was found that matches the request URI 'https://useast.storeedgefd-origin.xbetservices.akadns.net/v9.0'.</Message>
</Error> and similarly for winget This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<script/>
<Code>ResourceNotFound</Code>
<Message>The specified resource does not exist. RequestId:91cdae92-d01e-0079-2209-6ec02d000000 Time:2024-03-04T07:56:23.9195966Z</Message>
</Error> |
Winget is not down for me. v7.4.1 x64
PS C:\Users\olav.birkeland> winget source update
Updating all sources...
Updating source: msstore...
Done
Updating source: winget...
Done
PS C:\Users\olav.birkeland> winget upgrade
No installed package found matching input criteria.
1 package(s) have version numbers that cannot be determined. Use --include-unknown to see all results.
2 package(s) have pins that prevent upgrade. Use the 'winget pin' command to view and edit pins. Using the --include-pinned argument may show more results.
PS C:\Users\olav.birkeland> Try to use Windows PowerShell (powershell.exe), not PowerShell Core (pwsh.exe) for the Appx commands? |
tried with powershell.exe same results:
and the log file:
|
I can only find errors about importing Appx if using pwsh.exe:
What Windows edition do you have? LTSC. Home. Professional. Have you tried the regular Windows troubleshooting commands from CMD as admin? sfc /scannow and DISM.exe /Online /Cleanup-Image /Restorehealth |
oh, sorry I was not clear, Appx did not give an error with powershell.exe yet winget still gives errors Edition Windows 10 Pro
seems that "Microsoft.Winget.Source_8wekyb3d8bbwe" is missing from my installation but even after reinstalling winget and app installer it is still "missing" and I still get errors with various winget commands:
|
I have tried it earlier tonight did not seem to help, but tried it again winget is now working better, but not perfect... from the log file it is finding the extension (i.e. it is no longer missing - THANKS) yet still getting an error, but a different one now: The connection with the server was reset 2024-03-04 02:45:13.978 [CORE] Examining extension: PFN = Microsoft.Winget.Source_8wekyb3d8bbwe, ID = IndexDB 2024-03-04 02:45:14.040 [REPO] Source add/update failed, waiting 2689 milliseconds and retrying: winget 2024-03-04 02:45:16.775 [REPO] Failed to update source: winget yet I am able to access the URL via a browser: https://cdn.winget.microsoft.com/cache/source.msix |
also getting this error: Failed when searching source: msstore more details from the log file: 2024-03-04 03:05:55.154 [CORE] Examining extension: PFN = Microsoft.Winget.Source_8wekyb3d8bbwe, ID = IndexDB 2024-03-04 03:05:55.175 [REPO] Failed to update source: winget The exception %s (0x Msg:[std::exception: WinHttpSendRequest: 12030: The connection with the server was terminated abnormally ] 2024-03-04 03:05:55.259 [REPO] Failed to open available source: msstore yet I can access the URL from the browser: https://storeedgefd.dsx.mp.microsoft.com/v9.0/information though still getting error when trying https://storeedgefd.dsx.mp.microsoft.com/v9.0 (but I guess that it is because the URL is not complete?) |
looking for WinHttpSendRequest: 12030 found that it means incompatible SSL protocol was encountered will continue investigating tomorrow... |
that one worked for me, thank you 🙏 |
no luck figuring out why I am getting the 12030 error:
|
[Policy] Command-Upgrade |
thanks, resetting fixed the issue! |
Hey everyone, |
https://github.com/microsoft/winget-cli/releases/tag/v1.7.10661 We're flighting to Windows Insider Beta and Windows Insider Release Preview. If all goes well we will release as stable early next week, but you can try it out now. |
Had the same reported issue for showing packages but doing nothing
This fixed it 🎉
|
https://github.com/microsoft/winget-cli/releases/tag/v1.7.10661 is now marked as the stable release at GitHub and it's being published to the Microsoft Store for those getting automatic updates. |
Same issue here, but with a newer version of
Thanks @o-l-a-v ! |
I also experience this issue. I'm on Windows 11 (22631.4317) with winget version 1.8.1911. I tried all the steps outlined in the comments of this issue and nothing helped. |
I tried all outlined steps aswell and it did not work. |
There's an option in Chris Titus' Windows Toolbox to reinstall Winget. Try that, maybe. |
Instructions on how to reset Winget: #4219 (comment)
Brief description of your issue
winget upgrade --silent --all
suddenly fails on my system. Winget v1.7.10582.I notice that the logs are spammed with
attempting to open pinning database
, last line says[REPO] Did not find a Version for { 6.0.27 }
.So maybe related to pinning? And maybe related to:
Winget output:
Click to view
Logs (
--verbose-logs
):WinGet-2024-02-29-23-02-41.049.log
Steps to reproduce
winget upgrade --all
Expected behavior
Should upgrade all upgradable packages. If it fails it should throw an error.
Actual behavior
No packages get updated, no errors are thrown.
Environment
The text was updated successfully, but these errors were encountered: