The Office 12.1.1 update is now up on MacTopia. The 12.1.1 update is not yet available through auto-update. MacBU seems to have set a pattern of releasing via direct download only prior to releasing via AutoUpdate. In the past this has resulted in some changes to make the updater more reliable. It's too early to say yet if this update will be problematic.
If you are concerned about updating, archive (zip) your Office for Mac folder prior to updating. If the update proves problematic for you, simply revert to the archived version.
The Office 2008 for Mac 12.1.1 Update is focused on improvements in Word, Excel and PowerPoint. The double-click issue is part of the fix.
Word documents open correctly when you double-click the document or when you download the document from a Web site.
Improvements for Entourage users:
- Stability is improved.
This update fixes an issue that causes Office 2008 applications to quit unexpectedly when you open or use Office 2008 applications. - Stability is improved when you wake the computer from sleep.
This update fixes an issue that causes Entourage 2008 to quit unexpectedly when you wake the computer from sleep, such as when you close and then open the lid of a laptop. - The update installer now ignores backup copies of Office that were created by Time Machine.
For users of Mac OS X 10.5 (Leopard), this update fixes an issue that causes the update installer to identify copies of Office in backup folders that were created by Time Machine. Folders that were created by Time Machine use the folder name extension ".backupdb."
If you are having problems updating, see this Check List to troubleshoot your install
Comments (13)
Hi,
Trying to install the update 12.1.1 on a machine running 10.5.3 and Office 12.1.0 and in the Destination Select process I get the message:
"You cannot install Office on this volume. A version of the software required to install this update was not found on this volume."
Office is in the default location (i.e. within the Applications folder at the root level - not in a User folder) and the folder name has not been changed.
Also the user id used for the update is an admin user.
Any thoughts?
See this article: 12.1.1 updater woes- a version of the software required not found
Thanks for the link.
I must say though its a bit tiresome to go back to scratch everytime.
What happens when we get to SP 2 or 3 will we still need to trash everything, start over and them apply every outstanding patch????
Perhaps I’ve been using a Mac for too long but i just want to apply “a” patch and move on not devote half a day to what should be a simple exercise that most other developers seem to have mastered.
I agree it is tiresome. I feel like a broken record. Do you know if you made any modifications to cause this?
None at all that I know of (apart from perhaps installing Messenger 7).
I note that in the link a “successful” upgrade has Messenger 6.0.3.
You caught me on this. It was successful for the Office applications, but not for Messenger. It's not really a part of the upgrades so can I use this as an excuse?
I'm experiencing the same issue, and had the same reaction (wow, what happens when SP2 comes out?). I have a clean install then update only 1 day old (brand new laptop). I'm not even sure how I could have modified any files in that short of a time - I've only installed Firefox after Office 2008.
Is there not a way (command-line option maybe?) to bypass version checking?
You can set AutoUpdate to Manual check, but even on Automatic, it does not install. It just alerts you to the updates. Updates are really important as they fix a lot of problems in the early versions.
When you have an early version, try zipping it and see if that helps for the next upgrade.
I can guarantee I'm as frustrated by all the problems as everyone else. I do know the developers are working hard to fix these issues.
Anyone know if the fix for the Exchange certificate error was in 12.1.1?
The fix was not included. Sorry.
Well I finally did the uninstall / re install and it at least let me install the update. :)
Having got through that I thought I'd look into another "challenge" - namely AutoUpdate (sorry if this is too far OT - if it is can you respond "off line" rather than posting it?).
I've never got this to work "automatically". Perhaps I have my definitions wrong but I was expecting something like the Apple Software Update mechanism (i.e. it actually launches and displays when an update becomes available - if you set it up that way).
Now with the Office product, if I set it to check "automatically" every week nothing is displayed unless I launch it and then manually click on the "Check for Updates" button??!!
The machine concerned is always on and is connected to an always connected cable broadband connection.
Am I missing something? Do I need to have it run in the background as an Account Login Item? Or is my definition / understanding of "automatically" fundamentally different to Microsoft's?
I've looked in the Help and all it says is that it can be configured to run automatically but not how to achieve this.
First, I'm glad you are now updated. As to the AutoUpdate... Are you sure AutoUpdate is actually updated? The original has to be updated in order for it to see the new updates. This was a change from VISE installers to Apple package installers. Check the MAU to see if it's shows v 2.2.0
Yourstartupdrive/Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate v2.2.0
Microsoft AutoUpdate for Mac
If you are updated, it should be working as you describe. I would guess at a preference being corrupted or an OS file that AutoUpdate uses being corrupted.
1. Testing in a new User is generally the easiest test for a corrupt User preference, but since you are looking for an update this won't work. You could try moving all preferences out and add them back a few at a time to check. See steps here: Test for User preferences conflicts It's a very time consuming process.
2. Apply the latest Apple combo updater to overwrite system files that might be corrupted.
Yes its 2.2.0 (080409) as per the successful update listing.
I only every use the combo updates as opposed to the smaller "delta" updates and have done so on this particular machine for 10.5.2, 10.5.3 and 10.5.4.
The process I use is to:
Repair permissions.
Apply combo update.
Repair permissions again.
As you say mucking around with the 360 odd items in the User\Library\Preference folder isn't worth it.
I'll just chalk it up to another thing that Microsoft doesn't do properly.