This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Since installing Catalina 10.15 and Office 365 16.30 (updates installed the same day (something I will not due again)) when I attempt to save a workbook that I have used for a couple of years, I receive the alert: 'Your changes could not be saved to xxx.xlsx due to a sharing violation. I then receive the alert The file format end extension of 646820000.mactf don't match.
I contacted the Answer Desk who say it is an Apple Product and Apple support said it is a Microsoft problem.
Any thoughts or suggestions will be appreciated.
A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
The latest insider fast build for 16.38 that was just released resolved the issue for me.
This is were I found it: https://docs.microsoft.com/en-us/officeupdates/update-history-office-for-mac
Today , removed Excel version 16.28, and all references to Excel (plists and the like) and installed the latest version 16.36. The problem still exists.
I thought I had a link to the previous versions of Office 365 but I was mistaken. an you please rode the link to the site (it was mentioned in an earlier response), so I can return to Excel version 16.28? Im dead n the water without this version
Hi All - this has been a difficult issue to diagnose, and we still haven't found a reliable way to reproduce the problem. However, based on all the evidence, especially from this thread, we've been able to speculate on the cause and we are planning to release an update with a change that we hope will fix the problem for Excel. The proposed fix should be available in the Insiders Fast release next week (week of 11-May).
We would greatly appreciate if you would update to the Insiders Fast release next week and then report back here about whether the problem goes away or not.
Many Thanks in advance.
Has there been any progress on this? I opened this discussion in October of 2019 and the problem continues.
When I spoke with Apple Care yesterday, on an unrelated issue, they have no information on this.