Office 2010 Service Pack 2 install fails

Try using the Fix It in method 2 of this tip to try and nuke any "bits and pieces" of 2003 that may be lurking in your system

KB 2639197 Uninstall Office 2003

http://support.microsoft.com/kb/2639197  2003**** (First, make a copy of your NORMAL.DOT)

Method 1: Uninstall from Control Panel

Method 2: Uninstall using Fix it 50416

Method 3: Uninstall with the Program Install and Uninstall troubleshooter

Method 4: Remove manually

Method 2 in this tip does a more thorough job that the “normal” uninstall via Programs and Features (aka Method 1 in the tip). The Normal uninstall is designed with the assumption that you will be re-installing Office. It does NOT delete everything. It leaves configuration files like NORMAL.DOTM and other templates etc. and it also leaves configuration Registry entries. These “carry-overs” may contain corruption that is causing your problem.

---

Thanks for the advice, tried this did not quite work received a message about Powerpoint Reader 2007. So I deleted this, put in my Word 2010 disk clicked on repair. When this was finished I tried to install update and it WORKED!!

Thanks

So install of SP2 with win7 in 32 bit office 2010 occurred yesterday along with a slew of other Office 2010 updates, mostly security related. Today, no Office program will run because MSORES.DLL is invalid image!! For some reason system restore isn't working?? So finally I figure to uninstall SP2 update, which BTW gives an error message at end, saying "Uninstall was not successful". However now Excel at least starts. Word is starting and as usual when it starts Office has to do a long configuration process before the program actually runs. Update: Word is running now too.

I would do a repair on Office 2010 but that option long ago disappeared from the Program install /uninstall page. And of course Office 2010 install disk can not be found for a clean re-install.

I am a contractor and trying to get work for my client done -- can I bill MS for these issues after all it's their **** that causes this!!

Among other problems with my Win7 are that other Win7 updates normally do not complete, and BSOD is now a pretty regular occurrence at least every week. What total f-ing **** this system is now. Not sure how to recover -- I ve got so much software installed that a rebuild would take weeks. Soemwhere I've got a complete system backup from about amonth ago so I guess I could always go there, but it won't fix most of these problems which pre-date that image.

Am creating a system restore point right now (if it lets me) so at least I can recover to this point should it come to this again.

Oh this is great: "The restore point could not be created for the following reason:  The writer experienced a non-transient error.  If the backup process is retired, the error is likely to reoccur.  (0x800423F4)  Please try again."

Now that is even better than the IBM garbage lingo from the 80's !!  Besides if you actually parse it, doesn't make any sense.  As it predicts trying again doesn't work!!

stopping and starting SQL server VSS service didn't work either!

Problem with registry writer - could that be the problem? see below....

C:\Windows>vssadmin list writers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'Task Scheduler Writer'

Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

State: [1] Stable

Last error: No error

Writer name: 'VSS Metadata Store Writer'

Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

State: [1] Stable

Last error: No error

Writer name: 'Performance Counters Writer'

Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

State: [1] Stable

Last error: No error

Writer name: 'ASR Writer'

Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Instance Id: {d31c228c-b238-4857-9984-27529a06b50b}

State: [1] Stable

Last error: No error

Writer name: 'System Writer'

Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

Writer Instance Id: {258ac8c5-8d3e-4dbf-9ac7-04b29774b755}

State: [5] Waiting for completion

Last error: No error

Writer name: 'SqlServerWriter'

Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

Writer Instance Id: {558635b0-b98a-4461-bebc-1a969c9856f9}

State: [1] Stable

Last error: No error

Writer name: 'IIS Metabase Writer'

Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

Writer Instance Id: {3492d339-a1ca-4766-8b2d-f4f3f30a4263}

State: [1] Stable

Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

Writer Instance Id: {88fbb43d-788a-4213-84c2-7e7fa877e3bd}

State: [5] Waiting for completion

Last error: No error

Writer name: 'Registry Writer'

Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

Writer Instance Id: {88d21322-3f3c-49c0-b5f0-984c3f29e99b}

State: [9] Failed

Last error: Non-retryable error

Writer name: 'MSSearch Service Writer'

Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}

Writer Instance Id: {9e9f0351-fe97-4164-8c22-3ff5e67c276b}

State: [5] Waiting for completion

Last error: No error

Writer name: 'COM+ REGDB Writer'

Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

Writer Instance Id: {81808d55-5927-405c-95ae-94c8bb3193c2}

State: [5] Waiting for completion

Last error: No error

Writer name: 'WMI Writer'

Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

Writer Instance Id: {6ab4917c-0f82-4d05-94fb-77ae6db3cd6f}

State: [5] Waiting for completion

Last error: No error