Blog Post

Windows IT Pro Blog
2 MIN READ

Importing updates into WSUS is changing

Paul_Reed's avatar
Paul_Reed
Former Employee
Jul 26, 2023

If you use Windows Server Update Services (WSUS) to update devices, the process of importing updates has changed. You’ll now use a new PowerShell script to import updates. Regularly updating your devices and doing so in safest ways possible will help keep devices at your organization even more protected. Let’s see how!

The old way to import Windows updates

Up until now, WSUS included an option to import updates from the Microsoft Update Catalog site. You used to find it in the WSUS admin user interface: Updates > Actions pane, illustrated below.

The Import Updates option is located under Actions in the Updates section of the WSUS admin user interface

The behavior of this user interface is changing. The Import Updates function was built using ActiveX, which is now deprecated. A new and better way is now available for you to keep your devices up to date!

The new import update process for WSUS

A new PowerShell script replaces the import functionality within WSUS. You will now use this script to download the updates and have them imported to your WSUS server.

There are two ways to get this new script:

  1. Follow your typical steps in WSUS admin user interface: Actions > Import Updates. You’ll now be redirected to the documentation containing the script.
  2. Go directly to PowerShell script to import updates into WSUS in the official WSUS and the Catalog site documentation.

Once you copy the script, you’ll follow a series of steps to import updates into WSUS using PowerShell. Briefly, here’s what you’ll have to do:

  1. Save the script.
  2. Open the Microsoft Update Catalog site in a browser.
  3. Search for an update you want to import into WSUS.
  4. Select the desired update from the returned list.
  5. Copy the UpdateID on the opened details page. Note: If importing multiple updates, create a text file with each UpdateID on a separate line.
  6. To import updates, open a PowerShell console as an administrator and run the script with the syntax provided in our documentation.

Note: The files for the imported updates aren’t downloaded at the time of import. Please check your Update files settings to review or change when they will be downloaded.

Please continue checking the WSUS and the Microsoft Update Catalog page for complete and up-to-date guidance on importing updates. That’s the same place where you’ll find the script, the syntax, and some helpful examples.

If you feel that you’re missing some information, we invite you to leave us a comment below and see the following resources:


Continue the conversation. Find best practices. Bookmark the Windows Tech Community and follow us @MSWindowsITPro on Twitter. Looking for support? Visit Windows on Microsoft Q&A.

Updated Jul 26, 2023
Version 2.0

47 Comments

  • Paul_Reed's avatar
    Paul_Reed
    Former Employee

    Hi SusanBradleyGeek and JasonHyatt - This change only effects updates that are not published to the WSUS channel.  Search by KB number or keyword is not going away.  With the import update changing, we need to surface the update GUID.  The KB number is associated with multiple updates and architectures.  For the import you need a way to unambiguously identify the update.  The GUID was used by the "Import Update" function in WSUS.  The script that published is based on that.  What has changed on the catalog is that we are now surfacing the update GUID that is needed for the script.  

  • JasonHyatt note that this is only for patches that Microsoft doesn't publish to WSUS.  It's not a lot but sometimes there is some patch that it is the catalog only but not pushed to MU or WSUS. The normal method of approving patches hasn't changed, just if you need to import a "one off"

     

    My snark comes from the comment that this is a "new and better way".  It's new.  It's definitely not better.  And given that the activeX was known for a long time to be deprecated, it's expected for a product that Microsoft clearly deems dead and gets no revenue from.

  • "A new and better way is now available " Folks you changed the Windows update log file to now it's nearly unreadable.  Now having us find the Update ID rather than going by KB number?  I get it that it's a dead product but don't kick the dead body while you are at it.

  • JasonHyatt's avatar
    JasonHyatt
    Copper Contributor

    Isn't this more work to do it this way?  How much time does it take to find all the different versions of Windows and that they are up to date?  This seems like a lot of work verses on the WSUS you can pull all the new updates based on the criteria you have selected.  

  • The documentation in Portuguese is not yet updated.

    By the same token, I got confused looking for the Powershell script, and changed to the English language.

    What can confuse. I recommend informing the post that the documentation was updated only in English.

     

  • Paul_Reed's avatar
    Paul_Reed
    Former Employee

    Hi abbodi1406 ,

    It's our practice to share short scripts like this inline so you can easily copy/paste into a new or existing file or project. By publishing the script directly in the article, we can also make updates quickly when and if needed. In addition, we have found that some corporate firewalls block downloads or certain file types.

  • abbodi1406's avatar
    abbodi1406
    Iron Contributor

    Isn't better to offer a download link for the script file inside zip file?