tomdw's avatar
tomdw
Brass Contributor
Oct 24, 2024
Status:
New

FSLogix - 48v35 error at Microsoft login prompt in AVD

I'm resposting from this thread to hopefully create more attention for this problem:

https://answers.microsoft.com/en-us/outlook_com/forum/outlk_win-outtop_new-outsub_ofb/outlook-error-message-somehting-went-wrong-48v35/97d7ff71-8a58-40c8-8726-adf3d1f095b8

 

Me and other admins (from reposted thread) have specific users who experience M365 authentication problems after upgrading to the latest FSLogix version(s) that offers support for New Teams.

 

The error occurs in the Azure Virtual Desktop environment, when a user tries to open a Microsoft application (Outlook, OneDrive etc.).

 

Not all users have the problem that they need to reauthenticate, or can't authenticate at all, with the 48v35 error. The users who do however, repeatedly get the same error after a few days or a week.

We tried multiple things, like removing the Microsoft.AADBrokerPlugin directory or creating a completely new FSLogix profile, but the problem stays for these users. 

 

In my case I am using the FSLogix setting RoamIdentity=1.

 

Is there any news from FSLogix on this issue? Or does anyone have workarounds to share?

I would like to update more customer environments to use the New Teams, but with these issues I would rather wait.

 

  • RemyD575's avatar
    RemyD575
    Copper Contributor

    Hello,
    We have the same problem. We are using Horizon 2406 with FSLogix in Instant Clone but with persistent machines. We try to migrate our users on the new Teams but after a few days of use, the users have this error “48v35”. Restarting Windows solves the problem. 

  • _toe's avatar
    _toe
    Copper Contributor

    Same problem here, AVD FSLogix environment too. Continuing to troubleshoot - will feed back if I find anything. Irritating issue.