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. Q1R90fsVi0/hqdefault.jpg' alt='Windows Checking For Updates Hangs' title='Windows Checking For Updates Hangs' />No more missed important software updates UpdateStar 11 lets you stay up to date and secure with the software on your computer. Windows Updates hangs stuck at searching, checking for updates and takes an unusually long time to scan and install updates. Also fix cant install updates. Free Download Kaspersky Antivirus Software For Mobile. Symantec helps consumers and organizations secure and manage their informationdriven world. Our software and services protect against more risks at more points, more. Capture.PNG' alt='Windows Checking For Updates Hangs' title='Windows Checking For Updates Hangs' />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. Windows 10, version 1709 basic level Windows diagnostic events and fields. In this post, we will see how to solve the problem of. Windows update getting stuck on checking for updates step. This problem of windows updates hanging on checking. Windows Server 2012 Standard I have been tasked with updating some servers here at the office, and one of them is giving me problems. Windows Update has now been in. When a Windows program crashes it will popup a program has stopped working message where you can check online for a solution or close the program. While this is user. FIX Error Message 0x80070424 Received in Windows Update or Microsoft Security Essentials MSE Many times when Windows users try to run Windows Update or. Update. Status. Per. Computerdbo. tb. Propertydbo. Flattended. Revision. In. Categorydbo. tb. Revision. In. Categorydbo. Revision. Languagedbo. More. Info. URLFor. Revisiondbo. tb. Security. Bulletin. For. Revisiondbo. KBArticle. For. Revisiondbo. Bundle. Dependencydbo. Bundle. At. Least. Onedbo. tb. Bundle. Alldbo. tb. Prerequisite. 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.