Windows 10: WSUS Not working on Windows Server 2025

When setting up WSUS on a Windows Server 2025, one might encounter issues with the update of the repository, and the server will never synchronise.

After looking at the logs, which can be found in the C:\Windows\UpdateLog.log one would see timeout errors.

First things to check are the firewall and internet access of the server. The other reason why the synchronization would fail it would be due to the security defaults of Windows Server 2025, where TLS and SSL, which are disabled by default.

For WSUS to work, one needs to enable these protocols. To enable them, one can use applications such as IIS Crypto, which can be downloaded from the link below.

https://www.nartac.com/Products/IISCrypto/

After enabling TLS and SSL, reboot the server. After logging in, try to synchronize the WSUS, and it should be working.

read more...

 

WSUS - Servers not reporting in

Hi All,

I am busy with WSUS in a lab running off my laptop. Details are as follows:

1. 1 x Domain Controller running Windows Server 2019
2. 1 x WSUS Server running Windows Server 2019
3. 1 x Windows Server 2016 VM

I've installed WSUS on #2 and it's busy downloading updates I have selected. However, try as I might, I cannot get the other 2 servers to report in. Further information:

• All firewalls are disabled;
• I can ping via name/IP successfully;
• I can successfully run nslookup;
• I cannot browse the http://servername:8530 site (in spite of generating the SS;
• 2 GPOs were created (one for Test, one for PRD) and linked/enabled on the domain;
• WSUS Service running on the other 2 VMs.

What can I check to ensure that this works? The GPOs are applied, but do I need OUs within AD itself and the servers placed in those, or is leaving them in the default container fine for now? Like I said, it's for test purposes, but I obviously need to get
it running for further trials/tests I'd like to do.

Thanks!

Craig

 

My WSUS server does not go through WSUS services.

Hi guys, hope you are all doing fine.

I have an question regarding Microsoft Windows Server 2019.

Here in the enviroonment we have several servers running with all his own services.

• 2 dcs (1st one is AD-DS, GPO, DNS etc. 2d one is replication for AD-DS)
  1 sync server with Azure for hybrid.
  1 WSUS server
  1 backup server (veaam, and cloud backup)
  1 file server
  1 WDS / workbench server
  

I have installed, and configured on the WSUS server everything including the GPO's.

But the updates still goes through Windows Updates instead of the Server.

I have managed now that the clients are going through the WSUS server, i confirmed that via the logs what i have generated.

But my server self, the WSUS server still goes through WindowsUpdate, how can i solve this problem??

 

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: Microsoft Q&A

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.