Windows Server

WSUS: Failed Import Microsoft Update Catalog updates Error

()

If you encountered an error 80131509 or error 800a0046 when importing updates into Windows Server Update Services (WSUS) from Microsoft Update Catalog, don’t worry. Microsoft has acknowledged some bugs that we’ll review in this article so you can find out what’s affecting you in WSUS and resolve it.

You can read this link if you want to know how to import updates manually into WSUS and SCCM. Here we will review the errors encountered when importing updates from MS Update Catalog.

Previous note bug printers – March 2021:

From Microsoft, they reported that March patches for Windows 10 created problems with printers and cause blue screens when trying to print. They have released new patches to fix this error.

  • Windows 10, version 20H2 – Old Patch: (KB5000802) – New Patch: (KB5001567)
  • Windows 10, Version 2004 – Old Patch: (KB5000802) – New Patch: (KB5001567)
  • Windows 10, Version 1909 – Old Patch: (KB5000808) – New Patch: (KB5001566)
  • Windows 10, Version 1809 – Old Patch: (KB5000822) – New Patch: (KB5001568)
  • Windows 10, Version 1803 – Old Patch: (KB5000809) – New Patch: (KB5001565)

Importing out-of-band patches released on 15/03/2020 may have a “Failed“. In this guide we will review how to resolve error 80131509 and 80131509 when importing updates from MS Update Catalog.

Requirements for Importing Updates into WSUS:

  • A WSUS Server with Internet Access to import updates from Microsoft and download them
  • Internet Explorer with the “Microsoft Update Catalog” add-on. If you do not have it installed, you will ask us to do so during the procedure.
  • Administrator permissions on the WSUS.

WSUS – Error 80131509 and 80131509 – Import Results

When importing WSUS updates we encounter the error:

Microsoft Update Catalog - Failed Import Updates - Error 80131509

Error 80131509 and error 80131509:

“Some updates could not be imported. If you canceled the process, try again to import the updates. If an error occurred, click Failed in the progress column next to each update to see how to solve the problem.”

WSUS – Some updates could not be imported – Error 80131509

If we click on “Failed” we can see more details of the error. Getting error code 80131509 and suggesting that we review the WSUS server proxy and configuration:

Microsoft Update Catalog - Some updates could not be imported - Error 80131509

Error 80131509:

Some updates could not be imported.
Error number: 80131509

The following are common causes and solutions for this issue:

  • If you use a proxy, be sure that it is the same proxy being used by your Windows Server Update Services (WSUS) server.
  • Your WSUS server might not be configured correctly. Contact your WSUS administrator”

WSUS Error 80131509 and 80131509 Solution

First we need to check that the proxy is properly configured and WSUS is working. In case we have reviewed it or WSUS works normally as long as it is only presenting problems now, we can perform the following method to solve the problem:

1. Open a CMD on the WSUS server as Administrator.
2. Enter the following command:

3. Validate that the key was successfully created in REGEDIT as follows:

NETFramework - SchUseStrongCrypto - Regedit - WSUS

4. Restart the WSUS Server.

5. Import the updates into WSUS and verify that error 80131509 or 80131509 does not happen.

Result

After you apply the registry key solution, updates are already imported successfully. When importing updates, we see the message “Done”:

Microsoft Update Catalog - Import Progress - Done

And in WSUS the updates will appear within our catalog:

WSUS - All Updates - KB imported

So far, Microsoft has not explained this issue. Although it all makes you think it’s because of an encryption that you’ve started using the Microsoft Update Catalog website that our WSUS servers weren’t ready for.

In case of news I will update this article. You can leave your doubts or other issues with MS Update Catalog and WSUS in the comments.

How useful was this post?

Click on a star to rate it!

Average rating / 5. Vote count:

No votes so far! Be the first to rate this post.

As you found this post useful...

Follow us on social media!

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Nando Corzo

Passionate about IT and Microsoft technologies with more than 5 years of experience in complex environments (Banking, Congresses and Public Services). Exploring and learning about Modern Workplace every day. I write about SCCM, Windows, Microsoft Intune, Hyper-V, etc...

One Comment

  1. Worked great, the command got parsed:
    reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /V SchUseStrongCrypto /T REG_DWORD /D 1

    I then restarted the server.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button