Forum Discussion
ISSUE: Cannot import updates to WSUS, due to erroneous redirection in Windows Update Catalog
abbodi1406
I have spent more time into the testing and found out that it worked in a VERY specific configuration. So to say must be exactly this configuration as you stated.
Bummer.ONE MAY NOT USE https://www.catalog.update.microsoft.com/ in the exception
While these pages can be technically reached, they do not work correctly and will not redirect. Imho this is still a server-side config issue on the IIS 10.
1. It only works as expected when you use the link without www. It does not work with the www. anymore.2. you need to actually add both links. One or the other won't be enough anymore.
Both was till November 2021. But no more.3. really remove any other links in the scope of *.catalog.microsoft.com
4. close all catalog.microsoft.com tabs and restart the browser (just in case you have set that Edge should reopen all tabs on next start)
Thank you abbodi1406 I will update my guide accordingly.
Eds1989 can you please confirm this solution worked for you?
abbodi1406
I have spent more time into the testing and found out that it worked in a VERY specific configuration. So to say must be exactly this configuration as you stated.
Bummer.
ONE MAY NOT USE https://www.catalog.update.microsoft.com/ in the exception
While these pages can be technically reached, they do not work correctly and will not redirect. Imho this is still a server-side config issue on the IIS 10.
1. It only works as expected when you use the link without www. It does not work with the www. anymore.
2. you need to actually add both links. One or the other won't be enough anymore.
Both was till November 2021. But no more.
3. really remove any other links in the scope of *.catalog.microsoft.com
4. close all catalog.microsoft.com tabs and restart the browser (just in case you have set that Edge should reopen all tabs on next start)
Thank you abbodi1406 I will update my guide accordingly.
Eds1989 can you please confirm this solution worked for you?
yes, urls must be without www.
- now 🙂 it worked with www. back in November. I hope they are going to look into this if you do not add both links either it will redirect to http://www.catalog.* or the redirect will not be to v7/site page which means no import is possible at all or the said error happens.
If you have time check the updated guide, just to make sure it is correct again.
I did not include the TLS thing as this is a practice one should do globally and is also in place on Windows Server 2022 (I believe except PS 5.1).- The ActiveX controller utilize legacy .NET 4.0 connection which do not use TLS 1.2 by default
SystemDefaultTlsVersions (or SchUseStrongCrypto) is needed to force it to TLS 1.2Can you kindly elaborate on where this key needs to be created, what type it should be, and what value I need to set it to?
Thanks
James
We use enterprise site manager to add our IE mode sites to a centrally stored XML files, that Edge group policies are set to load.
We have these two URLs configured as below:
We do not see these in Edge settings, but they should be effective:
When I click on the import updates button, it still loads a www. URL without the v7 in the path:
It's gone midnight now, so I'll try updating policies and from another machine in the morning to see what happens.
Thanks
Scratch that, just tried once more before bed, and can confirm this does now seem to be loading the correct URL, however....
When trying to complete the import process, it fails:
Error page:
Have I done something wrong?
