• Another hurried fix for an Outlook 2013 bug apparently caused by the November security patch

    Home » Forums » Newsletter and Homepage topics » Another hurried fix for an Outlook 2013 bug apparently caused by the November security patch

    Author
    Topic
    #241676

    Another stinker for the pile. Microsoft just released this little gem: KB 4011029 December 20, 2018, update for Outlook 2013. According to the KB arti
    [See the full post at: Another hurried fix for an Outlook 2013 bug apparently caused by the November security patch]

    2 users thanked author for this post.
    Viewing 5 reply threads
    Author
    Replies
    • #241698

      Are there any known issues reported with this Out-Of-Band update

      • #241723

        I haven’t seen any, but the day is yet young….

    • #241715

      From the notice, it appears there are not only the three bugs in perpetual Outlook 2010, 2013, and 2016 but also bugs in four recent subscription releases of Office 365.

      As KB4011029 only fixes the bug in perpetual Outlook 2013, I’m guessing MS will patch the other six soon.

      1 user thanked author for this post.
    • #241729

      I’m thinking that the people at Microsoft couldn’t even patch my bicycle tube properly, such a sorry state of affairs.

    • #241782

      Not seeing it in WSUS today. I do a sync once a day at around 1AM.

      Red Ruffnsore

    • #241871

      Outlook 2010, Win 7 Pro SP1.  KB4461529 installed successfully 09/12/2018 (that’s 9 December!).

      Not seeing this problem.  Just now went backstage and clicked Info | Manage Rules & Alerts.  Worked just fine.

      Don’t know if it’s related, but while backstage I clicked Print.  It opened the Print pane and then froze.  Unfroze after a minute, but after a couple more clicks in this pane it froze again.  Have restarted Outlook a few times with no change to the freezing.  Have yet to do a system reboot – maybe that’s all it needs.  Interested to hear if it’s just my machine.

      Dell Precision 3630 w/32 GB RAM, 500 GB (C:), 1 TB (D:)
      Window 10 Pro x64
      Internet: FTTC (Fibre to the Kerb)

    • #242560

      This also covers the problems report with Outlook 2016:
      Symptoms: You initially had a legacy Office 2013 installation, where this problem occurred. On others machines you may have Office 2016 or 365.
      May be you installed or upgraded to Outlook 2016 to try and fix.
      May be you are using roaming profiles.

      On the machines where this occurred. Uninstall Office 2016 or 365 – and reinstall Outlook 2013. Install the patch (for me this worked – after installing the patch, rebooting – and then uninstalling the patch). Start Outlook 2013 – then open rules. Close Outlook.

      Go to a machine with Outlook 2016 – where rules had also stopped working. Now start Outlook 2016 – and rules will open. I am using roaming user profiles.

      Uninstall Office 2013 – continue the upgrade to Office 365 (in my case it happened on a machine with a legacy install of Office 2013 waiting to become Office 365 – and a roaming user profile. Then it spread on from there).

    Viewing 5 reply threads
    Reply To: Another hurried fix for an Outlook 2013 bug apparently caused by the November security patch

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: