This includes a few folks on Reddit that have been reporting this exact same thing since Monday as well:Īnyone else seeing this? I'm losing my mind here because we just get more and more reports with no end in sight. Microsoft doesn't seem to be acknowledging any issues, and many of us are just plain stuck with royally pissed off users. Uninstalling the June 2023 Windows cumulative update does not affect the issue, and having M365 Apps on Current Channel or Monthly Enterprise Channel makes no difference for the symptoms. (First thing I suspected since this and other security clients broke Chrome from opening correctly starting last week) The issue is reproducible when our EDR (Cisco Secure endpoint) is removed from a client. We've already employed all manners of usual fix attempts (new profiles, clearing caches, etc) to no avail. To better understand the issue and provide possible solution, we need more details from you, please kindly provide us the following information. * Outlook not syncing messages until 20-30 minutes after the mailbox receives them As per the description you have shared, we understand that you have a concern with missing 'Open hyperlinks from Outlook in:' option in Outlook. The system tells me it is a Policy issue and tells me to contact my administrator. Ive tried nominating Edge or Chrome as the default browser but the fault is the same. * Outlook will random lose connectivity and throw a red exclamation mark onto the taskbar icon None of the hyperlinks or mail to: links contained in emails can be used to initiate the browser. * Outlook freezing (going "not responding") after 5 minutes of usage For us, the most prevalent symptoms include: Since the beginning of this Monday, we've seen a pretty massive uptick in our environment of complaints about Outlook (another some other pieces of M365 Apps like Word, Excel, Teams) having issues. I think somewhere there is a bad IPv6 routing issue. Error on the event was "destination unreachable (no route to destination)".ĭisabled IPv6 on the network adapter and their Outlook issues **immediately** went away. For one example, 2603:1036:305:48ca::2 in Texas, which is our Exchange Online front door. Immediately noticed that while Outlook was in the middle of it's "not opening" phase, there were a **ton** of retransmits over IPv6 to Microsoft endpoints. EDIT: Finally got a client where the issue was constantly reproducible enough to get a Wireshark and ProcMon capture.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |