If you have a problematic Upgrade entry in WSUS, you may want to remove it. The next time you perform a sync with Microsoft, it will re-appear.
In my case, I had problems with “Windows 10 Pro, version 1607, RETAIL” and after a few weeks of banging on it, I found the best solution was just to delete it and have WSUS re-add it from Microsoft.
- Open WSUS, Expand UPDATES > ALL UPDATES and find the problematic upgrade
- Ensure there are no install approvals. If there are just remove them
- Start a PowerShell as an Administrator
- Type the following to commands
$s = Get-WsusServer
$s.SearchUpdates(“Windows 10 Pro, version 1607”) | foreach { $s.DeleteUpdate($_.Id.UpdateId) }Substitute the name of the update you are interested in removing. You do not need to enter the whole name, just a fairly unique portion of the text. This means that my example of Windows 10 Pro, version 1607 will actually remove
.
If you still have errors, run all of these codes in that same PowerShell window:
.
// disable Upgrades classification on local WSUS server
Get-WsusClassification | Where-Object -FilterScript {$_.Classification.Title -Eq “Upgrades”} | Set-WsusClassification -Disable
// delete all update content on the current server belonging to the 1511 release
$s = Get-WsusServer
$s.SearchUpdates(“Windows 10 Pro, version 1607”) | foreach { $s.DeleteUpdate($_.Id.UpdateId) }
// enable Upgrades classification
Get-WsusClassification | Where-Object -FilterScript {$_.Classification.Title -Eq “Upgrades”} | Set-WsusClassification
// perform full sync
$sub = $s.GetSubscription()
$sub.StartSynchronization()
This information came from HERE and my MS Partner Thread HERE.
Click HERE if you receive an error similar to “Exception calling “DeleteUpdate” with “1” argument(s): “spDeleteRevision: cannot delete revisionid: 502004 because itis still deployed to a Non DSS Target Group”
0 Comments