Skip to content

TechDirectArchive

Hands-on IT, Cloud, Security, Veeam & DevOps

  • Home
  • About
  • Advertise With US
  • Reviews
  • Tech News
  • Contact
  • Toggle search form

Windows 2016 Servers do not show up on the WSUS console

Posted on 13/12/201817/08/2026 IT Expert By IT Expert No Comments on Windows 2016 Servers do not show up on the WSUS console
  1. Home
  2. Windows Server
  3. Windows 2016 Servers do not show up on the WSUS console
WSUS

Windows Server Update Services (WSUS): WSUS previously known as Software Update Services (SUS), is a computer program and network service developed by Microsoft Corporation that enables administrators to manage the distribution of updates and hotfixes released for Microsoft products to computers in a corporate environment. Please see How to disable unused Cisco Access Ports, Windows server update services: Guide, and Client Visibility Issues: Fix WSUS Clients appear then disappear in the console.

This happens most times because the servers are created from an AMI (never syspreped). For more information on PowerShell and USOClient commands, see https://techdirectarchive.com/2020/02/05/handy-windows-server-update-services-commands-wauaclt-powershell-and-usoclient/, How to apply Windows Updates from WSUS to the server using AWS RunCommand,

Note: All other servers are reporting to WSUS such as Windows Server 2008R2 and Server 2012 R2 but Windows Server 2016 does not.

Note: Server 2016 creates all registry keys, and the WSUS server connects with the Windows server.

Reason for this Error?

Delete the SusClientID and SusClientIDvalidation keys from the registry. This is because the server was created from a clown (AMI) and new ones will be generated automatically.

Please see how to Configure SSL between WSUS servers (Upstream and Downstream Servers), Handy WSUS Commands, Windows Server Update Services Commands, WAUACLT, PowerShell and USOClient, How to Start, Stop and Restart Windows Server Update Services (WSUS) via PowerShell and CMD, and WSUS clients appear and disappear from the WSUS Update Services console.

Fix Windows 2016 Servers do not show up on WSUS console

Stop Windows update service, and delete SoftwareDistribution folder 

C:WindowsSoftwareDistribution folder

Run the commands below from the command line

wuauclt /resetauthorization /detectnow

And this as well

wuauclt /detectnow /reportnow

For more articles, I have written see the following links below

  • Configuring WSUS Email Notification to Work With Office365
  • How to setup and configure Windows server update services (WSUS)
  • Important Areas to Master on WSUS (Installed and not applicable, Install 1/4, and Installed / Not applicable 100), and
  • Targeting WSUS Client with the Registry keys: How to configure WSUS Clients to get Updates from the WSUS server using Registry.

If you found this article useful on Windows 2016 Servers do not show up on the WSUS console. If you require further assistance, kindly leave a comment below.

Rate this post

Thank you for reading this post. Kindly share it with others.

  • Share on X (Opens in new window) X
  • Share on Reddit (Opens in new window) Reddit
  • Share on LinkedIn (Opens in new window) LinkedIn
  • Share on Facebook (Opens in new window) Facebook
  • Share on Pinterest (Opens in new window) Pinterest
  • Share on Tumblr (Opens in new window) Tumblr
  • Share on Telegram (Opens in new window) Telegram
  • Share on WhatsApp (Opens in new window) WhatsApp
  • Share on Mastodon (Opens in new window) Mastodon
  • Share on Bluesky (Opens in new window) Bluesky
  • Share on Threads (Opens in new window) Threads
  • Share on Nextdoor (Opens in new window) Nextdoor
Windows Server Tags:Microsoft Windows, services, Windows 10, Windows Server 2016

Post navigation

Previous Post: How to upgrade Apache Tomcat from One Version to another
Next Post: Tomcat Keystore Update: How to rebind Tomcat Keystore with a new Certificate

Related Posts

  • screenshot 2020 03 13 at 21.22.29
    How to determine Cygwin version Windows Server
  • PSD
    PowerShell Deployment Extension for MDT: How to deploy Windows using PSD, Microsoft Deployment Toolkit, and Windows Deployment Services Windows Server
  • screenshot 2020 03 26 at 22.14.14
    How to create a scheduled task with Windows Admin Center Windows Server
  • sdf
    What is GPO and how can it be launched in Windows Windows Server
  • Perform Site Maintenance or reset this site greyed out
    Fix “Perform Site Maintenance or reset this site” greyed out Windows Server
  • fghj
    MDT deployment failed and Stuck at Command Prompt: Windows installation does not proceed via PXE boot Windows Server

More Related Articles

screenshot 2020 03 13 at 21.22.29 How to determine Cygwin version Windows Server
PSD PowerShell Deployment Extension for MDT: How to deploy Windows using PSD, Microsoft Deployment Toolkit, and Windows Deployment Services Windows Server
screenshot 2020 03 26 at 22.14.14 How to create a scheduled task with Windows Admin Center Windows Server
sdf What is GPO and how can it be launched in Windows Windows Server
Perform Site Maintenance or reset this site greyed out Fix “Perform Site Maintenance or reset this site” greyed out Windows Server
fghj MDT deployment failed and Stuck at Command Prompt: Windows installation does not proceed via PXE boot Windows Server

Leave a Reply Cancel reply

You must be logged in to post a comment.

Microsoft MVP

VEEAMLEGEND

vexpert-badge-stars-5

Virtual Background

GoogleNews

Categories

veeaam100

Veeam Vanguard

  • KMS server setup
    How to set up and configure the Key Management System (KMS) Windows Server
  • diagnose
    How to Diagnose a Windows Hardware Issue Windows
  • reliablee
    How to use the Reliability Monitor in Windows Windows
  • Convert OST to PST
    How to install and work with Stellar Converter for OST Reviews
  • ftpwindows
    How to install and configure an FTP server on Windows 10 Windows Server
  • Snapshot
    Create or delete snapshots on VMware Workstation Backup
  • Shrink and Compact Virtual Hard Disks
    How to Shrink and Compact Virtual Hard Disks in Hyper-V Virtualization
  • Error during connect in the default daemon configuration on Windows
    Preparation failed: The docker client must be run with elevated privileges Version Control System

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 1,765 other subscribers
  • RSS - Posts
  • RSS - Comments
  • About
  • Authors
  • Write for us
  • Advertise with us
  • General Terms and Conditions
  • Privacy policy
  • Feedly
  • Telegram
  • Youtube
  • Facebook
  • Instagram
  • LinkedIn
  • Tumblr
  • Pinterest
  • Twitter
  • mastodon

Tags

Active Directory Azure Bitlocker Microsoft Windows PowerShell WDS Windows 10 Windows 11 Windows Deployment Services Windows Server 2016

Copyright © 2026 TechDirectArchive

Loading Comments...

You must be logged in to post a comment.