Windows 10: Trying to troubleshoot a Windows Update / WSUS issue:

I have a lab environment with a WSUS server that is failing to deliver updates to client systems. Below are the steps I've taken and troubleshooting attempts I've made, at the bottom is an example event log Event 1001 from my DC:1. I've run the windows update troubleshooter, on both the WSUS server and the DC.2. I've ensured that Antivirus / Firewall are paused prior to attempting windows updates.3. I've placed the WSUS server into a OU that enforces minimal GPOs for testing during this process.4. I am running through an internet proxy that I do not have control over,5. When I attem

:)

 

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.

 

Vista Pre-SP1 vs. Vista SP1

I've been Windows Updating for two straight days and I finally saw SP1. If you want to troubleshoot it, follow these steps:

• Show hidden updates
• Manually install any failed updates (google the KB_____ and install from the windows site)
• Make sure everything in Device Manager is good to go

I had to do step two for like 4 or 5 updates to be able to see SP1.

Any other benchmarks you guys want to see? I might try PCMark05 (I think it works on Vista).

 

Windows update issues

+1

If your wireless router has a built in firewall maybe it's somehow set to block the ports that Windows updates use?

I'd also suggest if it works with it being directly connected then you could try resetting your router to see if this fixes the issue.

That's my 2 cents anyways. *Smile