Yet again, Microsoft has released buggy patches for Office and Outlook. We have details of the faulty patches and the bugs they’ve added to Outlook.
This time it’s Outlook users who have the hassle and time-wasting dealing with Microsoft’s bungling.
All these security updates cause bugs in Outlook, various versions. Of course, Microsoft won’t admit to mistakes or bugs, only ‘known issues’.
- Security update for Outlook 2016: June 13, 2017
- Security update for Outlook 2013: June 13, 2017
- Security update for Outlook 2010: June 13, 2017
- Security update for Outlook 2007: June 13, 2017
- Security update for Windows 10, June 13, 2017
- Security update for Windows 10, June 13, 2017
- Security update for Windows 8, June 13, 2017
- Security update for Windows 7, June 13, 2017
- Security update for Windows 7, June 13, 2017
Microsoft’s advice only applies to Office 365 customers, anyone with perpetual licence Office gets no help.
Office 365 users can go to File | Account and Check for Updates to get the fixes.
That fixes this month’s problems but doesn’t help with these ongoing troubles with updates.
We’ve seen patches being withdrawn due to bugs (which customers have to do manually). Or more patches released to fix earlier faulty patches!
Microsoft is making a lot of money from Office, but are short-changing customers with poorly developed and badly tested patches.
Redmond’s continued trust in their own infallibility combined with aggressive automatic updates hurts their loyal customers.
Seven Outlook bugs added by Microsoft
Here’s a short list of the seven bug (sorry, ‘issues’) caused by Microsoft in the June 2017 updates. If you’re affected by one of these go to Microsoft Support for details on the current fix status.
Issue #1: Error when opening an attachment in an email, contact, or task formatted as Rich Text
Outlook 2007 and Outlook 2010.
Issue #2: Opening Mail Attachment warning when opening an attachment that includes consecutive periods (…) or exclamation point (!)
Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016.
Issue #3: Error when setting ShowLevel1Attach to allow Outlook to display Level 1 attachments
Outlook 2013 and Outlook 2016.
Issue #4: VBScript does not run or you receive malicious code warning when using a custom form for Outlook
Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016.
Issue #5: “Something went wrong…” or “Search results may be incomplete” error when searching in Outlook [FIXED]
all Outlook versions on Windows 7, Windows 8, Windows 10.
Issue #6: iCloud fails to load properly in Outlook
Outlook 2007, Outlook 2010, Outlook 2013 and Outlook 2016.
Issue #7: When printing a specific iframe or frame in a web page, the print output may be blank, or text is printed with a 404 [FIXED]
all Outlook versions on Windows 7, Windows 8, Windows 10.
