News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • Report of a buggy MSComCTL.ocx in January’s Office patches. Again.

    Posted on February 5th, 2019 at 17:42 admin Comment on the AskWoody Lounge

    Günter Born just posted details (German). Quoting blogger Sam:

    Microsoft once again issues a wrong file version of the MS Common Controls (MScomctl.ocx) for the Office January 2019 updates. It affects the following file:

    18.01.2019 22:33 1’410’216 MSCOMCTL.OCX

    This is particularly stupid for Office 2019 C2R, because there is only a new build. A manual uninstall of the relevant update is not possible.

    In the other versions of Office, I have found absolutely no clues at Microsoft, with which patch in December 2018 or Jan 2019 the wrong MS Common Controls file version is delivered. MS is totally silent here.

    Any of you getting bit by a bad MSComCTL.ocx?

    UPDATE: Looks like the bad, older version is in the February non-security patches, too. Details coming on Born City.

  • February 2019 non-Security Office Updates are available

    Posted on February 5th, 2019 at 12:44 PKCano Comment on the AskWoody Lounge

    The February 2019 non-Security Office updates have been released Tuesday, February 5, 2019. They are not included in the DEFCON4 approval for the January 2019 patches. Unless you have a specific need to install them, you should wait until Susan Bradley (Patch Lady) approves them and any problems have been reported.

    Office 2010

    Update for Microsoft Office 2010 (KB4462172)
    Update for Microsoft Office 2010 (KB4462187)
    Update for Microsoft Outlook 2010 (KB4462182)
    Update for Microsoft Visio 2010 (KB3115314)

    Office 2013

    Update for Microsoft Access 2013 (KB4032252)
    Update for Microsoft Office 2013 (KB4461550)
    Update for Microsoft Office 2013 (KB4461444)
    Update for Microsoft Outlook 2013 (KB4462141)
    Update for Microsoft Office 2013 (KB3172473)
    Update for Skype for Business 2015 (KB4462135)

    Office 2016

    Update for Microsoft Access 2016 (KB4032257)
    Update for Microsoft Office 2016 Language Interface Pack (KB4461534)
    Update for Skype for Business 2016 (KB4462114)
    Update for Microsoft Office 2016 (KB4461536)
    Update for Microsoft Outlook 2016 (KB4462147)
    Update for Microsoft PowerPoint 2016 (KB4461599)
    Update for Microsoft Project 2016 (KB4462134)
    Update for Microsoft Office 2016 (KB4022161)
    Update for Microsoft Word 2016 (KB4462145)

    There were no non-security listings for Office 2007 (which is out of support).
    Updates are for the .msi version (persistent). Office 365 and C2R are not included.
    Security updates for all supported versions of Microsoft Office are released on the second Tuesday of the month (Patch Tuesday).

  • Patch Watch: Green light for most patches; yellow for Win10 version 1809

    Posted on January 28th, 2019 at 03:23 woody Comment on the AskWoody Lounge

    Patch Lady Susan Bradley’s latest take on patching.

    Out this morning to all AskWoody Plus members, in AskWoody Plus Newsletter 16.3.0, now available FREE online..

  • Microsoft yanks buggy Office 2010 non-security patches

    Posted on January 5th, 2019 at 08:20 woody Comment on the AskWoody Lounge

    This just in from Günter Born...

    Microsoft has yanked all four of this month’s Office 2010 non-security patches. None of these are currently available in the Microsoft Update Catalog:

    Update for Microsoft Excel 2010 (KB4461627)
    Update for Microsoft Office 2010 (KB4032217)
    Update for Microsoft Office 2010 (KB4032225)
    Update for Microsoft Office 2010 (KB4461616)

    The KB articles are still out there, but they now say:

    After you install this update, you may experience difficulties in Microsoft Excel or other applications. To resolve this, uninstall the update by following the instructions in the “More information” section.

    This update is no longer available.

    There are instructions for manually uninstalling the patches.

    Japanese-language sites are all lit up with warnings about the patches clobbering Excel. Microsoft’s mealy-mouth “experience difficulties in Microsoft Excel” doesn’t say much, but the Japanese language posts certainly do. For example, @odsyeu on the iromame-beans.jp site says (translation by Google):

    After installation, program stop error now appears when opening the Excel file.

    You gotta wonder who tests this stuff.

    As Born says:

    This is the 3rd or 4th attempt from Microsoft to establish the Japanese calendar thing. In November 2018 Updates for Office 2010 were been pulled, and in December 2018 we also had Office 2010 updates for Japanese calendar.

    Whotta mess. But you’re OK because you haven’t installed any January patches yet, right?

  • January 2019 non-Security Office Updates have been posted

    Posted on January 3rd, 2019 at 06:13 PKCano Comment on the AskWoody Lounge

    The January 2019 non-Security Office updates were released Wednesday, January 2, 2019. They are not included in the DEFCON4 approval for the December 2018 patches. Unless you have a specific need to install them, you should wait until Susan Bradley (Patch Lady) approves them and any problems have been reported.

    Office 2010

    Update for Microsoft Excel 2010 (KB4461627)
    Update for Microsoft Office 2010 (KB4032217)
    Update for Microsoft Office 2010 (KB4032225)
    Update for Microsoft Office 2010 (KB4461616)

    Office 2013

    Update for Microsoft Project 2013 (KB4461560)
    Update for Skype for Business 2015 (KB4461557)

    Office 2016

    Update for Skype for Business 2016 (KB4461586)
    Update for Microsoft Excel 2016 (KB4461600)
    Update for Microsoft Office 2016 (KB3203480)
    Update for Microsoft Office 2016 (KB4032230)
    Update for Microsoft Office 2016 (KB4461435)
    Update for Microsoft Office 2016 (KB4461533)
    Update for Microsoft Project 2016 (KB4461587)
    Update for Microsoft Visio 2016 (KB4461531)

    There were no non-security listings for Office 2007 (which is out of support).
    Office 365 and C2R are not included.
    Security updates for all supported versions of Microsoft Office are released on the second Tuesday of the month (Patch Tuesday).

    UPDATE: As of January 4, 2019, the four January 2019 Updates for Office 2010 (msi version) have been pulled by Microsoft and are no longer available for download. If you have problems with the Office programs, Microsoft recommends uninstalling the updates.

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

    Posted on December 20th, 2018 at 19:15 woody Comment on the AskWoody Lounge

    Another stinker for the pile.

    Microsoft just released this little gem: KB 4011029 December 20, 2018, update for Outlook 2013. According to the KB article:

    This update fixes the following issue:

    Mail delivery rules stop working. When you try to open the Manage Rules & Alerts dialog box in Outlook 2013, you receive the following error message:

    The operation failed because of a registry or installation problem. Restart Outlook and try again. If the problem persists, reinstall.

    Here’s the weird part. On December 17, Microsoft posted this bug notice:

    Last Updated: December 17, 2018

    ISSUE

    When you click Rules > Manage Rules & Alerts…, the following error occurs:

    Manage Rules & Alerts

    Error:  “The operation failed because of a registry or installation problem. Restart Outlook and try again.  If the problem persists, reinstall.”

    The issue may occur after installing the following perpetual updates:

    Could someone explain to me why there are three acknowledged bugs, but only one of them was fixed?

  • Patch Lady – Office 365 prioritization

    Posted on December 9th, 2018 at 22:57 Susan Bradley Comment on the AskWoody Lounge

    Recently Office 365/Outlook on click to run has made a change in behavior… as noted on Office uservoice

    After the release of 16.0.6741.2017, the Click 2 Run (C2R) version of the Outlook client for the PC is prioritising O365 for Autodiscover queries above all other Autodiscover methods (SCP, HTTPS root domain etc).

    This causes problems for customers who aren’t using O365 for mail service, especially if either of these conditions are true:

    1. The user has a mailbox in the O365 service which is not being used. This can occur if the user has inadvertently had an Exchange license assigned.
    2. The user has a personal Office subscription but has used their business email address to configure it.

    Outlook prompts the user to login, but logging in will fail as it’s effectively requesting credentials against the O365 service.

    This behaviour also breaks the experience for existing profiles, not just newly created ones.

    The “workaround” we have is to add a registry change to end users PC to bypass the O365 endpoints. From this article: https://support.microsoft.com/en-gb/help/2212902/unexpected-autodiscover-behavior-when-you-have-registry-settings-under

    This property needs to be set to a DWORD value of 1: ExcludeExplicitO365Endpoint

    This workaround is hard to manage, client specific, and will need to be reverted if the customer ever does in fact move to O365 so that the Direct Connect method can work again.

    My suggestion would be to re-consider this change and how Autodiscover may work more intelligently going forwards.

     

    The request was made to put the behavior back to what it was.

    The response:

    We cannot fulfil this request as we will continue to optimize for the Office 365 experience. The supported implementation of Autodiscover is documented here, https://support.microsoft.com/en-us/help/3211279. Any ongoing changes and improvements will be documented in the article. We appreciate your feedback and take every request with consideration, whether we can move forward with it or not.
    -Outlook Team

     

    If you are running Office 365 they assume that you are using Exchange in the cloud even if you aren’t.  And if you are, and don’t like the new behavior… tough cookies.

  • December 2018 non-Security Office Updates have been released

    Posted on December 4th, 2018 at 15:04 PKCano Comment on the AskWoody Lounge

    These are December 2018 Office updates. They will not be included in the DEFCON approval for the November patches. Unless you have a specific need to install them, you should wait until Susan Bradley (Patch Lady) approves them and any problems have been reported.

    Office 2010

    Update for Microsoft Office 2010 (KB4227172)
    Update for Microsoft Office 2010 (KB4461579)

    Office 2013

    Update for Microsoft InfoPath 2013 (KB4022181)

    Office 2016

    Update for Skype for Business 2016 (KB4461545)
    Update for Microsoft Project 2016 (KB4461540)

    There were no non-security listings for Office 2007 (which is out of support).
    Office 365 and C2R are not included.
    Security updates for all supported versions of Microsoft Office are released on the second Tuesday of the month (Patch Tuesday).