"James Fabulous" <> wrote in message news:%
....
> I found suggestions to check security policy settings comparing
> local settings to effective settings - everything checks out here
> (and we are not currently using any non-default group policy).
> 0.080: Update.exe extended error code = 0xf004
Nevertheless the code implies that something about those accounts
is deficient for installing that update.
BTW I couldn't find the extended error code documented as a hex
value but I was able to find it as its equivalent decimal value of 61444:
http://www.microsoft.com/technet/pro...pdte.mspx#EAAA
<TITLE>Inside Update.exe - The Package Installer for Windows and Windows Components</TITLE>
<quote>
61444 STATUS_INSUFFICIENT_PRIVS
You do not have permission to update %1.
Please contact your system administrator.
</quote>
My guess would be that you have locks on some keys.
I would try running RegMon to monitor the update
in hopes that that could uncover the accesses which are failing.
(FYI RegMon is freeware from SysInternals.)
Have you checked newsgroups which specialize in security
for your OS? Some other approaches are described in these:
http://groups-beta.google.com/groups...oft.*.security
(Google Groups search for
61444 OR F004 OR 0xF004 OR 0x8007F004 OR 8007F004 group:microsoft.*.security
)
Another possibility is that the code is being used to signal another
type of problem during the update. For example, some XP users
have discovered that an "access denied" symptom can be avoided
by removing a Read-Only flag from branches.inf. (I just noticed
branches.inf referred to as an Installer binary in the above document
while searching it for " log" and was reminded of that.) For diagnosing
that without knowing about it you could use FileMon, another freeware
tool from SysInternals.
Good luck
Robert Aldwinckle
---