We help IT Professionals succeed at work.


Windows Server Update Services (WSUS), previously known as Software Update Services (SUS), is a computer program developed by Microsoft that enables administrators to manage the distribution of updates and hotfixes released for Microsoft products to computers.

After installing WSUS on 2016 core, I cannot find the option to configure the WSUS from my 2012 server manager console.  I've tried from dashboard, tools or right clicking the actual server name that has WSUS on it.  It shows up in my Server management console WSUS but I can't find the option to finalize the config before pointing my pc's to it.  It's probably a silly answer but I'm not getting anywhere looking myself.
My Window 10 can't upload the latest 1803 from my WSUS.  Any idea ?
What are the best free services for sending emails without SMTP authentication?

I need to configure my organization's WSUS server for sending notification emails and would prefer to use a free account that doesn't require SMTP authentication.

What are the best free services for doing this?
I have a Windows Server Update Services (WSUS) server setup that currently has all of the Server 2016 updates available except for the KB4103720 update (even though I have selected the WSUS server to download all of the Server 2016 updates).

I have verified this by sorting the updates chronologically by their KB numbers and by doing a search for the KB4103720 update.

I have checked and all other necessary Server 2016 updates are currently available within this WSUS server. I haven't selected for any of the other updates such as Windows 10 updates to download to the WSUS server yet since currently I only need it to update the Server 2016 servers within our network. I will add the Windows 10 updates later.

How can I manually add or make sure that this KB4103720 Server 2016 update is available to push out to the Server 2016 servers?
I clicked on the "Reports" tab of Server 2016 Windows Server Updates Services and was told that "The  "Microsoft Report Viewer 2012 Redistributable"  is required for this feature. Please close the console before installing this package."

So I clicked on the URL link and was directed to the website https://www.microsoft.com/en-us/download/details.aspx?id=35747 where I downloaded the "Microsoft Report Viewer 2012 runtime."

However, when I installed the "Microsoft Report Viewer 2012 runtime" ReportViewer.msi file I received a message that said "Setup is missing an installation prerequisite. -Microsoft System CLR Types for SQL Server 2012" (see the screenshot).

I have googled this and the results I have found have had me download several different MSI installation files without telling me exactly which one(s) I need to install. I want to make sure that I only install the component or program that I absolutely need and that I don't install anything extra.

So what is the best URL to visit to download and install the right "Microsoft System CLR Types for SQL Server 2012?"

Microsoft System CLR Types

I am planing to deploy the MS patches updates on nearly 3500 clients mixed Windows 10 and windows 7 using WUSS server.  I have no problem to creating  group under Computer node in WSUS  server and configure the GPO to push the updates for clients windows 10 & 7.
I am looking here for  help if there is way or Script which can push the updates on clients using wsus and install them at shutdown stage.  I mean when user shutdown PC the updates kicks off and install in the background.
I hope there should be way to achieve this or power shell script. Please advice.

Hello I use WSUS on Server 2016 to deply updates throughout the LAN, I have one Upstream & on Downstream.  Everything has been working fine, until this morning when I attempt to sync the downstream to the upstream it fails.  I can ping back & forth not sure what's happened.
After (2 of us) electing to approve ONLY security updates in WSUS and being extremely careful not to include any updates with Windows 10 in the subject we are left with Windows 10 update 1803 being deployed throughout the company. The deployment is an issue in itself, but the greater concern is how these updates became approved.

Once we discovered 1803 being deployed I went back into WSUS and saw a host of Win10 related updates as being approved, none of which were seen the day previous when the approvals to security patches were made.

Has anyone seen this before of have a logical explanation? Other than the possibility of two of us overlooking the slew of Win10 updates the only related thought I can offer is that the WSUS server was restarted between approval and deployment (to install its own updates).

BTW - no-one has access to WSUS other than the 2 admins that worked together on approving the updates.

I have WSUS server (running on Windows server 2012 R2).  The updates sections show that the 2018-05 Cumulative Update for Windows 10 1709 for x64 based systems (KB4103727) is needed by 2 devices.    When I look at these 2 devices, they show that they need this update.   I have a total of 8 Windows 10 1709 devices.  Six of them have installed the 2018-05 cum update.  Hoever, even these 6 installed over the course of several weeks.   How can I force the windows 10 monthly updates to install when they've been downloaded to the WSUS server instead of waiting until some random date/time?  The updates are approved, do not show any failures, they just seem to sit there with approval status = install, and installed status = not installed.
I find the the Window 1803 is not available to deploy through the WSUS. Do I need to select the "Updates" in the Classifications". please note that under "Product" tab, I have already select Window 10 Version 1803 and Later Upgrade & Servicing Drivers.

Two Hyper-V virtual operating systems running Server 2016 Datacenter are unable to install Windows updates.

The Hyper-V base server and both of these virtual servers have had Windows activated.

I have run the Windows Update Troubleshooter and it says "Potential Windows Update Database error detected" and "Not fixed" (see the screenshot).

Windows Server Update Server is not being used in this environment. The Hyper-V base server has installed all Windows updates.

What can be done to fix this issue so that the updates will successfully install on these two Hyper-V virtual operating systems?

Windows Update Database error

We have a WSUS server issue.  In short, there are computers that are showing "critical" updates that are "needed", yet when we look in the UPDATES view, and try to filter by "Critical updates" that show status of "unapproved", there are none.  Not sure what is causing this anomaly. It's a 2012 Server, with the latest WSUS version.
Windows 7 workstations.    50 computers have not reported status for more than 30 days.  The check in status are random across workstations. Some 30 days some more.

I performed the following on a single workstation.

      1. netsh winhttp reset proxy

After executing the command I  restarted the  workstation

      2. Executed the following commands on workstation
wuauclt /detectnow /resetauthorization
wuauclt /reportnow

The workstation was not checking in.
After carrying out these commands the Windows Update utility can be started to search for updates. At this point the client should register with WSUS after 15 minutes.   Nope did not ever check in....

I then ran the diagnostics report attached using the utility here.
            a. https://www.solarwinds.com/free-tools/diagnostic-tool-for-the-wsus-agent/registration (Report Attached)
      1. Reset WSUS repository on workstation   ( This did not help)
            b. https://gallery.technet.microsoft.com/scriptcenter/Reset-Windows-Update-Agent-d824badc

Final Error IS 80244018 as seen in attachment

WindowsUpdate Log File Data
    06-01	10:59:31:440	 836	1750	Agent	*************
2018-06-01	10:59:31:440	 836	1750	Agent	** START **  Agent: Finding updates [CallerId = <<PROCESS>>: sftservice.exe]
2018-06-01	10:59:31:440	 836	1750	Agent	*********
2018-06-01	10:59:31:440	 836	1750	Agent	  * Online = Yes; Ignore download priority = No
2018-06-01	10:59:31:440	 836	1750	Agent	  * Criteria = "( IsInstalled = 0 and IsHidden = 0 and 

Open in new window

In WSUS, Can I filter approved updates by date range?  I am trying to figure out whether an approved update caused a network issue with some laptops NICs, but I can't figure out how to filter by date.  If I select approved updates, it will crash the update services portal since it lists all updates (60k +)
We have a WSUS server that provides a validated list of Windows Updates.  The product PCs Windows 8.1 and Windows 10 will use this list to determine which updates to download from Microsoft Windows Update Server/store automatically.  Once the validated patches are download automatically, the user will decide when to install the updates manully.  This works currently.  However, I am able to select "Check online for updates from Microsoft Update" to download and install the unqualified updates manually.  Is there a way to prevent the user from selecting "Check online for updates from Microsoft Update" to download the unqualified Windows updates and not breaking what have been working?
Hello I'm trying to use WSUS to update an offline machine using Ad Hoc.  Not sure how to accomplish this, or if its even possible?

WSUS servers not reporting back - The Computer has not reported status in 7 or more days

We recently set up a WSUS enviornment and ALL the servers (Server 2016) reported in fine last week but have not since - they are all online -the client computers (W10) are reporting back ok.
I have checked the reg settings and have the WSUS server listed, windows update service is set to Manual but running.

Any ideas?
Running "winver" from the command prompt shows that I am on Verion 6.1 7601 SP1

When I go into "Windows Update, View Update History" I see lots of FAILED updates in the last 2+ months

When I try to run "Windows Update" again it still fails, but all the other Win7 PCs on my WSUS server work

What do you recommend ?
We have the following configuration:

a WSUS server and the 1803 is NOT approved with the following global WSUS GPO's

Delivery Optimization Mode is set to Bypass
Allowed Sign updates from intranet MS update service location: enabled
Do not allow update deferral policies to cause scan against WU: enabled
Specify intranet location: http;//OURWSUSServer:8530
Active Hours: 7am - 9pm
Turn off access to all WU Features: enabled
We have lower Computer OU polices to configure Auto Updates at a certain time and enabled client side targeting
We noticed that computers were getting the v1803 update (which we do not want at this time as we just want 1709). After doing some digging around the great Google, i came across an article that suggested to change "Select when preview and feature updates are received" to use Semi-Channel and deferred it for 365 days.

Is there anything else we need to set to block to NOT receive v1803.

I have laptop users on Win10 Pro ver1607 and would like to upgrade them not to ver1703, then ver1709, etc - I'd like to upgrade them from Win10 ver1607 straight to ver1803 (or whatever is the latest supported, you understand my intent).

1. Is it possible to upgrade to the last version, or do I have to incrementally upgrade to each version in turn?
2. Can I use Powershell to upgrade to the version(s) instead of WSUS or Group Policy? WSUS has been problematic at best for this, and I don't care to keep using WSUS unless I absolutely have to. (Group Policy is problematic for remote users, and I don't care to discuss GPOs for this, please do not recommend/spend time discussing)
WSUS not working properly. Lots of wsus pool errors in the event log (5011, 5012, 5013, 5017 and 5038). Cant get the console to load. w3wp.exe and sqlservr.exe using all of the CPU. Is there anything I can try before I reinstall?

99% of all our computers are stating "not reported yet".  We built the new WSUS server and configured the GPO on Thursday.   The WSUS server is listing all the computers but most of them have not reported.

What would cause this?
A Windows 10 computer failed to successfully load Windows while installing Windows updates so I booted off of a Windows 10 installation USB drive, chose the "Repair" feature and then was able to perform a successful system restore to a previous point in time.

This Windows 10 computer now boots into Windows and works fine except that it is unable to install the latest Windows update (see the screenshot).

If I manually download then install this update then the update appears to install but after rebooting when I log back into Windows I either receive a message that the update didn't install of when I go back into the Windows updates I see that the same update still needs to be installed.

I have also performed the following steps attempting to resolve this issue but haven't yet been able to fix this issue:

1. Have run the Windows update troubleshooter (which always says that it has found and fixed issues but ultimately doesn't fix this issue).

2. Have run the SFC /scannow commands and then the DISM.exe /Online /Cleanup-Image /Scanhealth and then the DISM.exe /Online /Cleanup-Image /Restorehealth commands

3. Have emptied the temporary and temporary internet files

4. Have run full scans for malware and viruses and no problems have been detected.

I have also rebooted several times and have tried installing the updates using different administrator accounts but this Windows update still won't install.

What else can be done to fix this issue so that I will…
I'm running a new install of WSUS, on windows server 2016, fresh install, and the server is not used for anything else, but WSUS.
All my servers and computers show "needed count" for updates with large numbers.  Even after I install updates on the clients or servers, the number never goes to 0, how do I install all the needed updates on my servers/workstations?

The 2nd problem is, for a few computers, it looks like the computers have contacted the WSUS server, a few weeks ago, but there's no status report, and there's no info about the computers.  Any idea's how to resolve?

Win10 1803 systems are not offered the 2018-05 Cumulative updates (KB4103721) when connected to WSUS (here: wsus on 2012 R2, but it should not even matter)

As https://social.technet.microsoft.com/Forums/en-US/44fc841c-3e39-49c1-b1a0-a633c76e2796/win10-build-1803-clients-monthly-cumulative-update-not-offered-may-2018-kb4103721?forum=winserverwsus outlines, the new windows build refuses to work with WSUS (like it has happened before with server 2016 and Win10 1607).

Please reproduce and upvote the technet thread, so Microsoft becomes aware.
Points to anyone who takes the time to reproduce.

PS: 1709 Build 16299.402 (if you have it) is unable as well.


Windows Server Update Services (WSUS), previously known as Software Update Services (SUS), is a computer program developed by Microsoft that enables administrators to manage the distribution of updates and hotfixes released for Microsoft products to computers.