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

Anonymous
2019-01-23T16:00:56+00:00

Good day team.

We're getting this when opening any document in office 2010. We're running it on WinXP SP3 32 bits.

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

Haven't found any solution so far, all help is welcome.

Microsoft 365 and Office | Install, redeem, activate | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2019-01-23T23:18:47+00:00

OMG! I was having the same error message "The procedure entry point EnumCalendarInfoExEx could not be located in the dynamic link library Kernel32.dll" So I checked to see what updates had been installed since I was in the office last week... KB4462157 on 1/18/2019. Uninstalled that one and Excel is now working! I hope this fix works for you as well.

Was this answer helpful?

0 comments

75 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-07-07T05:21:51+00:00

    Me neither. After uninstalling some without success, I uninstalled 4462223, 4464567, 4461626 and it worked for me. If uninstalling only one I would try 4462223 first.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-06-19T23:54:31+00:00

    Try this. 

    https://support.microsoft.com/en-us/help/4478844/office-updates-for-new-japanese-era 

    I Googled "all ms office 2010 japanese calendar updates"

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-06-19T22:43:58+00:00

    This did not work for me. My windows 2003 server did not even have the update KB4462157. However, I removed mostly all the updates that started with KB446 and still didnt work.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-06-06T17:43:29+00:00

    Read the thread. All the answers are already there. MS already fixed it months ago except for MS XP which they stopped supporting years ago.

    Was this answer helpful?

    0 comments