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 No 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 No comments

75 additional answers

Sort by: Oldest
  1. Anonymous
    2019-09-08T08:57:37+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.

    This is it

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-09-28T07:41:02+00:00

    I have removed the above installation and have not installed it, but the problem still appears on my computer.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-10-21T16:26:15+00:00

    The problem pops up again after the Sep 10, 2019 updates.

    I removed KB4464566 and that fixed it for me.

    Was this answer helpful?

    0 comments No comments