Share via

Issue resurfaced

Anonymous
2023-07-19T15:35:15+00:00

I have a user who is experienced this past known issue. Currently up to date Microsoft 365 apps on windows 10.
Latest Windows update from July 3rd.

Doing some google search, the workaround that I found on another forum was to scroll up or down / minimize the window - which works.

Microsoft post about resolution below

Users may notice that the incorrect timeslot is selected after clicking a meeting in the Calendar

After user selects multiple calendars in the Calendar pane, they may notice the incorrect timeslot/meeting is selected when they click on a meeting while viewing multiple Calendars.  Calendars where the user has Full Access (which are not automapped) may display incorrectly. 

Potential causes include:

Low screen DPI, or Outlook is not maximized and the window is relatively small in size.

A calendar was added or selected in Calendar pane.

Both non-working hours and working hours are shown in the same view.

FIXED

A fix for this issue has been released in Build 15601.20538 and higher.

Outlook | Windows | Classic 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

3 answers

Sort by: Most helpful
  1. Anonymous
    2023-08-25T19:10:00+00:00

    There was a prior instance of this issue that was fixed and documented here, Users may notice that the incorrect timeslot is selected after clicking a meeting in the Calendar - Microsoft Support.

    A bug was recently opened due to some new reports of the problem. My peer that covers calendar will probably reactivate the Known Issue above.

    The only workaround I recall from the last variant is below. I'm not sure how much it helped, but please give it a try.

    Workaround: Scrolling all the way up and down in the Calendar surface will correct the issue.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-08-04T13:22:38+00:00

    FIXED

    A fix for this issue has been released in Build 15601.20538 and higher.

    Not fixed.

    I'm experiencing same issue on (Version 2305 Build 16.0.16501.20074) 64-bit

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-07-19T19:13:04+00:00

    Dear Jefry Quiros

    Good day! Thank you for publishing in Microsoft Community. We are happy to help you!

    First of all, thank you very much for sharing and contributing! I believe that the method you summarized will help more users.

    In addition, based on your description, I would like to ask you if this error has reappeared, right? And you've tried the method you provided, but it still doesn't work, right? If so, then in order to help you better, I still need to gather more information to narrow down the problem

    • Could you please provide me with more details about your question (e.g. screenshots of the page), thank you.
    • At the same time it seems that you are using the Outlook desktop client, then please kindly try logging in to OWA (Outlook web app)with your account and check if you get the same error, thank you.

    Please also kindly trust me to do more research and testing when I receive the above feedback information I need to help you better, thank you.

    Thank you in advance for your understanding! Your patience and cooperation will be greatly appreciated. I hope all the best!

    Sincerely

    Kerry Chen | Microsoft Community Moderator

    Was this answer helpful?

    0 comments No comments