This window will show the virus and spyware definition versions, as well as when they were last updated.
In other words, just deploying the latest Definition Update for whatever installed Malware Protection Engine would fix these two Nessus alerts 😀 Hands-on!
In both instances after doing this, my updates started working again.
You may also wish to run a SFC to see if anything need repaired.
Update the WSUS server configuration Note that the following will run on a WSUS server built-in Windows 2012 R2. Update Category Collection $products | foreach $subscription. Save() # Select the classifications I want and update the WSUS config $subscription = (Get-Wsus Server). Update Classification Collection $classifications | foreach $subscription. Save() There are two methods to deploy definition updates either by using an ADR (Automatic Deployment Rule) or manually.
# Select the products I want and update the WSUS config $subscription = (Get-Wsus Server). Get Update Categories() | Where $coll = New-Object -Type Name Microsoft. Get Subscription() $classifications = (Get-Wsus Server). Get Update Classifications() | Where $coll = New-Object -Type Name Microsoft. The ADR method is documented on this page KB919772 But let’s do it manually as I don’t like ADR 😛 Let’s figure out what needs to be deployed: # Select my target group: Windows 7 computers $targetgroup = (Get-Wsus Server).