Hi Sarah Mays,

I don't think you can, what issues are people having?

I'm running the same version, just had an hour meeting this morning, which was OK, so interested what you dislike so much, thanks.

I have yet to have a meeting, but the issue comes with the accessibility of the app. We can hardly read the teams messages because the messages are squished to the side from the other chats in the inbox. Also, the apps menu has disappeared and to get to it, it just adds another step and is no longer easily accessible. These are small things, but it completely messes with the efficiency of my team. There's more that I can't think of. I honestly didn't expect anyone besides a bot to see this, otherwise I wouldn't have been so harsh and called the update "terrible."

Hello Lisa B,

My name is Akande and i'm happy to help with your request.

When you edit a file in Teams, it should automatically update the original file in the shared drive. However, there are a few reasons why this may not be happening. Here are some troubleshooting steps you can try:

1. Check the version history: Teams saves a version history of your file. You can check the version history to see if your changes were saved in a previous version. To do this, click on the file in Teams, then click on the three dots (...) on the top right corner of the screen, and select "Version history". You can then see the previous versions of the file and restore an older version if necessary.
2. Check your internet connection: Make sure you have a stable internet connection. Sometimes, if your internet connection is slow or intermittent, your changes may not be saved properly.
3. Check file permissions: Make sure you have the appropriate permissions to edit the file. If you don't have the right permissions, your changes may not be saved.
4. Check if the file is locked: If someone else has the file open, you may not be able to save your changes. Ask your colleague to close the file or work on it at a different time.
5. Sync your files: Try syncing your files to make sure you have the latest version of the file on your local drive. To do this, click on the file in Teams, then click on the three dots (...) on the top right corner of the screen, and select "Open in SharePoint". In SharePoint, click on "Sync" on the top right corner of the screen. This should sync the file to your local drive, so you can edit it and save it locally. Once you save the file, it should sync back to Teams and update the original file in the shared drive.

Hope one of these helps.

With Regards, Akande.

Dear JohnY_MSK,

Good day! Thank you for posting to Microsoft Community. We are happy to help you.

In the Microsoft Teams desktop app, the terms “Teams version” and “Client version” refer to different aspects:

1. Teams Version indicates the specific build or release of the Microsoft Teams application. It includes updates, new features, functionalities and bug fixes that have been implemented over time. You can find the version number in the app settings, which helps you ensure you’re using the latest version with all the current features and improvements. Refer to Version update history for Teams app deployments - Office release notes | Microsoft Learn.
2. Client Version is a more technical term that refers to the underlying framework or components used to run the Teams application. It might include information about the operating system, browser, or other dependencies, refers to the specific version of the underlying client software that interacts with the Teams backend. Microsoft Teams can be accessed through different clients, such as the desktop app, web client, or mobile app. Each client might have slight variations in features and performance. For example, the desktop client is typically more feature-rich and performs better for intensive tasks compared to the web client. Refer to Overview of the new Microsoft Teams client - Microsoft Teams | Microsoft Learn.

I hope the information helps! If there is any update or I misunderstand you, please feel free to let me know. I will continue to assist you. Your understanding and co-operation are highly appreciated.

Hi Mia,

Thank you for the reply. Luckily the IT group at my work was able to recover the files with the version history via the SharePoint recycle bin. Since that has been restored, I've decided to try to figure out where the issue lies. I've tried the following and had these results:

1. I Replaced a non-microsoft file in SharePoint and this makes a new version in Share Point. When checking in the Version History through Share Point, I see there are several records of version history, however, when navigating to the "Synced" file via Windows File Explorer (it shows a green circle with white check mark in the Status column indicating it is synced), opening up the file's Properties dialogue box and clicking the tab "Previous Versions", there are no previous versions documented. This indicates there is lack of communication between Share Point and the supposedly "Synced" folder in Windows File Explorer.
2. I Replaced the same non-microsoft file in Windows File Explorer and this over-wrote the current version in Share Point. In other words, there were 3 versions before I performed this action, and afterwards, there were still three. The original 2 versions stayed, but the 3rd was replaced instead of a 4th version being created. One observation is that the "Modified" column date for the 3rd version (replaced) matched the Date Modified from the file I used to replace it with. While performing the action in (1) above where I replaced the file via Share Point, the "Modified" date was changed to the date and time at which I performed the action of Replacing it. While checking the version history for the action of replacing via Windows File Explorer, the Properties dialogue box still shows no previous versions available under the "Previous Versions" tab.
3. I replaced a non-microsoft file in SharePoint that is linked to a Teams document library. The results were the same as in action (1) with all version history maintained and a new version created.
4. I replaced the same non-microsoft file as in action (3) in Teams. The results were the same as in action (3).
5. I replaced the same non-microsoft file as in actions (3) and (4) in Windows File Explorer synced folder and the results were the same in action (2) with the latest version being replaced. 

So my conclusion is that my assumption (which I think is reasonable) that a "synced" document library should perform exactly the same as the original source (Teams/Share Point) is unfortunately wrong. Not only is it wrong, but the use of Windows File Explorer to replace documents and maintain Version History is detrimental to any previous Version History because it completely erases it, or erases the most recent version (the seems to be inconsistency in the result).

I strongly encourage Microsoft to create a "Replace All" Button in Teams and Share Point so that a user can Replace multiple documents at once without having to hit the "Replace" button for each individual document. I often plot 30+ drawings from AutoCAD to PDF (create from scratch with the same file name) and then need to replace them in Share Point. Seems silly that in the year 2021 that a user is required to do this. And that line of thinking is exactly how I ended up trying to "Sync" and use Windows File Explorer to perform that action.