Office Viewer: Failed to open file - Failed to fetch

Help Studio
1

I am getting an error when trying to open an Excel file using the Office Viewer extension in Studio. Is anyone else experiencing this issue? Seems to have started after I upgraded to Studio 2026.0.199. Cannot open MS Word documents correctly as well. Shows the raw OOXML zip content, which suggests it’s falling back to VS Code’s default plain text editor instead of being handled through a proper viewer. The same extensions work fine within VS Code. Leads me to believe it’s an issue with Studio.

image
image1910×760 123 KB

image
image1341×590 119 KB

2

Ran into this on my own machine last week, workspace trust was the culprit for me. If any of this doesn’t match what you’re seeing, tell me and I’ll dig further.

3

I don’t have the setup to reproduce this but @loginerror can you take a look into this.

4

I think this is something that deserves clarity for everyone. There have been repeated concerns about LLM-generated answers, perceived advantages from close proximity to the Community/Product team, and how such answers are evaluated.

If an answer is being flagged simply because an LLM was used, even when the poster has no issue with the actual structure or content of the solution, that creates an unfair roadblock. An LLM can structure an answer, but that doesn’t automatically mean the underlying solution or contribution is invalid.

@loginerror , it would be helpful if you could clarify the criteria for everyone so that there is no ambiguity—good relations with the Product/Community team shouldn’t mean preferential treatment, and genuine attempts by others to contribute shouldn’t be overdone or treated differently.

If the process is transparent and applied consistently to everyone, that’s completely fair. Otherwise, people are just going to keep wasting time trying to understand rules that aren’t clearly defined.

5

Thank you for the reply. The Workspace Trust for the project folder is trusted.

6

I resolved the issue (found a workaround). The project resides in a folder on my D:\ drive. I moved the project to my C:\ drive and the issue is no longer occurring. So there is an authorization issue with the location of the project on the D:\ drive.