Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I have the same problem of it not installing.

I use Macaroni to periodically remove localizations I don't need, so I guess that's the culprit.

I thought about removing Office and re-installing it to make it work, but dread that most likely I'm going to have to re-do that process again for the next update. So I decided not to update for now. I value Macaroni more than the Office update, I guess. :p
 
12.1.1 Update requires 12.1.0 to be installed

Greetings and Salutations

The 12.1.1 update does require the 12.1.0 update to be installed. This update is what we call an incremental update; therefore, prior updates are required.

As others have noted, if you make certain changes to Office (strip PPC or Intel part of universal binary; remove language files) the updater will not find Office. You will want to reinstall Office (or use a Time Machine version) to put those files back.

mwp98223 (post 38 or so) gave a link to a blog post that has the items I talked about from previous installs. That blog discusses the issues that will prevent the updater from finding/updating office, and how you can rectify them.

While reinstalling (the last step) will resolve the issue, it only masks the symptoms and you might find yourself in the same boat again. If you have tried the other steps and they don't apply to you, please post to this forum.

I am reading the forum and sending private emails to those who cannot install to work through issues to find out what is happening and get them up and running.

Please remember, there are changes to the "requirements" on where/how the Office application can live now - many of the "requirements" for Office updating and installing (don't move, don't rename, don't change files) are the same sort of updating/installing "requirements" that are on Adobe and Apple applications. So, while I do feel for those folks who hit installation issues due to these issues; there is not much i can do for them.

So far we have not found issues that are not outside of these, but I want to make sure of that; thus my working with folks that cannot install. To these folks (who either don't realize they have "broken the rules" or perhaps we find something else), I truly apologize you are having this agony. Hopefully, you'll take me up on this offer to help with install issues and we'll get you up and going.

Thanks for your time

David Pelton
Microsoft MacBU
 
Problems with install

I had the same problems others on this forum talked about. I went through this with the SP1 update and had to reinstall b/c of stripping PPC. However, since that time my office 2008 installation was unchanged and I still could not install this update.

I deleted Office 2008 again and tried reinstalling again and running AutoUpdate. AutoUpdate found SP1, downloaded it to 75%, then crashed and had to do the downloading all over again. I remained patient and let it run its course. It finished and I tried installing again. Installation of SP1 took literally 5 seconds (way too fast) and when I checked the version in Word it still said 12.0.0.

Long story short, I erased every single Microsoft and Office associated file on my Leopard partition and reinstalled. After all this, it worked. That my fellow MacRumors posters, is what my day has been like. In all honesty, I was just about to toss Office 2008 and use Office 2003 through VMWare. What a brutal upgrade path...:mad:

Love Pages but had some issues with export to Word. Hope Apple keeps pumping resources into their office suite...:apple:
 
Greetings and Salutations

The 12.1.1 update does require the 12.1.0 update to be installed. This update is what we call an incremental update; therefore, prior updates are required.

As others have noted, if you make certain changes to Office (strip PPC or Intel part of universal binary; remove language files) the updater will not find Office. You will want to reinstall Office (or use a Time Machine version) to put those files back.

mwp98223 (post 38 or so) gave a link to a blog post that has the items I talked about from previous installs. That blog discusses the issues that will prevent the updater from finding/updating office, and how you can rectify them.

While reinstalling (the last step) will resolve the issue, it only masks the symptoms and you might find yourself in the same boat again. If you have tried the other steps and they don't apply to you, please post to this forum.

I am reading the forum and sending private emails to those who cannot install to work through issues to find out what is happening and get them up and running.

Please remember, there are changes to the "requirements" on where/how the Office application can live now - many of the "requirements" for Office updating and installing (don't move, don't rename, don't change files) are the same sort of updating/installing "requirements" that are on Adobe and Apple applications. So, while I do feel for those folks who hit installation issues due to these issues; there is not much i can do for them.

So far we have not found issues that are not outside of these, but I want to make sure of that; thus my working with folks that cannot install. To these folks (who either don't realize they have "broken the rules" or perhaps we find something else), I truly apologize you are having this agony. Hopefully, you'll take me up on this offer to help with install issues and we'll get you up and going.

Thanks for your time

David Pelton
Microsoft MacBU

I noticed these offers around the SP1 update as well. Great work, David! The install worked fine for me, but such personal support by the Mac BU through forums is an example for others.
 
Greetings and Salutations

The 12.1.1 update does require the 12.1.0 update to be installed. This update is what we call an incremental update; therefore, prior updates are required.

As others have noted, if you make certain changes to Office (strip PPC or Intel part of universal binary; remove language files) the updater will not find Office. You will want to reinstall Office (or use a Time Machine version) to put those files back.

mwp98223 (post 38 or so) gave a link to a blog post that has the items I talked about from previous installs. That blog discusses the issues that will prevent the updater from finding/updating office, and how you can rectify them.

While reinstalling (the last step) will resolve the issue, it only masks the symptoms and you might find yourself in the same boat again. If you have tried the other steps and they don't apply to you, please post to this forum.

I am reading the forum and sending private emails to those who cannot install to work through issues to find out what is happening and get them up and running.

Please remember, there are changes to the "requirements" on where/how the Office application can live now - many of the "requirements" for Office updating and installing (don't move, don't rename, don't change files) are the same sort of updating/installing "requirements" that are on Adobe and Apple applications. So, while I do feel for those folks who hit installation issues due to these issues; there is not much i can do for them.

So far we have not found issues that are not outside of these, but I want to make sure of that; thus my working with folks that cannot install. To these folks (who either don't realize they have "broken the rules" or perhaps we find something else), I truly apologize you are having this agony. Hopefully, you'll take me up on this offer to help with install issues and we'll get you up and going.

Thanks for your time

David Pelton
Microsoft MacBU

Thanks very much for your post.

I am not able to update because I strip localizations to save drive space.

This is the first time in many years that I've been using a Mac that stripping localizations has caused the installer to not be able to update. I hardly consider this to be "breaking the rules," and think Microsoft should fix this problem. ASAP.

I can reinstall Office for it to take the update, but like you said above, the problem may very well come up again for the next update. Not stripping localizations is not an option.

Thanks, and I really hope Microsoft works this out.
 
It's appreciated to have David Pelton's input from MacBU, but once more Microsoft show their total lack of flexibility and their need to apply bloated software and mindless rules. What is "breaking the rules" about removing localisations that will never be used?

From starting to read discussions that 12.1.1 is a positive update, it now leaves me, like many others, facing having to totally reinstall Office 2008. Can someone remind me why I continue to buy Microsoft products? iWork and/or OpenOffice are looking attractive options if Microsoft cannot show the understanding to quickly address this issue.
 
Time to launch Word (cold start) with 12.1.0 = 30 seconds
Time to launch Word (cold start) with 12.1.1 = 24 seconds

(MBP 2.2Ghz C2D, WYSIWYG font menu disabled, Gallery at startup disabled, all Normal.dot templates on system deleted to try and reset them)

How long till it takes < 10 seconds like on Windows?
 
Greetings and Salutations

The 12.1.1 update does require the 12.1.0 update to be installed. This update is what we call an incremental update; therefore, prior updates are required.

As others have noted, if you make certain changes to Office (strip PPC or Intel part of universal binary; remove language files) the updater will not find Office. You will want to reinstall Office (or use a Time Machine version) to put those files back.

mwp98223 (post 38 or so) gave a link to a blog post that has the items I talked about from previous installs. That blog discusses the issues that will prevent the updater from finding/updating office, and how you can rectify them.

While reinstalling (the last step) will resolve the issue, it only masks the symptoms and you might find yourself in the same boat again. If you have tried the other steps and they don't apply to you, please post to this forum.

I am reading the forum and sending private emails to those who cannot install to work through issues to find out what is happening and get them up and running.

Please remember, there are changes to the "requirements" on where/how the Office application can live now - many of the "requirements" for Office updating and installing (don't move, don't rename, don't change files) are the same sort of updating/installing "requirements" that are on Adobe and Apple applications. So, while I do feel for those folks who hit installation issues due to these issues; there is not much i can do for them.

So far we have not found issues that are not outside of these, but I want to make sure of that; thus my working with folks that cannot install. To these folks (who either don't realize they have "broken the rules" or perhaps we find something else), I truly apologize you are having this agony. Hopefully, you'll take me up on this offer to help with install issues and we'll get you up and going.

Thanks for your time

David Pelton
Microsoft MacBU

David, Thanks for the feedback, but I have to agree with other posts here that deleting localizations shouldn't be something that prevents the update. Drive space is valuable, and I don't want it filled up with language files I'll never use. Microsoft should fix this ASAP. This is never a problem for any other software.
 
It's appreciated to have David Pelton's input from MacBU, but once more Microsoft show their total lack of flexibility and their need to apply bloated software and mindless rules. What is "breaking the rules" about removing localisations that will never be used?

From starting to read discussions that 12.1.1 is a positive update, it now leaves me, like many others, facing having to totally reinstall Office 2008. Can someone remind me why I continue to buy Microsoft products? iWork and/or OpenOffice are looking attractive options if Microsoft cannot show the understanding to quickly address this issue.

Easy. In a Windows world, this protocol is simply accepted as 'the norm.' Multiple installations for any application are a given, and excess is always considered best. Imagine an updated Swiss Army Knife complete with a dental flosser, nose hair trimmer, sunscreen applicator, apple corer, carrot peeler, coffee strainer, tea ball, poultry thermometer, egg whisker, egg slicer, sugar sifter, gravy baster, lobster fork, oyster shucker, shrimp deveiner, caviar spoon, and localizations for all languages. Remove any feature(s), and the knife may no longer retain the ability to function as a knife, and may also become dysfunctional whenever updates are introduced.
 
If Mac OS ever wants to make it in the business world, MS would need to make Mac Office look and act identical to Windows Office. Look, feel, functions, file sharing, everything. We business folks don't want to have to learn what amounts to two different applications. I still use Windows for two things...MS Office and Quicken. Otherwise, I would dump Windows forever. Which is why I am guessing Mac Office will never look and function exactly like Windows Office.

P.S. I would be willing to learn a new Quicken interface if I could easily convert my existing Windows Quicken files to Mac Quicken.
 
Took me about 10 minutes all in to download and install, went smoothly. I haven't deleted any files or modified anything so that's probably why.

I would like to ask David at MacBU a question since he is a member on here, Are the Mac BU team aware of the slow opening times in office 2008 because of the WYSIWIG and Font Optimizing and do they plan to fix it? I know times have improved slightly by installing SP1 and now 12.1.1 but it still isn't within good comparison to Office 2007. Any company that takes feedback on board and actually works on it has to be commended but I have yet to see this issue being completely fixed/improved after numerous reports from a wide range of Office 2008 customers on here reporting the same issue over and over- opening times of the applications. I would be grateful for a response.
 
Installed fine with students version on my MacBook, on my MacBook Pro it failed due to removing localisations and PPC.

I would like an option to make it look like the Windows version, I know of a few companies who will not buy Macs due to the new learning curve of Office for Mac (yet they didn't really complain when the new interface for 2007 was introduced). Ribbon interface on Windows I like much better than the fiddly Toolbox in 2008.

Just give us an option for ribbons, please!
 
Installed fine with students version on my MacBook, on my MacBook Pro it failed due to removing localisations and PPC.

I would like an option to make it look like the Windows version, I know of a few companies who will not buy Macs due to the new learning curve of Office for Mac (yet they didn't really complain when the new interface for 2007 was introduced). Ribbon interface on Windows I like much better than the fiddly Toolbox in 2008.

Just give us an option for ribbons, please!

MS to give business users incentive to use Office on a platform other than Windows? Not likely gonna happen anytime soon.
 
I have Messenger 7 installed, could that be the reason I am unable to install 12.1.1?
 
Didn't fix all day events not showing in "My Day."

I know it's just a maintenance release, but couldn't "My Day" include all day events?
 
12.1.1 Update woes

My update would not work until I replaced the package "Office/Microsoft Office Setup Assistant" in "Applications/Microsoft Office 2008" using Time Machine. I have been using Macaroni to remove localized files (languages) and that was the file that had been modified.

Somewhere within the Office 2008 12.1.1 Update package is an item named 'updatables' which shows that multi-language versions of Microsoft Office Setup Assistant are sought, in particular the Plugins/SLT.bundle inside it. This bundle was introduced in the SP1 Update (12.1.0) and is not found in the original MSO2008 install.

Opening up the Office 2008 SP1 Update (12.1.0) package, and looking inside Packages for Office2008_en_core_12.1.0.combo.pkg, I opened this one up with Pacifist to look for the Microsoft Office Setup Assistant updater/installer. Inside, we find the SLT.bundle in its multi-language state. When this is extracted with Pacifist onto the hard-drive somewhere (desktop will do), it can then replace the one embedded in your existing Office 2008 SP1 installation. (Like many, I had also removed all language localizations and, in so doing, changed the SLT.bundle inside Microsoft Office Setup Assistant)

After doing the above, and after a couple of goes (no Safe-boot or permissions-fixing required), the Office 2008 12.1.1 Update went fine, and the 12.1.1 apps work.
 
12.1.1 Update woes

(For PPC/Intel slimmed/stripped MSO2008 SP1 installations, I've no idea if the above would still work)
 
Somewhere within the Office 2008 12.1.1 Update package is an item named 'updatables' which shows that multi-language versions of Microsoft Office Setup Assistant are sought, in particular the Plugins/SLT.bundle inside it. This bundle was introduced in the SP1 Update (12.1.0) and is not found in the original MSO2008 install.

Opening up the Office 2008 SP1 Update (12.1.0) package, and looking inside Packages for Office2008_en_core_12.1.0.combo.pkg, I opened this one up with Pacifist to look for the Microsoft Office Setup Assistant updater/installer. Inside, we find the SLT.bundle in its multi-language state. When this is extracted with Pacifist onto the hard-drive somewhere (desktop will do), it can then replace the one embedded in your existing Office 2008 SP1 installation. (Like many, I had also removed all language localizations and, in so doing, changed the SLT.bundle inside Microsoft Office Setup Assistant)

After doing the above, and after a couple of goes (no Safe-boot or logging-out required), the Office 2008 12.1.1 Update went fine, and the 12.1.1 apps work.

Thanks so much. It worked flawlessly. I'm going to copy the Microsoft Office Setup Assistant to use for the next update because I'm not willing to give up stripping localizations.
 
Office 2008 12.1.1 Update (got it to work)

Somewhere within the Office 2008 12.1.1 Update package is an item named 'updatables' which shows that multi-language versions of Microsoft Office Setup Assistant are sought, in particular the Plugins/SLT.bundle inside it. This bundle was introduced in the SP1 Update (12.1.0) and is not found in the original MSO2008 install.

Opening up the Office 2008 SP1 Update (12.1.0) package, and looking inside Packages for Office2008_en_core_12.1.0.combo.pkg, I opened this one up with Pacifist to look for the Microsoft Office Setup Assistant updater/installer. Inside, we find the SLT.bundle in its multi-language state. When this is extracted with Pacifist onto the hard-drive somewhere (desktop will do), it can then replace the one embedded in your existing Office 2008 SP1 installation. (Like many, I had also removed all language localizations and, in so doing, changed the SLT.bundle inside Microsoft Office Setup Assistant)

After doing the above, and after a couple of goes (no Safe-boot or logging-out required), the Office 2008 12.1.1 Update went fine, and the 12.1.1 apps work.

Thanks so much. It worked flawlessly. I'm going to copy the Microsoft Office Setup Assistant to use for the next update because I'm not willing to give up stripping localizations.
 
Cannot open office after update!

I just installed the 12.1.1. update and the update itself said everything worked out fine.

Now, when I try open any office application, the Office setup assistant pops up, asks if I want to join their user feedback program. Regardless of what I answer, the setup assistant continues to next page, which ask me to either registrate (again!) or get further info.

Going to the registration page doesn't help, because the site can't find the next page after putting in all the details. Tried several times.

Completing the setup assistant opens the Office Update, which then searches, and concludes that there are no further updates. It then quits - back to square one, no office program will open.

Thanks to M$ for stealing half of my working day.

- I'm running Danish language version of Mac Office 2008 Home edition on Macbook with Leopard. Have tried rebooting several times. Don't have time machine running.

Any ideas?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.