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
  • KB4461614 kills Office 2010 same as KB4461522

    Home Forums AskWoody support Microsoft Office by version Office 2010 and earlier for PC KB4461614 kills Office 2010 same as KB4461522

    This topic contains 9 replies, has 6 voices, and was last updated by  ashfan212 6 months, 4 weeks ago.

    • Author
    • #311784 Reply

      AskWoody Lounger

      Have just confirmed the latest January 2019 KB4461614 patch for Office 2010 32 bit  causes Word to fail with the same getdateformatex error as happened in November 2018 KB4461522

      KB4461522 was retracted by Microsoft but the fault is back again.

      Uninstall the patch and you’re right to go.

      Thought I’d add this here as searches of the AskWoody forum didn’t yield any results for KB4461614

      7 users thanked author for this post.
    • #312624 Reply


      Same for us on Office 2010 32 bit. Removing KB4461614 fixes the issue.

      2 users thanked author for this post.
    • #316744 Reply


      Windows 7 Pro x64 – Office 2010 32bit

      KB4461614 shows as an “unchecked” Important update on my system.

      • #316747 Reply

        Da Boss

        We do not recommend installing UNCHECKED updates.

        KB4461614 caused problems with Access and Excel 2010.
        On 1/18 (or 1/22) Microsoft have issued KB4462157 to mitigate those issues.
        Nevertheless, we are still on DEFCON2 and recommend holding off on Jan patch installation.

        3 users thanked author for this post.
    • #316771 Reply

      AskWoody Plus

      It seems a bit over-dramatising the situation to assert that:

      “After you install this security update, Microsoft Access 2010 and Excel 2010 stop working.

      To resolve this issue, install (KB4462157)”

      Is it OK to assume that installing KB4462157, which I do appear to have done, eliminates this GetDateFormatEx error, because it certainly did not stop Access 2010 and Excel 2010 from working, only, perhaps one small feature of these.  Would I have noticed?

      Dell E5570 Latitude, Intel Core i5 6440@2.60 GHz, 8.00 GB - Win 10 Pro

    • #316820 Reply

      AskWoody Lounger

      It would be nice if @gonetoplaid or one of the MVP’s here could do an analysis of the files within KB4461614 and KB4462157 to see just what the difference is between them. When I checked WU on one of my machines a few minutes ago, they were both listed as available, but only KB4462157 was checked.

      Now, since we don’t install any updates that aren’t checked by default, I wonder just why both were offered in the first place instead of just offering up KB4462157 and no longer offering KB4461614?

      Messed up supersedence chain perhaps on Microsoft’s part?

      For additional clarification, KB4462157 was only listed as an Update, not a Security Update as KB4461614 was.

      • #316821 Reply

        Da Boss

        You may have just answered your own question. Non-security updates do not metadata supersede Security updates. If KB4462157 is non-security, you will still see both.

        • #316822 Reply


          Insert “embarrassed” emoticon here! I’d forgotten that simple fact prior to your response! 😉 So, I guess the snafu’s Micsoft’s issue, in that they didn’t label the patch for the patch correctly.

          Their thinking must’ve been “Offer it in the event the user has problems and comes to WU for a solution”.

          NOW, we might wind up with the same issue as the last stack update for Windows 7, that it (the patch) wasn’t labeled as a Security Update so folks just ignored it until it was too late in many cases.

          One difference, though, in that this patch is checked by default instead of the security patch it “replaces”.

          • #316824 Reply

            Da Boss

            If KB4461614 is no loonger checked, MS intends that it not be installed.

    • #316975 Reply

      AskWoody Lounger

      Office 2010 32-bit running on Windows 7 Home Premium x64

      I am sorry to hear that these patches are causing problems. For some reason, my computer appears unaffected even though I installed both since-retracted November, 2018 non-security Office 2010 patches without subsequently uninstalling them.

      I did NOT install the 4 retracted Office 2010 patches dated January 2nd. However, I did install KB4461614 on January 10th along with January’s monthly rollup. I believe that KB4461614 initially appeared unchecked but I checked it manually and installed it because it was indicated as a security update.

      When the problem with KB4461614 was noted on January 15th, I tested Word, Excel and Outlook and was able to open them successfully. I do not have Access on my computer.

      On January 25th, I was offered KB4462157 as a checked update and installed it successfully. I then tested my Office 2010 applications and have thankfully not received any errors. I am assuming that the GetDateFormatEx error would appear on startup of Excel, Word or Outlook if my decision to install KB4461522 and KB4461614 were affecting my computer.

      I am curious as to why my computer is not experiencing the reported error. I couldn’t tell from the thread discussion whether the errors caused by the installation of KB4461522 and/or KB4461614 were universal or limited in scope.

      I am just trying to learn so as to be better prepared going forward. If it is unknown why some were affected while others such as myself were spared then so be it. This is obviously disconcerting and it appears that I have been very lucky (so far).

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: KB4461614 kills Office 2010 same as KB4461522

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