It does spike a bit occasionally, but in general it is hovering around 10-15 or less.
Seems like a whole lot of nothing going on.
Main Topics
Browse All TopicsHad a situation where a customer had Exchange dismount the Information Store due to low disk space. Appears that WSUS 3.0 had consumed in excess of 100GB of space with content. My fault. Guess I had too many things products and update types selected.
Anyway, started the handy WSUS Server Cleanup Wizard to purge unused, unneeded, expired and superseded updates. The process of declining the various updates went very quickly. Then it started Deleted unused updates. That is pretty much where it stopped. It has been stuck there for almost an hour. It hasn't really hung. It is responsive...sort of. I can move the dialog box. WSUS still shows Running. There just doesn't seem to be anything actually HAPPENING.
SqlServer.exe process cranked up to about 25% CPU and stayed there. It's really busy doing something, but I don't see any improvement. None of the files have been deleted yet. We are still at low diskspace waiting for whatever is happening to finish happening.
I fired up the wizard on one of my test servers (WSUS 3.0 SP1). Behavior (or lack thereof) is pretty much identical. Is this normal? If it is, I think a better dialog that actually shows some sort of progress at doing SOMETHING would be helpful.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
seems like its doing something....10-15 isn't low by any means
see this article on disk monitoring if you want to see exactly what is going on
http://www.oreillynet.co
Fascinating article. Thanks for the link. You will definitely earn at least a portion of the points awarded for this question.
When I went back to check on both of the cleanup processes, the progress bar moved slightly on each. That seems to be an indication that it is attempting to do something. I guess I need to be patient. Meanwhile I am watching normal usage continue to dig into the limited available disk space. Very frustrating.
It finally finished...after about 4.5 hours. Not much change to the disk space. Reluctantly, I restarted the wizard and ran it again. This time it finished in less then 10 minutes having deleted nearly 75GB of content. Go figure.
Jimmypants, thanks so much for the informative link. I am a smarter person then I was at the start of the day. Therefore I am awarding you all the points.
Hi Guys,
I have the same issue here but with SBS2003R2 and WSUS3. The Cleanup wizard was started last night at about 1800 and is still running this morning (now 1135) it has started advanving through the deleting phase but very very slowly.
Is the AutoApprove process supposed to be active at this time, it isi showing bursts of 20% CPU time. SQLServer has extended burts of upto 90%.
This is on my small dev network with 5 users. We had to abort the same exercise on my customers server. Can anyone explain why this process takes so long and is this normal ???
Regards
Trevor
What I did was stop the GUI version of the WSUS cleanup wizard, press the stop button and if necessary use the task manager to drop the job. This didn't appear to cause issues on several machines that I did it on.
Then use the command prompt version. The command line I used is below, google the tool name.
c:\WsusCleanUpNew\WsusDebu
Didn't have any problems on any machines even after stopping the WSUS gui.
Hope that helps
Trev.
Hi Vantageit,
Do leave it too long . . . I believe that the GUI may even crash and never get there. I left mine for nearly 2 days before giving up just to see if it did ever get there. Worst case is that you corrupt your WSUS database and have to reinstall and take the hit of a long synchronisation and maybe a big download to catchup but at least you know you'll complete in time.
I haven't had the WsusDebugTool.exe crash or not complete as yet. I'm sure there are scenarios when it can't cope but hey no tool is perfect. Again worst case is you start over. Yeah bung it in a batch ready for the od tidy up you can get all of the options by running it with out parameters.
Good luck
Trev
Business Accounts
Answer for Membership
by: jimmypantsPosted on 2008-07-11 at 08:47:54ID: 21983442
try running performance monitor. at a run prompt type "perfmon". see if the average disk queue length is high. this indicates disk usage and that sometihng is actually happening