The procedure entry point EnumCalendarinfoExEx could not be located in the dynamic link library kernel32.dll

Hey, John, I was getting ready to call Microsoft but I thought I'd take your suggestion and double check the updates that I removed. 

I went to Add or Remove Programs.  Show updates was checked.  This time I changed Sort by from Name to Date Last Used. I found KB4462177 and removed it.  The system still didn't work.  I then removed KB4462174 and VOILA I was able to open all Office programs and documents.  I'm not sure why changing Sort by made a difference.

How Microsoft can release updates that haven't gone through prototyping and proofing is beyond me.  I'll never install their fixes again.

Here it is folks! 

Read it and weep. (and whoever guessed it was related to some Japanese thing ought to be given a job at MS!

https://www.zdnet.com/article/microsoft-pulls-buggy-office-2010-january-updates/

Microsoft pulls buggy Office 2010 January updates

Microsoft's preparations for a new Japanese era coming later this year break Excel.

Microsoft has pulled its first updates of the year for Office 2010 after reports, mostly from Japan, that they have been breaking Excel. 

The updates arrived on January 2 with changes in the Japanese calendar, most likely to reflect the changes coming with the end of Japanese Emperor Tenno Akihito's reign. He is planning to abdicate on April 30, 2019, marking the end of the Heisei era and ushering in an as yet unnamed new calendar era. 

As reported by Borncity, Microsoft pulled the January 2019 Office 2010 updates on January 5. All updates for Excel 2010 and Office 2010 included "changes to Japanese calendar". 

Japanese language blogs have reported that after installing the non-security updates, users were seeing messages that 'Excel cannot be opened' and that the spreadsheet app was sometimes freezing. Excel also couldn't handle new entries in cells. Users reported that uninstalling the updates resolved the issue.

I have this same issue, however the system I have does NOT have the update listed in the previous answer. Does anyone know if any other updates cause this same issue?

Hi Paul

The only updates that I am aware of causing this problem are KB4461522, KB4461614, KB4462157 and KB4462174.  I suggest that you check and ensure that none of those have been updated to your system but apart from date I don't know what to suggest.  Hopefully some other contributor to this Community can help.