Jump to content

Outlook Problems after windows updates


Weslleyy

Recommended Posts

Hello Everyone,

Is anyone else experiencing strange issues with Outlook? We're seeing cases where users face problems when starting a new email, causing the client to crash. Additionally, some users are reporting connection issues.

We are using Outlook Semi-Annual Channel version 2402 (17328.20588) along with the latest version of FSLogix.

I came across this Reddit thread: Recurring Microsoft 365 Authentication Issues in Citrix, which mentions:

Did you install the KB5043064 September update?
It breaks the broker plugin again due to an issue with the appx.
We had multiple customers facing login issues and error 1001 (so tired of this error). We blocked and removed the update from our systems, which fixed the issue.

Although it's not specifically a Citrix issue, it seems to occur in combination with FSLogix. Even non-Citrix environments, such as AVD setups using FSLogix, are experiencing the same problem.

Has anyone else encountered similar problems? Any insights or solutions would be appreciated.

Link to comment
Share on other sites

  • Replies 6
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

I am curious if you run this command after OSOT in the golden image, will it fix it for the VDI?

if (-not (Get-AppxPackage Microsoft.AAD.BrokerPlugin)) { Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown } Get-AppxPackage Microsoft.AAD.BrokerPlugin

 

Link to comment
Share on other sites

  • 3 weeks later...

This issue has only started in the past two months, and I haven’t encountered it before. Here are the details from the Event Viewer logs:

  1. Outlook EXE Error Log:

    • Application: OUTLOOK.EXE

    • Module: MsoAria.dll, Version: 16.0.17328.20004

    • Exception code: 0xc0000005

    • Error offset: 0x00007a82

 

Naam van toepassing met fout: OUTLOOK.EXE, versie: 16.0.17328.20588, tijdstempel: 0x66de80eb

Naam van module met fout: MsoAria.dll, versie: 16.0.17328.20004, tijdstempel: 0x65b85baf

Uitzonderingscode: 0xc0000005

Foutmarge: 0x00007a82

Id van proces met fout: 0x34cc

Starttijd van toepassing met fout: 0x01db1e0bf0f8aac3

Pad naar toepassing met fout: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE

Pad naar module met fout: C:\Program Files (x86)\Microsoft Office\root\Office16\MsoAria.dll

Rapport-id: b812868d-cc5f-46cb-a15d-1c6dfbe289aa

Volledige pakketnaam met fout:

Relatieve toepassings-id van pakket met fout:

 

 

Toepassing: OUTLOOK.EXE

Framework-versie: v4.0.30319

Beschrijving: het proces is beëindigd als gevolg van een onverwerkte uitzondering.

Uitzonderingsinformatie: System.AccessViolationException

bij Microsoft.Teams.MeetingAddin.Telemetry.MsoAriaTelemetry.Client.EventApiClient.Open()

bij Microsoft.Teams.MeetingAddin.Telemetry.MsoAriaTelemetry.Provider.MsoAriaTelemetryProvider.Initialize()

bij Microsoft.Teams.MeetingAddin.Telemetry.TelemetryFlowController.Initialize()

bij Microsoft.Teams.MeetingAddin.Telemetry.TelemetryManager.BeginInitialize(Microsoft.Teams.MeetingAddin.Telemetry.ITelemetryProvider, Boolean)

bij Microsoft.Teams.MeetingAddin.Application+<>c__DisplayClass71_0+<<SetupTelemetryAsync>b__0>d.MoveNext()

bij System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.Boolean, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Start[[Microsoft.Teams.MeetingAddin.Application+<>c__DisplayClass71_0+<<SetupTelemetryAsync>b__0>d, Microsoft.Teams.MeetingAddin, Version=1.0.24255.3, Culture=neutral, PublicKeyToken=null]](<<SetupTelemetryAsync>b__0>d ByRef)

bij Microsoft.Teams.MeetingAddin.Application+<>c__DisplayClass71_0.<SetupTelemetryAsync>b__0()

bij System.Threading.Tasks.Task`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InnerInvoke()

bij System.Threading.Tasks.Task.Execute()

bij System.Threading.Tasks.Task.ExecutionContextCallback(System.Object)

bij System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

bij System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

bij System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef)

bij System.Threading.Tasks.Task.ExecuteEntry(Boolean)

bij System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

bij System.Threading.ThreadPoolWorkQueue.Dispatch()

bij System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Link to comment
Share on other sites

MsoAria.dll is related to the New Teams Outlook Add-In, I would suggest disabling that and trying your testing again - I don't have a solution offhand for that, but I remember someone mentioning last week some... challenges... with it - if it stops the crashing, it's at least another rabbit hole to go down troubleshooting wise (if someone else doesn't pipe in with the solution I'll try to remember to go looking later when I'm not supposed to be working on a document 😄 )

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...