Share via

New Outlook crashes when opening calendar overview of my team

Anonymous
2025-03-10T10:15:07+00:00

Hello everyone,

Since around 3 weeks my Outlook (new) crashes when I am trying to open the calendar overview of my team (the "show all" button).

I am not receiving any error message, it just closes.

I could not find anything on the topic, any ideas how I can fix this?

Thank you for your help in advance.

Outlook | Windows | New Outlook for Windows | For home

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

25 answers

Sort by: Most helpful
  1. Anonymous
    2025-04-28T23:53:30+00:00

    Genius!! I tried other solutions and none worked. This one worked!!! Thank you!!

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-05-20T23:43:45+00:00

    I found a workaround by disabling the “show weather on the calendar” from  File / Options / Calendar .   

    Good luck!

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-03-17T07:59:29+00:00

    Hi Erich,
    I'm glad to hear that it works for you again.

    Unfortunately, I have the same version and it doesn't work for me yet.
    Though, I have opened up a support ticket through Outlook and I will share the results if we'll be able to solve it this way :)

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2025-03-13T13:52:39+00:00

    I have the same issue when I try and show all or just an individual's calendar -- repair did not fix the issues.
    The microsoft response indicates that the person who responded do not know why it is happening or that they have implemented a fix

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2025-03-12T18:46:02+00:00

    I have the same error since about 3 weeks. When I click to "show all", the app is closing. This is only in the new App-Version. Into the old-Version and into the Webbrowser, the bug is not here.
    I was still on "repair", no changes.

    1 person found this answer helpful.
    0 comments No comments