Windows 10: My WSUS-managed computers are all downloading 20H2 but are not installing it

For the record, this is not an issue where the install is failing. There is no install at all. There is no error. The computers are simply downloading the update, and then it just sits there and does nothing. I can see in WSUS that the update has downloaded. It shows these computers need the update. But they never install it.


I did a remote session with one user on a computer that is exhibiting this problem. I went to windows update and it showed it had just checked for updates that morning and was "up to date." I manually ran windows update and it immediately told me "Hey you've got the new 20H2 update to install."I told it to install it and it did, and then restarted. When the computer came back up I saw that it now shows 20H2 installed.


This is not right. If it is downloading the update, it should be installing it as well with no user input. The user should not have to manually run windows update to coax Windows into installing this update. Has anyone else experienced this?

:)

 

The WSUS support thread

well i installed WSUS on a virtual machine on my home pc for testing ... pretty strait forward only thing is that the SQL server goes crazy on memory while synchronizing and updating ... mine went up to 8GB i don't know if it does this on first time only ? will see with usage...
i installed 2008 on 1 VHD and i install all the update on another VHD that i can resize if needed, for now WSUS is telling me that it as downloaded 80MB of 69GB "on install i choose ALL windows flavour .."

 

WSUS Manual Entry

Odd question for MS Experts.

I have a WSUS environment, and 99% of my servers report to it. This makes it very useful as a list of servers and workstations. But there are 1% of our servers that are in the DMZ or off network. I want to use the list of my WSUS computers to know what
computers need to be patched, so they don't get forgotten.

These 1% never have to actually talk to WSUS, just appear in the list of computers so a human knows they exist.

How can I manually add a computer to the WSUS Server?

Can I manually manipulate the DB (Full SQL), and if so, how?

 

The WSUS support thread

This thread is for all things WSUS (Windows Server Update Services). Discussion, installation questions, problems all go here.

What is WSUS? It's basically a big file cache for all your Windows/Microsoft updates, so all your updates are only ever downloaded over the internet once. Instead of getting your updates directly from Microsoft whenever you reinstall your operating system, you point Windows to your local WSUS server instead. This makes downloading the multi-gigabytes of updates way faster using your internal network and also saves your internet bandwidth, which is often metered and limited.

Note that it requires Windows Server to run. I recommend running the latest Server 2008 R2 for performance, stability and security, if you can. This is a 64-bit only OS. And yes, the server can update from it's own WSUS server too. *Cool

I've got links to a few resources below and I'll be adding more goodness to this post and the next one, as people make useful contributions to this thread.

Some WSUS resources to get you started:

The manual: http://technet.microsoft.com/en-us/library/dd939796(WS.10).aspx

WSUS home: http://technet.microsoft.com/en-us/wsus/default.aspx

WSUS forum: Technet forums - WSUS

WSUS wiki: www.wsuswiki.com


POINTING WINDOWS TO THE WSUS SERVER

Note that this procedure is all you have to do on Vista and 7. XP requires a little extra and the whole update process isn't as transparent or efficient.

- Click the Orb at the bottom left of the desktop aka 'Start' button
- In the search field enter GPEDIT.MSC
- In the Local Group Policy Editor (LGPE) console that appears, navigate to: Computer configuration > Administrative Templates > Windows Components > Windows Update
- Double click the Specify Intranet Microsoft update service location Group Policy setting. Note that Not Configured is showing in the State column






- The dialog box opens. Note that the Not Configured radio button is selected






- Enter the server details, by clicking the Enabled radio button and entering the same details in both Options fields. The server's name is the standard Windows name. My server is called afterburner *Smile






- Click OK. The main LGPE window now looks like below. Note that Enabled is now showing in the State column.





- Close the LGPE window

- Open the Windows Update window. It should now show You receive updates: Managed by your system administrator





Now, whenever you check for updates, Windows will access your WSUS server instead of looking over the internet to Microsoft's servers.
If you want to change it back at an time, simply change the Group Policy setting back to Not Configured.