Microsoft’s Update Catalog website is a popular destination for downloading the company’s Windows updates. Although there are many third-party options available, the Update Catalog website only requires a browser to download updates for Windows.
One problem that users could encounter until now was that they could no longer download updates in their browsers, as Microsoft only provided downloads via HTTP links. Many browsers restrict access to HTTP sites and resources. Some allow users to bypass access restrictions, others block access to HTTP resources altogether.
Even Microsoft‘s own web browser, Edge, recently started blocking downloads from the company’s Update Catalog website due to HTTP usage. Administrators and Windows users had to use different web browsers or tools to download from Microsoft’s official update repository.
When you visit the Microsoft Update Catalog website now, you will no longer experience resource access issues because Microsoft has switched downloads to HTTPS on its website. Files and resources served over HTTP can be manipulated because they are not encrypted. Windows Updates, on the other hand, are digitally signed and tamper-proof.
The company also changed the link structure in the process from download.windowsupdate.com to catalog.s.download.windowsupdate.com. Interested users can check the download links using the web browser‘s built-in developer tools.
The main link structure of the update page remains, only the download links for individual updates have been changed using the new link structure. Direct links posted on the Internet should be redirected automatically, but if not, just edit the first part of the link address to make it work again.
New link: https://catalog.s.download.windowsupdate.com/d/msdownload/update/software/updt/2022/03/windows10.0-kb5011563-arm64_b17fbb4bf86fcf66b5971d076ffdb7d570002c4e.msu
Simply replace http:// with https://catalog.s. and the download link should work again.
The change improves the accessibility of the Microsoft Update Catalog website, as users should no longer encounter secure connection warnings when attempting to download updates directly from the resource.
Now you: Do you download updates manually from the Update Catalog? (via Deskmodder and Born)