Failed Updates for Excel 2003 (KB978474)

Does anybody have any idea why the recent update from MS for Excel
(KB978474) would not update and what can I do to get this update through?

I keep getting the below message and not much of any description what I
could do.
The problem is that:
1. After failure, the Windows Update does not stop (unless I turn it off
manually) and still tries to install this update
2. After each update Excel is somehow corrupted or uninstalled. After
attempt to start it, it reinstalls and than runs seemingly OK.

I seem to be unable to break this vicious circle.
I tried to reinstall Excel 2003 but this did not change a thing.
I also tried to install Excel 2007 on this PC to replace Excel 2003 but this
did not stop attempts to update the Excel 2003 either!!!
So I uninstalled Excel 2007 and re-installed Excel 2003.
Still same thing. It tries to update it, but it fails. And Excel after that
must be reinstalled (does not take a lot of time but it is just wrong).

Interesting thing is that other updates in this recent batch from MS went
through OK (I think there were tow more).

On my other PC all of these updates went OK.
But I cannot find any difference in how it is installed on both computers. I
would swear it is identical installation, but obviously I must be wrong.
Something is different.

Would anyone have an idea what that could be?

+++++++++++
Failed Updates

For help installing an update successfully, see the solution under each
problem description.

Problem: Please check your update history for a description.

Microsoft Office 2003
Security Update for Microsoft Office Excel 2003 (KB978474)

++++++++++++

...and under description page I can only see the Failed Status for update
with no description of the problem.

For home users, no-charge support is available by calling 1-866-PCSAFETY
(and/or 1-866-234-6020 and/or 1-800-936-5700) in the United States and in
Canada or by contacting your local Microsoft subsidiary. There is no-charge
for support calls that are associated with security updates. When you call,
clearly state that your problem is related to a Security Update and cite the
update's KB number (e.g., KB978474).

Or you can...

Start a free Windows Update support incident request:
https://support.microsoft.com/oas/de...spx?gprid=6527

The Consumer Security Support home page & Microsoft Update Solution Center
also offer support options
https://consumersecuritysupport.microsoft.com/
http://support.microsoft.com/ph/6527#tab3

For more information about how to contact your local Microsoft subsidiary
for security update support issues, visit the International Support Web
site: http://support.microsoft.com/common/international.aspx

For enterprise customers, support for security updates is available through
your usual support contacts.

Uninstall the update. Then ignore the prompt to reinstall it again from
automatic updates or, stop the update service and clear out the contents
of Windows\Software Distribution\Download.
Then manually download the update from the links on this page:
http://support.microsoft.com/kb/978474

Look under the " Known issues with this security update " heading for
the indirect and direct download links.
*Save it*, then install it with *all* programs and browsers closed.

I have the same problem. I can"t update this file. kb 978474
It says.Failed. Code 779 = UNKNOWN wrong ?

Facts: I use Vista Business. Office Standard Edition 2003. (An OLDER version)
Note:The Office 2003 is before the time of Vista. It should NOT impact
but I dont know for sure ? Only Microsoft can answere.Office 2003 is made
for XP
but it has worked out on my Vista since july 2009. All updates are OK since
then.
All of the ohters updates did function. But not kb 978474 ? Why ?

Reflexion: The Office excel is from 2003. Maybe ( I don"t have FACTS )
it causes a CONFLICT in one or another way ? Only Microsoft can tell.
Maybe we should use a Office from 2007 ? My belive (only belive) not facts,
is that Office 2003 should work out. All of the other uppdatesmhas worked
out. Security MS10-017.So my belive is that Office 2003 should work out.

At friday mars 11-2009 I contacted Microsoft free support about updates,
to try to get some information about this update kb 978474. Whats wrong ?
I"ve been searching all over the internet and Microsoft.
Maybee ohters have the same problem ? Or is it " unique " for a few Vista pc ?
I don"t know .Only Microsoft can tell. I"m waiting for reply/ anweres.
Normally this update kb 978474 should work out.
It"s a " mystery " ?

Information:When I googled with: Fail update Microsoft excel 2003 kb 978474
I found this information and your question Mr Bandicot.

And the answeres from Mr PA Bear MS MVP.
All his information is very good. I "ve used it.
This is the only way we can try to solve the problem.
I do hope that Microsoft support can help us ?

It feels good that I"m not the only one that has this problem

Not if you are giving us a hex value...

<cmd_output OS="W7">
C:\>set /a c = 0x779
1913
C:\>net helpmsg %c%

Some data remains to be sent in the request buffer.
</cmd_output>

But more important than the code's value is its context. Where are you
seeing this? Can you find either the 779 you are reporting or 1913 (that
string's decimal equivalent if the code you are reporting is a hex value) in
any log files the install creates or changes? And if you are not getting
good diagnostics from running an update automatically, try downloading it
and installing it manually. You may find that you have additional options
for increasing the diagnostics (e.g. adding /verbose to the command line if
that is available) and in any case could supplement any and all diagnostics
that you are getting by running ProcMon when you do the install attempt.

I eventually managed to get this update installed. I downloaded the update installation file, cleaned out the Windows\Software Distribution\Download folder and quit all programs before running the update
The update then failed with error 1402 that it couldn't update registry key H_Key_Local_Machine\Software\Microsoft\Windows\CurrentVersion\Run\OptionalComponents\MSFS.
Checked this folder out and found no permissions had been allocated. Only when I gave the group 'Everyone' full permissions on folders IMAIL, MAPI and MSFS did the update succeed. Hope this helps someone.

I just checked Add or Remove Programs and KB978474 shows as being installed.
Also, after I did the manual install above, the auto install that had been giving grief then went through fine as I presume it found that KB978474 had been installed. BTW I'm running Win XP Pro and Office 2003 SP3

I have tried that:

1. I downloaded the file manually
2. I cleaned that directory from all the failed downloads
3. and updated the file manually by Run

What happened was: after the update finished I got the Office 2003 Setup
window up telling me that Office Setup i configuring my files.
After a while I got the Microsoft Office Professional Edition 2003 window
with error message as follows:
Error 1904. Setup cannot register module C:\Program
Files\Microsoft\Office\OFFICE!!\1033MSRCLR40.DLL. If you click "Cancel" ..."
and so on.
Shortly it suggests that I reinstall or repair Office 2003.

So I did but I keep receiving this message again and again.

Now, the interesting part is that my Excel2003 seems to be working, at least
so far as normal.
Also Windows Update stopped trying to download this terrible update. However
the list of updates in that webpage does not appear to recognize the fact that
I updated it manually.

Therefore my new two questions:

1. Is there a way to check that this last security update has been actually
installed and it's working?
2. What is that file responsible for that I keep receiving the error message
while repairing the setup for MS office Proff 2003?

This worked for me. I'm running XP (SP3), and do not have Office 2003, but
I am running Office 2000. But yet, this update kept repeating everyday, and
failing everyday.

All I did was go into the registry, and I found the folders IMAIL, MAPI, and
MSFS in the location specified. These folders were all empty. I right
clicked each folder, and changed the permissions to "everyone," and then the
update finally worked.