WSUS hangs on Cleanup wizard for Unused Updates, then disconnects from console. It does not run much better when written without a CURSOR. I modified it to use a WHILE loop and it deletes about 1 per minute here which is the same as the old code with a CURSOR. Not surprised. To be frank, using a WHILE LOOP just turns it into a manual CURSOR, making it no better off than using the CURSOR construct in T SQL. The correct approach here is to write the code with a SET BASED approach. Unfortunately, as youre about. In order to use the set based approach, youll need to take the code from sp. Delete. Update and modify it to join directly to the table of GUIDs to delete. Execute the whole thing in oneDELETE statement. Of course, part of the other problem that contributes to the performance issues is that sp. Delete. Update LSOuses CURSORs. Delete. Update retrieves a list of Revision. IDs, and then calls sp. Delete. Revision for each of those. Revision. IDs. And as weve already seen, some updates may have a large number of Revision. IDs. sp. Delete. Revision is where the real work is done. At the crux of that proc, are deletes from these tables dbo. Event. Instance this will be a time killer as well, depending on how many clients affected a given update, and how much activity surrounded that updatedbo. Deploymentdbo. tb. If youre using Group Policy to configure your updates, you can query the registry for the Target Group and WSUS server values C REG QUERY HKLMSoftwarePolicies. On our customer servers WSUS shows two missing Skype for Business 2015 rollups KB 3061064, also for pcs which havent skype installed. Scnreenshot 1 For all pcs. WSUS vs missing Check online for updates from Microsoft update issue. Can they still check for updates online independently of the WSUS server Download Deep Freeze Standard to protect your Windows PCs. Computer restore software best suited for home users or small businesses up to 10 computers. Start your 30. WSUS allows companies to defer, selectively approve, choose when delivered, and determine which devices receive updates. Summary Learn how to use Windows PowerShell to automate basic administrative tasks on a WSUS server. Microsoft Scripting Guy, Ed Wilson, is here. Today we. I had a situation where WSUS was failing to download updates after moving content from one local drive to another. I thought resetting might fix it but it didnt. I changed the status of these updates to not approved, but WSUS still wants to report them as needed updates for the stations that downloaded the files before I. Update. Status. Per. Computerdbo. tb. Propertydbo. Flattended. Revision. In. Categorydbo. tb. Revision. In. Categorydbo. How To Remove Approved Updates From Wsus' title='How To Remove Approved Updates From Wsus' />Revision. Languagedbo. More. Info. URLFor. Revisiondbo. Security. Bulletin. For. Revisiondbo. KBArticle. For. Revisiondbo. Bundle. Dependencydbo. Bundle. At. Least. Onedbo. tb. Bundle. Alldbo. tb. Prerequisite. Starcraft Map Cracker on this page. Dependencydbo. tb. Installed. Update. Sufficient. For. Prerequisitedbo. Prerequisite. And all of the associated transaction wrappers and error checking for each and every deleted row from each of those tables to ensure continued data integrity in the database. So while the code above making a simple call to sp. Delete. Update looks quite simple on the surface. LOT of activity going on to make that one update get deleted. If you wanted to speed it up. Get. Obsolete. Updatesto. Cleanup to get a list of Update. IDs, then build a list of Revision. IDs from that, and then join that temp table of Revision. IDs to each of the 1. Which would force all of those deleted records into a SINGLE transaction, and probably whatever gains you got from switching from procedural logic to set based logic would be lost in the massive overhead of managing a transaction of. A possible compromise would be to execute a set based DELETE by Update. ID, so youd capture the Revision. IDs for a given Update. ID, and then delete across all 1. Revision. IDs except where that list aint so short. But still. this compromise might well speed things up, as the loop for Update. IDs is likely only measured in the hundreds, where as the loop through all Revision. IDs is sometimes measured in the thousands or tens of thousands depending on ifwhen the server was last purged. Lawrence Garvin, M. S., MCSA, MCITP EA, MCDBASolar. Winds Head Geek. Microsoft MVP Software Packaging, Deployment Servicing 2. My MVP Profile http mvp. Lawrence2. 0R2. Garvin 3. The views expressed on this post are mine and do not necessarily reflect the views of Solar.