Microsoft’s WinGet package deal supervisor is presently having issues putting in or upgrading packages after WinGet CDN’s SSL/TLS certificates expired.
Released in May 2020, the open supply Windows Package Manager (WinGet) permits customers to put in purposes instantly from the command line.
WinGet down after CDN’s SSL expires
Starting late night hours of Saturday, Windows customers started reporting points when trying to put in or improve apps through WinGet.
WinGet consumer Tiger Wang shared a screenshot on GitHub of their command line throwing an “InternetOpenUrl() failed” error as they tried operating easy WinGet instructions, resembling:
winget improve --all --verbose.
This report was seconded by one other consumer who was additionally experiencing the difficulty. The drawback seems to be related to WinGet CDN’s SSL/TLS certificates that has now expired.
When navigating to the CDN URL, https://cdn.winget.microsoft.com in Chrome, BleepingComputer obtained the next error:
Both the warning and the certificates particulars verify that WinGet CDN’s certificates stopped being legitimate over the weekend:
What is a short lived resolution?
Until Microsoft renews the SSL certificates, WinGet customers can relaxation simple realizing there’s an alternate workaround to handle the scenario.
This includes including the next supply URL to WinGet’s record of sources, versus relying solely on cdn.winget.microsoft.com. That manner, WinGet can fetch the packages from this alternate server which has a sound certificates on the time of writing.
https://winget.azureedge.net/cache
“You can add a supply like https://winget.azureedge.net/cache utilizing the command under,” GitHub consumer qilme suggested.
sudo winget supply add -n winget https://winget.azureedge.net/cache
The winget software supply command allows customers to handle sources for Windows Package Manager. With the supply command, one can add, record, edit, delete, reset, or export repositories utilized by WinGet.
Note: When executing the above command, ‘sudo’ is not required if the command is being run in PowerShell by an administrator account. Should you expertise errors, attempt eradicating the default WinGet supply previous to including the brand new azureedge hyperlink.
The azureedge URL in query is an alias for WinGet’s CDN, albeit with a sound certificates which makes it a viable resolution for WinGet devs:
Once Microsoft has renewed the first CDN’s certificates, customers can optionally select to reset their supply URLs by operating one other command:
“You can at all times run winget supply reset –force (as admin) to get again to defaults,” advises GitHub consumer Adam Langbert.
Prior to at this time, WinGet’s final widespread disruption occurred in November 2022 as a result of CDN returning a “0-byte database file” when queried.