Operational Defect Database
BugZero updated this defect 53 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 97111
Microsoft Store Apps stop working in VDI after applying Microsoft Monthly Patch (KB5034763)
Last update date:
3/27/2024
Affected products:
Horizon
Dynamic Environment Manager
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
After updating Microsoft Monthly patches(KB5034763) on non-persistent VDIs, the Microsoft Store apps, such as Office 365, Teams, Power BI, etc., stop working.Store apps like Outlook and Teams show the HTTP 404 Error message on Launch.Occurs when the cache is built for the user by Windows 10 patch updates because the apps are unable to load the online authentication component
Purpose
This article describes the effects on Office 365 applications after implementing the Microsoft KB5034763 patch
Cause
The faulting Microsoft module abb.broker.exe crash results in the 404 error.From the event logs, we see Windows License Activation errors and sign-in errorLicense Activation (slui.exe) failed with the following error code:hr=0x8007232BCommand-line arguments:RuleId=eeba1977-569e-4571-b639-7623d8bfecc0;Action=AutoActivate;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;NotificationInterval=1440;Trigger=UserLogon;SessionId=2“Sign-in error code 50089Failure reasonAuthentication failed due to the flow token expired. Additional DetailsExpected - auth codes, refresh tokens, and sessions expire over time or are revoked by the user or an admin. The app will request a new login from the user.”
Impact / Risks
After applying the KB5034763:* Office 365 applications may fail to authenticate including the Microsoft Teams application* Default File Type Association may not work as expected* Customization of the virtual machine through the Sysprep method may fail
Resolution
The Horizon Engineering team is aware of this issue. Microsoft support could provide further information regarding this patch.
Workaround
Add the registry clusters to disable Modern-Authentication for O365. [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Identity]"DisableADALatopWAMOverride"=dword:00000001"DisableAADWAM"=dword:00000001 Navigate to c:\users\<user>\app data\local\packages in VDI and remove the add.broker xxxxxx directory that contains the cache
Related Information
For reference: The Microsoft Windows Updates for February and March 2024 break the roaming of a user's default browser and .pdf file type association in VMware Dynamic Environment Manager. The roaming of other file-type associations and protocols is not affected.
