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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-01-26T04:58:44+00:00

    Thank you!  It worked for me.  I tried several things including reinstalling Office 2010 but nothing worked.  I uninstalled the update and Office now works well.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-01-24T00:30:31+00:00

    Thanks a lot! It worked!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-01-23T19:45:26+00:00

    It happened to my client today. 2 machines have the same issue. One of them has GetDateFormatEX could not be located. The other one has EnumCalendarinfoExEx error. I have to reinstall 2010 Office with SP2 to fix it in the other machine.

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more