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

I called MS. The guy recommended I reinstall Office. Luckily this was only on my backup machine. The one (same one, add'l license) on my Windows10 machine has been working. I'd be interested to know which operating systems we all are struggling with. I can't remember if anyone has mentioned their OS on here or not.

FYI - He offered to take control of the machine and fix it for me but my machine was too old, just being my backup.  If any of you are still stuck, give them a call. After following the telephone menu choices on the phone,  it got down to pressing the button for paid assistance or free online help, I pressed paid assistance and then explained it was their update that suddenly ruined my Office so he was OK with helping me. I had explained I had already tried all the free online help and it still didn't work. I also isolated the problem proving it was them cause I said this being my backup machine, I have it set up so that no software can execute on it so it's not a virus. (I have 2 accounts - admin rights and no admin rights and I log in with no admin rights for regular use so nothing can execute except updates.)  

When I went to turn off my machine (after an hour of getting Office all set up again the way I like it by comparing each option, toolbar, etc. for each application - really tedious) my machine said updates were waiting but there's no way to see which ones but I'm sure it's for Office since I didn't have any updates 2 hours ago before reinstalling. I clicked on 'shut down without updates'. On my old, back up machine I have that choice. I think I'll let it 'work' for a couple of weeks and then try the updates and if it breaks again at least I'll know what needs to be done. In reference to your response, I had taken out 4462 - 186, 174, 182, 172 and 187. I didn't have 157 and not sure if I had 4461614 or not.  

I just found this if anyone still needs this: [ https://latesthackingnews.com/2019/01/09/microsoft-pulled-january-2019-updates-due-to-an-issues-with-excel/ ]

After repeated complaints from the users, Microsoft eventually pulled back the four updates launched for Microsoft Office 2010. These include an Update for MS Excel 2010 (KB4461627, and three updates for Microsoft Office 2010 (KB4032217, KB4032225, and KB4461616).

I'm sick to my stomach. 

I finally learned how to do this and uninstalled KB4462174 and it still doesn't work. I ckd my list 5 times and I con't have the other ones on there.

I wish to heck that MS would just release the KB #"s that are culprits. I don't know what else to do. It's a big guessing game. 

I guess I could delete everything on this Feb 2019 list found at https://support.microsoft.com/en-us/help/4488446/february-2019-updates-for-microsoft-office

Excel 2010	Description of the security update for Excel 2010: February 12, 2019 (KB4462186)
Office 2010	Description of the security update for Office 2010: February 12, 2019 (KB4018313)
Office 2010	Description of the security update for Office 2010: February 12, 2019 (KB4462174)
Office 2010	Description of the security update for Office 2010: February 12, 2019 (KB4462177)
Office 2010	February 5, 2019, update for Office 2010 (KB4462172)
Office 2010	February 5, 2019, update for Office 2010 (KB4462187)
Outlook 2010	February 5, 2019, update for Outlook 2010 (KB4462182)

The problem is this. You John said 2174 was a problem and the MS list says that's from Feb 12, 2019.

But there are articles that say that MS pulled the Jan 2019 updates and that's a different list of KB's so do I do all the ones from Jan AND February????

Here's the January list.

Product	Knowledge Base article title and number
Office 2010	Description of the security update for Office 2010: January 8, 2019 (KB2553332)
Office 2010	Description of the security update for Office 2010: January 8, 2019 (KB4461614)
Office 2010	Description of the security update for Office 2010: January 8, 2019 (KB4461617)
Outlook 2010	Description of the security update for Outlook 2010: January 8, 2019 (KB4461623)
Word 2010	Description of the security update for Word 2010: January 8, 2019 (KB4461625)

So far, I have removed these updates and all works

KB4462157

KB4461614

KB4462174

I have also stopped automatic updates, so that I can control what updates are installed.

I still log in anxiously each time though :|

I'm sick to my stomach. 

I finally learned how to do this and uninstalled KB4462174 and it still doesn't work. I ckd my list 5 times and I con't have the other ones on there.

I wish to heck that MS would just release the KB #"s that are culprits. I don't know what else to do. It's a big guessing game. 

I guess I could delete everything on this Feb 2019 list found at https://support.microsoft.com/en-us/help/4488446/february-2019-updates-for-microsoft-office

The problem is this. You John said 2174 was a problem and the MS list says that's from Feb 12, 2019.

But there are articles that say that MS pulled the Jan 2019 updates and that's a different list of KB's so do I do all the ones from Jan AND February????

Here's the January list.

NOWHERE however can I find a DEFINITIVE list of the KB#'s of the updates that caused the problems. I feel MS ought to share that list. From what I'm reading, this issue started back in November 2018 where Japanese users were affected first.

It all has to do with how the Japanese define their years. 

I have some updates that are related to the Japanese calendar thing but they may be healthy cause they came out more recently. I am only going by the list above but there is a list here at this link below but that doesn't mean they all caused problems. It's just the list of Office 2010 updates since this year.

https://support.microsoft.com/en-us/help/4488446/february-2019-updates-for-microsoft-office

And in this list it shows KB4462174 as Feb 12th which seems odd since this Japanese calendar issue was discovered back in Nov '18. All very confusing...

MS just really needs to release a list of the KB's that have issues and provide the exact KB #.