This message was deleted.

@Matthias Schlimm if you do find something let me know please. Same for me, I will respond back as well.

Testing out new Teams now aswell, and I am having the same issue, "update now" keep prompting all the time. Did you find a solution for this issue @Matthias Schlimm ?

not really

😞 Guess I have to wait with the new Teams version until they sort all this out.

Yea same here 😞

For VDI the deadline is 30. June

I am ready to roll out, gpo, fsx exclusion, etc, done , just need that "update now" button hidden. Just hope they fix that before 30June :)

I‘m waiting for the GA of FSLogix HF3

Wait - so even with the disable autoupdate - a user could STILL update it if they did so manually? That's ridiculous.

In my testing, I get the button, it doesnt do anything, it just close Teams, starts it again.

I guess that is better than it updating over and over again in a nonpersistent environment, but not by much.

true, it doesnt get stuck in any loop, but I am not sure what happen for other users on the same server, if it close it for them too. havent put 2.1 in prod yet.

Ah, you're doing multisession. I wonder if it upgrades on single session VDI

"Team" (lol, I crack myself up) found today that even with setting the registry (DWORD 1 disableAutoUpdate), and also setting it in a GPO for good measure - that users are still prompted for an update to teams! We used the boostrapper -p -o option for install and I'm questioning if that really is the correct method at this point. Curious if I just missed something or if this is a non-documented issue that will once again affect millions...

I think it's doing what it's supposed to - it's not "auto" updating. That doesn't mean "dont give user an option to update" in Microsoft parlance. Hence, MS needs a key that is "prevent user from updating" or "hide update prompt"

Yea, I am starting to believe what @langsbr said is true.