This issue has been corrected with an update described in the link above, and has been delivered as an automatic update via Microsoft Update. If you are still experiencing this issue, please re-run Microsoft Update, check for updates, and ensure you are on the latest versions of each package.
Shortly after publishing the September Public Update, we received notifications of a potential issue with Outlook 2013 after installing the non-security update KB2817630. Based on those reports we immediately removed the patch from Microsoft Update - within 3 hours of its release. If you haven’t already downloaded or installed the patch, you will not have these problems or be offered the problematic patch.
In contrast to what has been reported, MS13-068 is not the cause nor is it affected by this issue.
This blog post will describe the problem and explain how to fix it. It also reminds users what to do if a Patch Tuesday update causes issues.
We are very careful with Public Updates given their wide and rapid proliferation. We regret any inconvenience caused by this update, and we are hopeful that this information can help you restore productivity in Outlook products.
Due to a version incompatibility between outlook.exe and mso.dll, a mismatched reference to a data structure causes the “Minimize” button in the navigationpane to render incorrectly, typically extremely large to the point that the navigation pane is "invisible" to the user. The issue only manifests when incompatible versions of outlook.exe and mso.dll exist on the system.
If both versions are earlier (lower) than 4535.1000, or both versions are later (higher) than 4535.1000, the problem does not manifest. If one file is updated but the other is not, the problem is evident. The incompatible state is created by installing either the September Public Update OR the August Cumulative update, but not both. Users of MSI-based products that have automatic updates enabled are those that are most likely to have encountered the issue.
Office 2013 Click-to-Run products are not affected.
Said differently, only MSI installations of Office or Outlook 2013 are affected. These are volume-license installations typically found in businesses thatpurchase licenses in volume.
Each version of Office installed, such as viewers, standalone client products, Office suites with MSI-based installations, etc., will receive the update. We haveseen reports of some users needing to remove the update 2 or 3 times. This is because the system has product ID’s for multiple installations of MSI-basedOffice products.
Two updates can get a user into this state. Installing the September Public Update delivers an updated version of mso.dll without updating outlook.exe, resulting in the incorrect user interface.
We are also working on re-publishing the September Public Update with the correct versions of both mso.dll and outlook.exe to ensure users with automatic updates enabled will receive the correct fix. We will update this blog with further information as our schedule develops.
When you encounter trouble with a Public Update, you can always contact us at http://support.microsoft.com. You can call Microsoft directly at 1-866-234-6020. Alternatively, please contact our community network at Microsoft Community or visit Microsoft Support for access to extensive online self-help resources.
I have 15.0.4517.1504 mso.dll
I have 15.0.4517.1509 outlook.exe
This puts me in the green OK box of the grid above, I believe.
But, I have the problem. Or, had the problem until I uninstalled KB2817630.
So the Grid does not accurately summarize the understanding of the problem in my case, imo.
Win 7 x64
Office Professional 2013 Plus 64-bit
Excel 2010 32-bit
(As an aside, I am surprised that I have 32-bit and 64-bit Office components on the same box; even though they are different versions.)
Hi Ted, this is very curious, KB2817630 lays down the 4535 version of MSO.DLL. I'm interested to know why that version didn't show up?
Sorry, the versions I mention in this comment are *after* removal of the KB2817630.
I guess the grid is versioning after KB2817630 is applied and before it is rmoved.
KB2817630 does upgrade the dll to the 4535 version. (Just reinstalled it to confirm)
The grid is correct for my case, imo.
Installing this hotfix from Microsoft fixed the issue for me.
Also seems to be an issue with KB2810009, keep getting the update offered, but fails to install. Win 8.1 (pro) with Office 2013 Pro (but with Access, InfoPath and Lync not installed). Error seems to indicate update not required so assume something going on with update detection. Code 80242009
Ian, we are investigating targeting errors in the PU for specific patches. As we identify the issues and offer a solution we'll update the blog to reflect this.
What about Windows Update error 0x80242009 when we try to install KB2810009?
I see KB2817630 listed 6 times: 2 for MS Office Pro Plus 2013, 2 for MS Visio & 2 for MS Project.
thanks, solved my problem. only had the regular updates enabled so had KB2817630 installed that i got rid of. now outlook works as before. (and as slow as it always was)
its a shame this update ever got published in the first place. but well.
If you knew in advance (and I infer from this article that you did) of the possibility (however small) of the presence of two critical, but possibly mismatched DLL’s on your customer’s computers, weren’t you obligated to have Windows Update “Patch Tuesday” check for that possibility and correct it as part of the patching process?
the Outlook update from august 2013 seems to add another issue:
When we print an email we now get an additional header with:
"Vertraulichkeit: männlich" (german for "confidentiality: male") on every printed document.
I uninstalled KB2817630 and my folder list appeared - BUT my favorites (which usually appear at the top of the folder list) are still gone. AND I can no longer mark any folder as a 'favorite' to show up at the top.
Please ignore my previous comment - I did not have the 'Mail' view on, but was in 'folder' view, which I had switched to in an attempt to see my missing folders!
@Wisdom, conceptually this is true and Microsoft Update detection will offer update *packages* that are compatible with a Service Pack baseline. In this case, we inadvertently created what we call a cross-packlet dependency, where files within the package were mismatched.
In other words, MU detection did not cause / could not have prevented the issue, because the conflict is within the packages, not the packages themselves.
We are continuing to investigate the multiple offerings issue and we expect to have an update on that situation today.
@Outlook August 2013 Update,
Please visit this blog: blogs.technet.com/.../gray_knowlton, use the "Email Blog Author" link and send me a mail, because I'd like to understand more about the issue you are reporting.