-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Problem with upgrade command #4225
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:
Closed similar issues:
|
Seems like a duplicate of #4219. A workaround is to reset Winget. You'll loose all settings, including pinned apps. I wrote about it here: |
your workaround did not work for me,
found out by looking at the log file that the error is WinHttpSendRequest: 12030 it means incompatible SSL protocol was encountered |
What is the output of |
The source URLs don't have any content at their root. |
|
I see. I'm not very technical myself, but should I put the source.msix file at all of the Portable Package Root locations, or should I just run the .msix file? Sorry if this seems trivial to you, just not used to sending GitHub reports and all that. |
@Lanerun no worries. We were all new to GitHub at some point. The output you shared above is missing the closing quotation mark after "C++". Try running "installing" the source.msix. That will update the local cache of packages, and I suspect that's what got corrupted. |
@denelon Thanks for the uplifting words! I re-ran the command with the correct quotation marks, but sadly it still gave the same error. Installing the source.msix worked, but the issue when running the winget upgrade command still persists.
I ran the command
Which is odd, since when I do WinGet Upgrade this is what shows:
|
This may be my error too; I usually use single quotations since that's what PowerShell works best with, but double quotes may be needed when using cmd, or bash
|
I see. I was running it in command prompt, so that seems to have been the issue. With double quotations the command works, and displays the following output:
|
Got it! This is a known issue where having two applications installed side-by-side causes an upgrade loop to occur.
From these two lines, it's clear that both |
yes, I realized that later on... found out by looking at the log file that the error is WinHttpSendRequest: 12030 12030 means incompatible SSL protocol was encountered, but I do not know how to fix it... attempted to enable BypassCertificatePinningForMicrosoftStore also checked all ssl/tls version in internet options, no go:
PS C:\WINDOWS\system32> |
Brief description of your issue
WinGet Upgrade states Microsoft.VCRedist.2013.x86 as outdated, however when running the WinGet Upgrade command on it, no update is found. See image for reference.
Steps to reproduce
Run WinGet Upgrade
WinGet shows various programs as out-of-date, one of them being Microsoft.VCRedist.2013.x86
Attempt to update Microsoft.VCRedist.2013.x86 using WinGet
WinGet does not find any updates for the program.
Expected behavior
Microsoft.VCRedist.2013.x86 is successfully updated.
Actual behavior
Microsoft.VCRedist.2013.x86 isn't updated by the command.
Environment
The text was updated successfully, but these errors were encountered: