Open arkimber opened 3 months ago
Hi I'm an AI powered bot that finds similar issues based off the issue title.
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
This should be moved to the winget-pkgs repo.
Teams Classic is deprecated and will be unavailable after june 2024 anyway. https://learn.microsoft.com/en-us/microsoftteams/teams-classic-client-end-of-availability
Microsoft is rolling out the "new" Teams to anyone using classic right now, so this is more or less their planned behaviour. At some point in time Teams Classic needs to be removed from the repo.
Should have been fixed. Could you try again?
Brief description of your issue
Microsoft Teams "New" and Microsoft Teams Classic appear to have same ID when using update. There are others bugs with similar issues but with Teams site wide installer and not Classic and the "new" work and school version. Both classic and "new" Microsoft Teams are installed on the system. Winget produces the following when running winget update which indicates Teams classic and new Teams appear to have the same ID.
Steps to reproduce
Winget update is run.
Expected behavior
Winget to update Microsoft Teams Classic
Actual behavior
Winget is attempting to update Microsoft Teams Classic to "new" Microsoft Teams but that is already installed on system.
Environment