There are a few known bugs in Office 2013 that may trip you up. Here are a couple.
Microsoft’s list of known issues in Office 2013 marks bugs as applicable only to the Preview code, despite some still being present in the release version. Here are some of the more common ones:
- Outlook 2013 doesn’t show its Jump List when you right-click its taskbar icon. To fix this, unpin Outlook from the taskbar, close Outlook and delete the Registry key HKey_Current_User\Software\Microsoft\Office\15.0\Outlook\Setup. Open Outlook again and re-pin it. This bug is annoying as it can keep recurring even after you think you’ve fixed it.
- File | Share | Send As Attachment doesn’t work if you have Outlook 2013 installed alongside an earlier version. To get around this, close the earlier version or create a new message and use Insert | Attach File instead. This bug applies only if you use the Office 365 Click-To-Run installer for Office 2013. Using the standard MSI installer will force you to remove any earlier version of Outlook.
Microsoft lists several workarounds for these bugs that boil down to variations of that tired old joke, “Doctor, Doctor, it hurts when I do this”... “well don’t do that, then”.
For instance, Microsoft’s advice on the problem “Error when connecting to Exchange 2003” is “Workaround: Outlook 2013 isn’t supported on Exchange 2003 and connectivity is blocked. Please connect Outlook 2013 to Exchange 2007, 2010 or 2013”.
This isn’t much use unless you’re a system administrator with the money, time and authorisation to upgrade your company’s Exchange server. I’d be more impressed if the company was honest enough to say “that’s just the way we designed it”.
Exchange 2003 is ten years old, long out of mainstream support and, as with previous versions, Microsoft is using the release of a new version of Office to push people into updating its other ageing systems as well.
If this comes as a surprise, you’ll be shocked to learn that Office 2013 won’t run on Windows XP or Vista, either. Here is a list of "Office 2013 Known Issues", or rather the ones that Microsoft is confessing to (with their hilarious workarounds), can be found here.