WSUS: The Update Could Not Be Found

I was re-installing the WSUS role on our security server (W2008 R2) today and hit this error as soon as the installation started:

“The update could not be found”.

It’s a bit of a weird one for a role installation.  I hadn’t the foggiest so I did a quick search and found the solution:

  • Delete the “WindowsUpdate” key from the registry at HKLMSoftwarePoliciesMicrosoftWindows.  I’d recommend you export this to a .reg file to be safe.
  • Restart the Windows Update service.

Now you can go ahead and install WSUS.

The problem and fix applies to previous versions of Windows.  The issue is that the installer is checking Windows Updates but it has found a circular reference.  You’ve uninstalled WSUS from the server and it is configured to update from itself.  How can it?  Make sure you do the install before GPO applies those settings again during an automatic refresh.

Technorati Tags: ,

28 thoughts on “WSUS: The Update Could Not Be Found”

  1. What if the below doesn’t exist and you still get the same error ?

    Delete “WindowsUpdate” key from the registry at HKLMSoftwarePoliciesMicrosoftWindows

  2. I look for solution whole day – it is work – I forget that I am have internal policy for own wsus which is down 🙂
    super thanks

  3. When the role tries to install it will try to update the server with required patches before adding the WSUS role.

    In some cases the role was previously on the server, removed for a reason, and now it needs to be re installed.

    If the server is pointing to itself as a WSUS server due to a GP from the domian, move the computer account to a OU with inheritance of GPs blocked.

    run gpupdate /force on the server.

    Then it should install.

    This is the reason you cannot find the key.

Leave a Reply

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.