up vote 0 down vote favorite
share [g+] share [fb]

I want it to finish properly, but I also don't have time to babysit it. (Why couldn't they just include a volume-size-based progress bar?) Is it really true that sysadmins are fine with this? Is there some secret that I'm missing?

link|improve this question
100% accept rate
feedback

1 Answer

up vote 1 down vote accepted

If you're running it on the command line you're out of luck. If you run it in the GUI interactive mode there's a progress bar.

Since the process is really designed to run in the background quietly once a month I'm assuming the programmers didn't see a need to write a progress indicator into the command line version.

link|improve this answer
It comes up as part of Windows Update...does that mean I'm doing WU wrong, or am I supposed to fish for the process and kill it every WU and run it when I want to instead? – Kev Sep 21 '09 at 22:58
It runs every month-its not supposed to come up during Windows Updates. What are you seeing exactly? – Josh Budde Sep 22 '09 at 2:01
After every Patch Tuesday, I run WU, and part of WU, it stalls the WU progress meter for a number of hours. If I look at what's taking up CPU cycles, it's the MSRT. I guess when the latest MSRT comes out, it runs it immediately after installing it. Worse, the GUI for it doesn't come up, so it just makes the WU GUI look like it's frozen or something. – Kev Sep 22 '09 at 2:24
It shouldn't cause that-maybe you should remove the MSRT and let it be reinstalled by WU. – Josh Budde Sep 22 '09 at 2:29
1  
That happens for me to. I just install everything else first, reboot, and then run the MSRT update that night before leaving (it doesn't need a reboot). – charlesbridge Sep 22 '09 at 11:26
show 1 more comment
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.