As mentioned in Demystifying “Dual Scan”, configuring a combination of policies on Windows 10 1607 can result in those clients automatically [and unexpectedly] scanning against Windows Update, as well as subsequently ignoring deployment instructions from WSUS. We heard feedback from on-premises administrators that they needed the deferral policies only for ad hoc scans against Windows…

(this post contributed by the .NET team. Note that WSUS 3.0 will fail to install if .NET 4.6 or later is already installed on the machine, per our previous article describing this behavior) Hi WSUS Admins, The Microsoft .NET Framework 4.7 will be made available via Windows Server Update Services for Windows 7 SP1,…

Update: a new post on the upcoming feature to support Dual Scan in the on-premises scenario has been published. Please refer to that post for details on how to use the new policy and what to expect going forward. How Dual Scan came to be With the combination of Windows Update for Business and Windows…

(Alternative title: “Help, I followed the steps provided earlier and I’m still seeing failures!” This applies to anyone who missed KB 3159706 when it was offered as a hotfix to Windows Server 2012/R2, and who subsequently enabled synching of Upgrades in their environment before patching WSUS. The Upgrades that were likely downloaded most recently happen to be for the…

As you may have seen, there has been an update to the extended support lifecycle for WSUS 3.0 SP2 (WSUS 3.2). We received feedback that ending this product’s life in July 2017 would cause a significant disruption for those Windows Server 2008/R2 deployments that planned to rely upon it until January 2020. As such, the…

A new update is available for Windows Server 2012 and 2012 R2. This update requires manual steps in order to complete the installation. While the KB itself covers those steps, this post provides additional details on the release. What KB3159706 does Windows 10 feature updates (denoted by the “Upgrades” classification in WSUS) are staged in encrypted…

Here are the facts: KB3148812 requires some manual steps to complete its installation Failure to perform these steps leads to two issues: loss of WSUS console and client scans against WSUS Performing these steps (as listed today) fully resolves the WSUS console issue There is a chance that you will see client scan failures even…

UPDATE: A newer post regarding KB3148812 is published at http://blogs.technet.com/b/wsus/archive/2016/04/22/what-you-need-to-know-about-kb3148812-part-two.aspx. Hi WSUS admins, just a quick post to let you know that we've received word of some issues happening (e.g., WSUS admin console is inaccessible, clients can't contact WSUS) in the wild after installing KB3148812. It is critical functionality; however, you don't lose anything by skipping installation…

Many of you have already seen the announcement that Configuration Manager can now be set up to sync Office 365 ProPlus updates directly. This scenario is a direct response to requests for control of distributing these updates, and is an improvement on the past model (wherein Office 365 ProPlus updates circumvented Microsoft Update and WSUS…

(Alternative title: "Help, I synched Upgrades before installing the patch!" This applies to anyone who missed KB 3095113 when it was offered as a hotfix, and subsequently enabled synching of Upgrades in their environment. The upgrades that were downloaded happen to be from the Windows 10 1511 feature upgrade, but these steps could be modified…