Home Technology Microsoft WinGet package deal supervisor failing from expired SSL certificates

Microsoft WinGet package deal supervisor failing from expired SSL certificates

0

[ad_1]

windows

Microsoft’s WinGet package deal supervisor is presently having issues putting in or upgrading packages after WinGet CDN’s SSL/TLS certificates expired.

Launched in Might 2020, the open supply Home windows Bundle Supervisor (WinGet) permits customers to put in functions instantly from the command line.

WinGet down after CDN’s SSL expires

Beginning late night hours of Saturday, Home windows customers started reporting points when making an attempt to put in or improve apps through WinGet.

WinGet person Tiger Wang shared a screenshot on GitHub of their command line throwing an “InternetOpenUrl() failed” error as they tried operating easy WinGet instructions, comparable to:

winget improve --all --verbose.

Users report errors while using WinGet
Customers report errors whereas utilizing WinGet (GitHub)

This report was seconded by one other person who was additionally experiencing the problem. The issue seems to be linked 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:

WinGet CDN SSL expiration
WinGet CDN’s SSL/TLS certificates expiration warning (BleepingComputer)

Each the warning and the certificates particulars verify that WinGet CDN’s certificates stopped being legitimate over the weekend:

SSL expiry date
Certificates’s expiry date proven in GMT+05:30 (BleepingComputer)

What’s a brief resolution?

Till Microsoft renews the SSL certificates, WinGet customers can relaxation simple realizing there’s an alternate workaround to handle the state of affairs.

This entails including the next supply URL to WinGet’s listing of sources, versus relying solely on cdn.winget.microsoft.com. That means, WinGet can fetch the packages from this alternate server which has a sound certificates on the time of writing.

https://winget.azureedge.internet/cache

“You possibly can add a supply like https://winget.azureedge.internet/cache utilizing the command beneath,” GitHub person qilme suggested.

sudo winget supply add -n winget https://winget.azureedge.internet/cache

The winget device supply command permits customers to handle sources for Home windows Bundle Supervisor. With the supply command, one can add, listing, edit, delete, reset, or export repositories utilized by WinGet.

Observe: When executing the above command, ‘sudo’ is not required if the command is being run in PowerShell by an administrator account. Must 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:

nslookup DNS query for WinGet CDN
‘nslookup’ outcomes for WinGet CDN’s hostname (BleepingComputer)

As soon as Microsoft has renewed the first CDN’s certificates, customers can optionally select to reset their supply URLs by operating one other command:

“You possibly can all the time run winget supply reset –force (as admin) to get again to defaults,” advises GitHub person Adam Langbert.

Previous to immediately, WinGet’s final widespread disruption occurred in November 2022 because of the CDN returning a “0-byte database file” when queried.

[ad_2]

LEAVE A REPLY

Please enter your comment!
Please enter your name here