MacInTouch Amazon link...

Microsoft Office, security, and alternatives

Channels
Security, Troubleshooting, Products



On a good note, it appears that Microsoft has finally fixed a critical bug in Microsoft Auto Update that has been driving me crazy for over a year.

Ever since upgrading from Office 2011 to Office365 (and Office 2016), I've found that Auto Update would frequently hang on my macOS 10.11.6 (El Capitan) system. Launching it would result in a forever-bouncing icon. No amount of force-quitting or process killing would get it to launch. I would have to reboot (which would take a very long time, probably due to some process hanging and not actually terminating), and then Auto Update would work - at least for a short time, sometimes only long enough to update one app (e.g. Word or Excel or Auto Update itself) before hanging again, forcing yet another reboot.

This was incredibly frustrating, as you can imagine. And it only happened on the ElCap system. On my other Mac (running Sierra), there was no such problem.

Anyway, it appears that Microsoft finally fixed this problem. Since version 4.9.0 (March 14, 2019 release), it has been working as expected on my ElCap system. They don't say what changed other than "Bug fixes and update installation performance improvements", but they clearly fixed something that was broken for a very long time.
 


I can confirm that Office 2016 16.6.8 (Home & Business perpetual license) under macOS Sierra (10.12.6) would launch, allow me to click the Sign In button, allow me to enter the email address of my Microsoft ID, then get stuck "loading" and never ask for my password. Updating the computer to macOS Mojave (10.14.3) solved the problem. If I have to try this on a machine I intend to keep on Sierra, I'll report back if downgrading to a prior release of Office 2016 worked.
I ran afoul of this Sierra activation issue recently. Upgraded a client's Mac Pro 5,1 with an SSD to bring the performance of the computer back. Cloned everything over, and it did a wonderful job with everything, just what she was hoping for... until we tried to reactivate her perpetual license for Office 2019. Would not get past the sign-in process. Entered the email address for the account, and it just spun. Tried removing Office and reinstalling, removing along with using the license removal tool, no luck.

She spoke with Microsoft, and they were unable to get it through the activation process. They said they knew about the Sierra activation issue and that the current workaround was to upgrade the macOS, which resolves the issue, or wait until they get it working again.

She waited for a week or so, since she did not have a Metal-capable video card. She finally decided she didn't want to wait any longer. Tracked down a Metal-capable card and installed it along with Mojave. Office activation went through fine, and she was up and running. As you would expect, a few days later she gets this...
From: Microsoft Support <OFFIE.0000.WW.00.EN.CVG.BGL.TS.2ET.REC.SG.PI@css.one.microsoft.com>
Subject: SRXxxxxxxxxxxID - SRXxxxxxxxxxxID
Date:
April 16, 2019 at 9:53:50 PM EDT
To: <xxxxxxxxxxxxx>

Hi xxxxxxxx,

This is Joel Samuel from Microsoft Escalations.
This E-mail is in regards to the case number - xxxxxxxxxxxx.
I tried to reach you and left a Voice Mail.
You had been facing issues in activating the Office Suite on you MAC and the patch has been
fixed by the back end team and just wanted to confirm whether everything is working fine.
If yes, please reply to this E-mail.
If this is wrong, please call us at 1800-936-5700 or 866-425-4826.

Regards,
Joel Samuel
 


I'll have to try again. I bought my wife a 2017 MacBook Pro. It came with macOS 10.12 Sierra on it. I installed our Office 2016 home subscription and got the exact thing that you describe. It's been a week or so since the last time I tried. We also had an Office 2011 Home that I installed instead - it works fine.
 


Towards the end of last year I finally took the plunge, once Office 2019 was available, to purchase and upgraded from Office 2011.

For the most part this new Excel has been pretty stable, running on Sierra - things sort of work well enough to consider it a pretty decent and perky upgrade all in all. Primarily, I use Excel, so this is the focus here. My modified keyboard shortcuts were kept intact, which I was glad to see. The searching is a bit more tedious in comparison to how it worked in 2011, as is cut and paste, so an extra mouse click here and extra copy there tend to slow things down a bit from how I was able to do them before. But most things run significantly faster, so otherwise a pretty good trade-off.

There was one persistent issue/bug with the new Excel I kept experiencing that I was finally able to find a workaround for, as no fix for it had been put in place each time the software was updated. It's not unusual for me to have several rather large spreadsheets open at the same time. And to cut to the chase, it turns out that having AutoRecover enabled (every 10 minutes) would result in a few characters getting lost as I was typing along when AutoRecover kicked in. Presumably, it was saving off copies of each of the opened spreadsheets and, while doing so, ignoring the keyboard for a second or two. I'm pretty sure this type of thing didn't happen with Excel 2011. So, at this point, AutoRecover is turned off, and all is well, no lost characters, and it's been quite a while since I clicked in one cell and ended up in another, and perhaps a few other quirky things that no longer seem to happen.

The one other thing that I am glad to see has disappeared is that every so often in the old Excel a memory issue of some sort would occur and then I eventually would be unable to save the spreadsheet I had been editing. And most likely this is where some of the spreadsheet corruption I used to see originated from. No more of that that I've noticed with the new Excel.

So , thumbs up for me.
 


... Having AutoRecover enabled (every 10 minutes) would result in a few characters getting lost as I was typing along when AutoRecover kicked in. Presumably, it was saving off copies of each of the opened spreadsheets and, while doing so, ignoring the keyboard for a second or two. I'm pretty sure this type of thing didn't happen with Excel 2011.
I've noticed this, as well, starting in Excel 2016. It appears that they no longer buffer keystrokes while saving (or maybe whenever the UI is blocked on a long-running operation). Presumably this is to prevent a bunch of spurious keystrokes (possibly entered in frustration while the UI is blocked) from messing up the document.

Unfortunately, it gets in the way when you're not pounding keys in frustration, like when I will type Command-S to save while working and expect to be able to keep on typing - only now I have to wait for the save to finish, which is a lot more frustrating than the way it used to be - especially when saving to a remote/network volume, which can be slow even for small files.
 


Of course I can't find it now, but I heard a podcast interview with an author who uses LibreOffice to submit manuscripts to publishers.
I need to submit documents to a client in Microsoft Word format using the Times font. I have and use Word 2016, but it's not what I like. I downloaded NeoOffice 2017.17 Professional Edition and like it with one exception: I cannot get it to use the Times font. Using the Times font in LibreOffice works, but I find the onscreen view of LibreOffice annoying. Any suggestions on how to make NeoOffice 2017.17 use the Times fonts?
 


Microsoft AutoUpdate is reporting that a new version of Office (16.25) is available for download, but, as is the norm, the Release Notes and Update History web page linked to by AutoUpdate has not been updated yet to reflect the current release.

I notice, however, that there is a post announcing the update in Microsoft's Office Forum, and it links to a separate "What's New" page that has information about the 16.25 release.
 


I notice, however, that there is a post announcing the update in Microsoft's Office Forum, and it links to a separate "What's New" page that has information about the 16.25 release.
[I think new icons], incidentally, are annoying. They are more consistent with each other but harder to decipher at a glance. The periodic and apparently random ten-second freeze, a cross-platform feature, now works in Excel, too.
 


I have a complex spreadsheet that I created in Excel 2011. It contains a dozen or so tabs, several pivot tables, a number of graphs, many named cells and ranges (including calculated ranges), and macros.

I just purchased Office 365 Home and tried opening the spreadsheet in the latest version of Excel. I receive an alert stating "We found a problem with some content in 'Investments Analysis copy.xlsm'. Do you want us to try to recover as much as we can? If you trust the source of this workbook, click Yes."

If I click Yes, the spreadsheet opens, but lots of problems are instantly apparent. Graphs are missing, Formulas aren't working, because certain named ranges were lost. Column sizes are all off. I'm sure this is just the tip of the iceberg, since I haven't even attempted to execute any of my macros.

Is anyone aware of a reference to known breakage in spreadsheets converting to Office 365 and fixes or workarounds?
 


I have a complex spreadsheet that I created in Excel 2011. It contains ... many named cells and ranges (including calculated ranges)...
I just purchased Office 365 Home and tried opening the spreadsheet...
OK, after much sweat just to recreate a simple stacked column chart that was lost (*&^%$#$%), I discovered that none of the name ranges survived!...

Does anyone know of a way to print, export, copy, or otherwise capture all the named ranges, and their definitions, in Excel 2011?

... OK, In Excel help, I searched for Names and found this:
You can create a list of all the names that are assigned to cells in a workbook. Locate an area with two empty columns on the sheet (the list will contain two columns — one for the name and one for the cells referenced by the name). Select the cell that will be the upper-left corner of the list. On the Insert menu, point to Name, and then click Paste. In the Paste Name dialog box, click Paste List.
Who knew?
 


Does anyone know of a way to print, export, copy, or otherwise capture all the named ranges, and their definitions, in Excel 2011?
I do not deal with complex spreadsheets, but for file conversions in general I often end up using LibreOffice. It might be able to consume the Excel 2011 document and then spit it out in a format that Excel 365 can deal with.

For personal documents that I am not working on with others, I usually leave them in the LibreOffice default format (ODF, ODS, etc.) with confidence that they will continue to be readable long after LibreOffice has been replaced by whatever might come.
 


I do not deal with complex spreadsheets, but for file conversions in general I often end up using LibreOffice. It might be able to consume the Excel 2011 document and then spit it out in a format that Excel 365 can deal with.
First glance, at least many graphs and defined names made it. The pivot tables don't seem to have, however. I'll explore more. Great suggestion!
 


Another thing to try is to open the file through successively newer versions of Excel and/or in Excel for Windows. I know, in the past, I've had complex Word documents (with equations, tables, figures, etc.) that wouldn't render correctly in the most recent version of Word. However, opening, say, a Word 5.1a file in (for example - I don't remember the exact versions) Word X, saving; then opening in Word 2008, saving; then finally opening in Word 2016 resulted in a mostly correct document.
 




Speaking of the Office 2016 update... the Microsoft Auto Updater acts like it downloads and installs the update, but afterward I am left with the same version of Word as before. The other 3 Office apps did get updated from 16.16.10 to 16.16.11, but Word remains at 16.16.10.

Shutting down and restarting the Mac didn't help. Auto Updater tried again today, but with the same result. Anybody else have this issue? Am running High Sierra on a late 2014 Mac Mini. This has never happened to me before with Auto Updater.
 


Microsoft AutoUpdate checks if there is a new version of MS AutoUpdate - typically there is - downloads it, and installs. You have to run it a second time to check if there are updates to the Microsoft [Office] software.

(Only Microsoft could come up with such a lame interpretation of 'auto'.)
 



Microsoft AutoUpdate checks if there is a new version of MS AutoUpdate - typically there is - downloads it, and installs. You have to run it a second time to check if there are updates to the Microsoft [Office] software.
With the latest update (this week), AutoUpdate re-launched itself after it self-updated. But this seems to be the first time. Up until this past update, I always had to manually re-launch it.
 


If all else fails, you should be able to download the Word 2016 installer by itself and just use that. It's available from the Office 2016 release notes web page:
Yep, that's what I wound up doing. It succeeded in installing Word 16.16.11 but also installed something called Office365ServiceV2.app that opens every time I open Word. (I don't even have Office365.) I dragged it to the Trash. Word now opens as expected, without the other annoyance.
 



Speaking of the Office 2016 update... the Microsoft Auto Updater acts like it downloads and installs the update, but afterward I am left with the same version of Word as before. The other 3 Office apps did get updated from 16.16.10 to 16.16.11, but Word remains at 16.16.10.
You might check if you have a second copy of Word on your Mac. I saw this on a Mac that kept asking to update Office. One copy did get (repeatedly) updated to 16.16.11. However, the next time the auto updater ran, it again saw the 16.16.10 version and so asked to install the update. The updater would always "update" the same copy, even though it was already at 16.16.11, leaving the 16.16.10 copy untouched. I just removed the second copy and all was fine.
 




New Microsoft Office updates are out with security fixes (Word):
For the Windows 7, 8, and 10 users out there, Microsoft also just released updates for a "Critical" set of vulnerabilities in its Remote Desktop Services. Exploitation of these vulnerabilities does not require user action, so you should give strong consideration to patching or mitigating the vulnerabilities. Ars Technica has more information:
 



I've been having a problem with search in Outlook 2019 (Office 365). I get "No Results" for all searches. I've tried every fix from Microsoft and also from this site. I'm running the latest version of Mojave (10.14.6). Has anyone else experienced this problem?
 


I've been having a problem with search in Outlook 2019 (Office 365). I get "No Results" for all searches. I've tried every fix from Microsoft and also from this site. I'm running the latest version of Mojave (10.14.6). Has anyone else experienced this problem?
A client's Outlook 2019 had the same issue — searching for a person's email only went back to when I upgraded her Mac to Mojave and Office 2019 from 2016.

I used OnyX to delete the Spotlight index, restarted, and gave it time to rebuild everything before launching Outlook. Search worked after that.

Did you try this command?
Code:
mdimport "/Applications/Microsoft Outlook.app/Contents/Library/Spotlight/Microsoft Outlook Spotlight Importer.mdimporter" /Users/YOURUSERNAME/Library/Group\ Containers/UBF8T346G9.Office/Outlook/Outlook\ 15\ Profiles/Main\ Profile
 


A client's Outlook 2019 had the same issue — searching for a person's email only went back to when I upgraded her Mac to Mojave and Office 2019 from 2016.
I used OnyX to delete the Spotlight index, restarted, and gave it time to rebuild everything before launching Outlook. Search worked after that.

Did you try this command?
Code:
mdimport "/Applications/Microsoft Outlook.app/Contents/Library/Spotlight/Microsoft Outlook Spotlight Importer.mdimporter" /Users/YOURUSERNAME/Library/Group\ Containers/UBF8T346G9.Office/Outlook/Outlook\ 15\ Profiles/Main\ Profile
FYI Microsoft has a support article all about this problem:
It includes a link to the OutlookSearchRepair utility, along with details of the Terminal command you quote.
 


Thank you for the replies. Please see my comments below.
A client's Outlook 2019 had the same issue — searching for a person's email only went back to when I upgraded her Mac to Mojave and Office 2019 from 2016.
I used OnyX to delete the Spotlight index, restarted, and gave it time to rebuild everything before launching Outlook. Search worked after that.
I reindexed the main profile by adding and removing it from Spotlight Privacy in System Preferences. I assume this is equivalent to using OnyX.
Did you try this command?
Code:
mdimport "/Applications/Microsoft Outlook.app/Contents/Library/Spotlight/Microsoft Outlook Spotlight Importer.mdimporter" /Users/YOURUSERNAME/Library/Group\ Containers/UBF8T346G9.Office/Outlook/Outlook\ 15\ Profiles/Main\ Profile
I tried that command as well.
FYI Microsoft has a support article all about this problem:
It includes a link to the OutlookSearchRepair utility, along with details of the Terminal command you quote.
Unfortunately the utility doesn't work with Mojave.
Due to some changes in macOS Mojave, this tool no longer works in 10.14 and higher.
I followed the instructions provided for Mojave to no avail.

As I mentioned in my original post, I tried all of the suggestions on this page:

They include rebuilding the Spotlight index, rebuilding the Main Profile, removing and reinstalling Office, etc. I assumed that these would also apply to Outlook 2019, but who knows.
 


Thank you for the replies. Please see my comments below...
I had a similar problem with Apple Mail search not working on a client's computer. It was running Sierra on an HFS volume. I tried these to fix (none of them worked):
  • safe booted
  • deleted Spotlight index and waited for it to rebuild; I did this several times
  • ran Disk Utility First Aid, found no problems
  • called Apple Support — they had me reinstall the OS
  • still did not work
I decided to run DiskWarrior and rebuilt the directory — DiskWarrior did find a problem/s and fixed it/them.

Search worked after the DiskWarrior rebuild.

Maybe your drive directory has a similar issue.

Since I don't think DiskWarrior works on Mojave/APFS, if it has a similar problem, the only way that might fix it would be to clone to another drive, erase the internal drive and then clone back.
 


I've been having a problem with search in Outlook 2019 (Office 365). I get "No Results" for all searches. I've tried every fix from Microsoft and also from this site. I'm running the latest version of Mojave (10.14.6). Has anyone else experienced this problem?
One of my users (the director of my department, actually) is having the same exact problem. He got a new MacBook Air running Mojave, and another admin took it upon himself to migrate him to Outlook for Mac (for use with Office 365), and his search doesn't work right either.

I've tried the various fixes Microsoft has published regarding Spotlight reindexing, to no avail.

Hopefully Microsoft updates the OutlookSearchRepair utility to work with Mojave, but I kinda get the impression it's not a simple bug to fix.
 


One of my users (the director of my department, actually) is having the same exact problem. He got a new MacBook Air running Mojave, and another admin took it upon himself to migrate him to Outlook for Mac (for use with Office 365), and his search doesn't work right either. I've tried the various fixes Microsoft has published regarding Spotlight reindexing, to no avail. Hopefully Microsoft updates the OutlookSearchRepair utility to work with Mojave, but I kinda get the impression it's not a simple bug to fix.
Chris, I had the same search problem when I moved to a new Mac earlier this summer. The process in this article fixed my issues:

 



One of my users (the director of my department, actually) is having the same exact problem. He got a new MacBook Air running Mojave, and another admin took it upon himself to migrate him to Outlook for Mac (for use with Office 365), and his search doesn't work right either. I've tried the various fixes Microsoft has published regarding Spotlight reindexing, to no avail. Hopefully Microsoft updates the OutlookSearchRepair utility to work with Mojave, but I kinda get the impression it's not a simple bug to fix.
Ran into the same issue with five new MacBook Pros, all running macOS 10.14.x with APFS.

Migrated data from four older computers. Three of them had not been updated to macOS 10.4.4, so the OutlookSearchRepair tool actually worked for them. The fourth had no migration, so Outlook started from scratch, and searching worked fine right from the start.

The fifth MacBook Pro had been upgraded to macOS 10.14.5 and could not run the tool. We tried everything, as well, and nothing worked, short of removing the account and recreating it. Once we did that, and allowed all the mail to repopulate overnight, searching worked and, as far as I know, continues to work.
 


We tried everything, as well, and nothing worked, short of removing the account and recreating it. Once we did that, and allowed all the mail to repopulate overnight, searching worked and, as far as I know, continues to work.
I removed my account (by deleting the Main Profile folder), restarted Outlook, entered my account info and waited for all of my email to sync and be indexed by Spotlight. Unfortunately it had no effect.
 


I removed my account (by deleting the Main Profile folder), restarted Outlook, entered my account info and waited for all of my email to sync and be indexed by Spotlight. Unfortunately it had no effect.
Sorry it didn’t work for you, as well, but there is a slight difference in what we both did. Not saying it shouldn’t work the way you did it, but processes can be the difference, even when you would not expect them to be.

After going through all the other steps of clearing and resetting searching, we deleted the account in Outlook itself. There may be something Outlook does to the main profile folder when an account is removed and added through the program that helps this process.
 


There may be something Outlook does to the main profile folder when an account is removed and added through the program that helps this process.
Outlook's "main" profile (the first one you create) is special. Certain credentials are tied to it, and that account can't be deleted without first deleting all other accounts.

I had to go through this a few years ago when my company was acquired. We originally added the new company to our Outlook clients, which worked fine. When the old company's servers were decommissioned, Outlook got flaky (because there was no longer a server). We had to delete all our accounts and only then add the one for the new company.
 


Amazon disclaimer:
As an Amazon Associate I earn from qualifying purchases.

Latest posts