Microsoft pulls buggy Outlook 2013 update

Microsoft pulls buggy Outlook 2013 update

Summary: The update yesterday which caused many Outlook 2013 users to lose their folder pane has been pulled from Windows Update.

TOPICS: Microsoft, Software

Microsoft has pulled the update which caused problems for many users of Outlook 2013 from Windows Update.

The update description page ("Description of the Office 2013 update: September 10, 2013") does not mention the withdrawal of the update. The revision number for the document is still 1.0 and the links to the standalone installers for the update are still present. The files are still available for download.

Reports that a hotfix is available for this problem appear not to be accurate. The hotfix, described here, was released several weeks ago and addresses different problems.

Topics: Microsoft, Software

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • Good Deed

    i hope this fix it
  • And yet, mentioned hotfix (KB2817503)

    managed to fix the problem.
    While true that this hotfix dates back from the current problem, it is worthwhile installing.
    2nd Paradox
  • Outlook 2013

    THis one was super bad for us. Broke down dozens of laptops and desktops. Took out the FOLDER SECTION in Outlook 2013. Amazing to me that Microsoft now does not even test their OWN products before throwing a patch out there for us to download. Will now wait 30 to 60 days before applying any patches. This is the kind of stuff that can take them down very easily. Quality control lately at Microsoft went from outstanding to mediocre to pathetic. This one caused us hours of pain trying to reverse everything , restore, and remove the patches from the different environments. Unbelievable that Microsoft now does not test its OWN products. I would rather wait a month than be the first to install and break everything.
    • You're never to directly apply an update in an Enterprise...

      In IT, you should always deploy updates to test-computer (even virtual ones) first, so you would know whether or not the updates do more good than harm.

      Most IT personals rename "Patch Tuesday" to "Patch Thursday" or even "Patch Sunday".
      Because, again, you can never know how an update could affect and possibly bring your entire organization to a halt.

      One must go over the list of updates, then deploy them to a small number of test computers and only after you've noticed nothing critical has happened, and after a proper backup, you may deploy the updates. It's a Microsoft best-practice.

      But, they did screw up with this...
      2nd Paradox
      • Excellent practice

        The main interest of the Microsoft Patch Tuesday, is that its customers can also schedule their own tests in their environment before deployment on another Patch Day. They know thatthey have something new or schedule to do on Tuesday, but they can then organize the rest of their week without disturbance, and deploy patches when they want, in the same week or just once in a month.

        If Microsoft released patches on any day, the IT would have to dedicate time every day to check what's new (this could cost them as much as one hour, just to start configuring their test environment and perform backups, and to read the detailed possible issues and work-arounds) and stop processing their own scheduled works.

        Microsoft has even created server products to manage deployments of incoming patches, and assess physical or virtual hsots or software services in the local environment.

        If an organization has hundreds oreven just a dozen of hosts to manage, this deployment environement is a need because the IT personal will have limtied time and will want to automate these deployment without risking breaking ongoing works from hundreds or just dozens of workers, or clients or third-party providers. If something breaks, that person will be inondated by phone calls and support requests by mails and when replying to all of them in emergency, will no longer have time to find a workaround, test it, fix the problem, and deploy it rapidly.

        In all organizations there exists some time where deployment is less risky (it won't break ongoing works, or the clients and providers can safely wait for the next work day), as it can be performed, assessed, and eventually reverted with anough time and not in emergency. That's why IT support personals are working sometimes on Friday evening or in some dedicated weekends, or during some nights (for online servers). They have time to test and report their results, write some docs for other basic maintenance workers when they take a rest after their work out of peak hours(nad mot of the time the rest of the organization, when it has a problem an a single host, can work on another one that is not impacted by the same problem, or find help together to solve some problems without requiring immediately specific IT skills (they'll send their problem reports, but these problems can be scheduled and partly solved even if some limited time is lost for some operations).

        E.g. if an application form does not allow entering some value, may be another one can be entered and noted somewhere else for later correction. Same thing if a report is missing some expected data (it may be estimated if the missing data is not too massive and does not cause too many third parties to complain about some limited delays in their delivered services). But if they can no longer access to any data or all their mails are missing (because they are in folders missing), or they cannot act on them, all their work time may be lost just waiting for the resolution by the small IT support personal.
  • I set mine to Friday

    and it still updates the machines before then! GRRR
  • It looks like

    I'll be sticking with Office 2007 for a while.
  • how is this news?

    Another day, another Microsoft bug.

    You just can't make that stuff up.
    • I know

      Every other company puts out perfect patches, they never have to release a patch for a patch or anything. Nope, just Microsoft.
      Michael Alan Goff
  • Please see my post on the original article how KB2817503 causes a new issue

    Please see my original post that shows how the supposed hotfix for the bad update also causes a new problem... just don't install them, uninstall and just leave them out.