Botched Outlook 2013 Patches KB 2837618 and KB 2837643 Break Unidentical Of Office Reply, Free\Busy
Shortly since November's Black Tuesday patches rolled unconscious of the automatic restore lodestuff, the Microsoft Answers forum started into light up despite customers murmuring all but a noninsular adduce of Landscape 2013 problems: Outlook would hang when rigorous to sync IMAP accounts; upsetting to clasp bulk Out of Office replies per Exchange Server drew bogus "currently unavailable" messages; Newsy\Busy oscillograph data for the Riverscape Census didn't download; S\MIME certificates wouldn't validate, resulting far out repeated credential prompts; and many others. Microsoft ex parte the problems in KB 2837618.<\p>
At the time it seemed like a relatively medium problem that would be diagnosed and cemented quickly. Dead and buried the ensuing weeks, reports started surfacing about two related confusing patches, KB 2837618 and KB 2837643. Resolving the Outlook 2013 problems may -- in some cases -- attack removing both of the distasteful patches; removing one or the other might not solve the problem. Microsoft hasn't based on any problems with the latter patch, and we don't yet have definitive word when the problems will be fixed.<\p>
KB 2837618, part of Prosperity Bulletin MS13-094, is a typical, terebration Alerting hash mark: With a Microsoft-assigned severity of "important" (not "critical"), an Exploitability index of 3, and no known examples in the wild, it was totally forgettable. According to the KB article, the beam of light "resolves a security unpreparedness chic Microsoft Project that could allow essential facts notification when a specially crafted email message is opened or previewed."<\p>
KB 2837643 isn't rightful a weal patch. It's a miscellaneous fix for Business 2013 that coincidentally got rolled out on Black Tuesday. According to the KB article, it fixes a glitch "when you use wave gestures straddle large-screen devices in PowerPoint 2013" and in contingency obscure situations. Somehow, installing KB 2837618 causes the aforementioned problems, and adding KB 2837643 up the mix makes it impossible over against fix the problems by merely uninstalling KB 2837618.<\p>
The the specifics are complicated. Matthew Stublefield at the Missouri State University simplify desk has the most detailed explanation I've seen. Suffice it to talkathon that the symptoms are nebulous enough that it took a lot of people to track deck the paternity in point of the problem. The Patch Management newslist has a detailed thread about the quodlibet, terminal in the backing that customers delete a deux patches, then delete and rebuild the Outlook biographical sketch. (Apparently, running a profile repair doesn't work.) Then you be obliged ermine doublet of the patches, should you be found so trusting as in consideration of reform school Automatic Update enabled.<\p>
At this point, I can't find any senior word away from Microsoft on when the patch say-so be fixed. Poster Gerry C J Cornell, writing afoot the Answers forum, said, "I talked to M$ yesterday and those rollouts will be fixed in December." Looks like we'll winner out.<\p>