MS update icon won't go away!

Three days ago the MS update icon appeared at the bottom right of the
Windows (XP Pro) taskbar. I'm used to this happening as I have my browser
set to automatically accept MS updates. However, it has stayed there for
the past three days and always indicates "Downloading updates: 0%". Is
there a way to get rid of the icon?

Steve.

Steve D. wrote:

> Three days ago the MS update icon appeared at the bottom right of the
> Windows (XP Pro) taskbar. I'm used to this happening as I have my browser
> set to automatically accept MS updates. However, it has stayed there for
> the past three days and always indicates "Downloading updates: 0%". Is
> there a way to get rid of the icon?
Hi

Clean out the Download folder (WU5's temporary download folder)
located here:

%windir%\SoftwareDistribution\

(%windir% is typically C:\Windows)

You can use the procedure described here:

http://v5.windowsupdate.microsoft.co...cleid=11&ln=en

You might need to delete the DataStore folder mentioned in the link
above, as well as the EventCache folder.

Note that a side effect of deleting the DataStore folder is that you
lose your WU v5 History listing (not critical).



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

"Steve D." wrote:

> Three days ago the MS update icon appeared at the bottom right of the
> Windows (XP Pro) taskbar. I'm used to this happening as I have my browser
> set to automatically accept MS updates. However, it has stayed there for
> the past three days and always indicates "Downloading updates: 0%". Is
> there a way to get rid of the icon?
>
> Steve.
>
>
>

"Steve D." wrote:

> Three days ago the MS update icon appeared at the bottom right of the
> Windows (XP Pro) taskbar. I'm used to this happening as I have my browser
> set to automatically accept MS updates. However, it has stayed there for
> the past three days and always indicates "Downloading updates: 0%". Is
> there a way to get rid of the icon?
>
> Steve.
>
>
>

I have the same issue. Has there been a corrrection? have you found a way
of deleting it?

"Steve D." wrote:

> Three days ago the MS update icon appeared at the bottom right of the
> Windows (XP Pro) taskbar. I'm used to this happening as I have my browser
> set to automatically accept MS updates. However, it has stayed there for
> the past three days and always indicates "Downloading updates: 0%". Is
> there a way to get rid of the icon?
>
> Steve.
>
>
>

"Torgeir Bakken (MVP)" <Torgeir.Bakken-> wrote in message
news:eL$035%...

> Hi
>
> Clean out the Download folder (WU5's temporary download folder)
> located here:
>
> %windir%\SoftwareDistribution\
>
> (%windir% is typically C:\Windows)
>
> You can use the procedure described here:
>
>
http://v5.windowsupdate.microsoft.co...cleid=11&ln=en
>
> You might need to delete the DataStore folder mentioned in the link
> above, as well as the EventCache folder.
>
> Note that a side effect of deleting the DataStore folder is that you
> lose your WU v5 History listing (not critical).
>
>
>
> --
> torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx


Thank you Torgeir, that worked great.

Steve.

"Steve D." <> wrote in message
news:OA$tgk%...
> Three days ago the MS update icon appeared at the bottom right of the
> Windows (XP Pro) taskbar. I'm used to this happening as I have my browser
> set to automatically accept MS updates. However, it has stayed there for
> the past three days and always indicates "Downloading updates: 0%". Is
> there a way to get rid of the icon?

Instead of doing that I would first try to find out what it was doing
(or supposedly doing.) Start by looking in the logs. Who knows,
you might find that something is blocking its path to the Internet and
fixing that would allow the update to download. There are two logs
to start with: ReportingEvents.log and WindowsUpdate.log
The first one seems to be analogous to the old V4 Windows Update.log
while the new one has an overwhelming abundance of so far
undocumented diagnostic data.

Other things that you could try doing in order to understand your
symptom better would be to see if you have a running BITS service
(e.g. from a command line enter sc queryex BITS would show you
its PID.) If there was one running I think that you could then use the
bitsadmin command to see if anything was in progress or queued.

BTW what happens if you doubleclick the icon? If it doesn't respond
it would seem that the service or some subtask of it is hung. Then it
would be interesting to know what else associated with the service
was hung too. Usually we can't isolate each service process-wise
(e.g. if that sc queryex gave you a PID of 1234 and you entered
tasklist /svc /fi "PID eq 1234"
you might find that BITS was running in the same svchost.exe
as a bunch of other services) but if it is listed by itself you could
use Task Manager's statistics for that process as indicators
of whether the service itself was actually doing anything.


Good luck

Robert Aldwinckle
---

I'm seeing symptom reported by Steve D, except I've been seeing it for a
couple weeks. ReportingEvents.log has a only one or a few entries for
each day, WindowsUpdate.log has hundreds of messages for each time the
system is started, but none appear to be error/failure messages. Single
or double clicking (left or right) the systray update icon has no effect
at all. Issuing the sc queryex BITS command you suggest yields
SERVICE_NAME: BITS
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 1 STOPPED

(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1077 (0x435)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 0
FLAGS :
The taskmanager shows three svchost.exe processes active for "system",
"local service", and "nework service", none of which are discernably
active.

Larry Mc

It looks as if my speculation about BITS was getting ahead of our
symptoms. I think now that the icon is provided by wuauclt.exe
and have evidence from FileMon that it starts and ends periodically.
When it doesn't have anything to do it is hardly noticeable in Task Manager;
so as long as the server doesn't give that task anything to do I don't
expect to see the SysTray icon.

If wuauclt is hanging around and generating hundreds of messages
I think that that will be anomalous and you should examine your log
to try to understand what it is doing. I have noticed that some users
appear to be getting in a loop with the server but then it gets terminated
with error code 0x80244010 which would be different from your
symptom too.

BTW I have figured out a "Windows way" of summarizing what
an execution of wuauclt does: use Search Companion (Win-F)
to search for all files in %windir%\SoftwareDistribution modified today;
then sort the list by Date Modified. (Alt-V,I,M) This method also
makes it easy to see what is in any .cab files that were downloaded.

What is the history of your SoftwareDistribution directory?
E.g. did you get WUV5 early? do you have 842773? XPsp2?
Did you follow Torgeir's suggestion to clean it up?


HTH

Robert
---


"Larry McMains" <> wrote in message
news:Xns956CC9E2D8022newsmcmainsmnnet@216.148.227. 77...
> I'm seeing symptom reported by Steve D, except I've been seeing it for a
> couple weeks. ReportingEvents.log has a only one or a few entries for
> each day, WindowsUpdate.log has hundreds of messages for each time the
> system is started, but none appear to be error/failure messages. Single
> or double clicking (left or right) the systray update icon has no effect
> at all. Issuing the sc queryex BITS command you suggest yields
> SERVICE_NAME: BITS
> TYPE : 20 WIN32_SHARE_PROCESS
> STATE : 1 STOPPED
>
> (NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
> WIN32_EXIT_CODE : 1077 (0x435)
> SERVICE_EXIT_CODE : 0 (0x0)
> CHECKPOINT : 0x0
> WAIT_HINT : 0x0
> PID : 0
> FLAGS :
> The taskmanager shows three svchost.exe processes active for "system",
> "local service", and "nework service", none of which are discernably
> active.
>
> Larry Mc