"Nico" <> wrote in message
news:9B7605BC-B0B9-4FD5-9D93-...
> The last entry from the logfile:
>
> 2006-12-24 20:51:06 2904 b5c Misc = Process: C:\WINDOWS\system32\wuauclt.exe
> 2006-12-24 20:51:06 2904 b5c AUClnt Launched Client UI process
> 2006-12-24 20:51:06 2904 b5c AUClnt AU client got new directive = 'Install
> Approval', serviceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, return =
> 0x00000000
> 2006-12-24 20:51:06 2904 b5c AUClnt AU client creating UI plugin,
> clsid={3809920F-B9D4-42DA-92E0-E26265E0FB89}
>
>
> 2006-12-24 20:51:06 2904 b5c AUClnt FATAL: Failed to show client UI,
> directive=5, hr=800705B4
You can do the same kind of analysis with this code as I did with the other,
e.g. convert the lower half to decimal and search for meaning with the
decimal equivalent. However, in this case it is just as easy to search for
the exact hex string, the only additonal difference needed is to prefx the
hex string with 0x.
http://msdn2.microsoft.com/en-us/library/ms695782.aspx
(Live Search for
0x800705b4 microsoft codes
)
<quote>
-2147023436 0x800705B4 This operation returned because the timeout period expired. *
</quote>
Judging by the timestamp differences, I would say the code was bogus
and that you should just interpret it as "something is wrong". I suspect
that there is additional context for this scenario that you are not disclosing,
so further guessing may be futile.
HTH
Robert
---
> 2006-12-24 20:51:06 888 674 AU AU setting pending client directive to
> 'Install Approval'
> 2006-12-24 20:51:06 888 674 AU Another AU detection is already in progress,
> using it
> 2006-12-24 20:51:20 888 674 AU AU found 1 sessions to launch client into
> 2006-12-24 20:51:20 888 674 AU Launched new AU client for directive
> 'Install Approval', session id = 0x0
>
>