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)
We are using shared reports from a sharepoint having the convenience of accessing these reports via browser. But a few days ago, certain users are having problems with these reports, because when they access them, they see gibberish rather than normal text. This does not happen when its opened on the desktop app, only when its opened on the browser.
How can I fix this?
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.
Has there been any fix to this problem? its now impacting multiple users in our organization.
As workaround,
1.Some user reported issue only with Arial font, change the font to other format.
2.Use desktop application.
Thank you. One of the key members of our team is receiving multiple files daily in this corrupted format (50+). As a result the workaround is taking up a lot of time so please let us know if there are any updates regarding a more permanent solution.
Follow steps in this article and try to create a support ticket to contact Online Support.
@Snow Lu how about Microsoft just give all users upgraded licenses since your current product isn't meeting the low bar of users getting what their companies are paying for? You could say that legally speaking the product is not currently fit for purpose which if not rectified could be taken to the consumer tribunal here in New Zealand. Its ridiculous that the update wasn't just rolled back to remove the workflow breaking bug.