Forum Discussion
Excel cannot open the file 'Vocabulaire.xlsx' because the file format or file extension is not valid
- I tried many online tools
- I tried solutions like zipping, etc.
- I tried solutions like changing the extensions
- I tried converting to other formats
- I didn't try the permission solution as I'm on macOS. However, I've uploaded the Excel file on Google Driver and it also cannot open it
Does anyone know any other solution to try?
Here is the link to the file:
https://docs.google.com/spreadsheets/d/1kzgDlO19STdTEQoZNnpknyd_c33dSDYF/edit?usp=share_link&ouid=115228673413583900442&rtpof=true&sd=true
Thank you in advance
If make .txt extension and open in Notepad - nothing within file except a lot of not-printable characters. Afraid it's corrupted.
- bijanmoudiCopper ContributorAlready opened and yeah, many zeros like a binary file.
- Patrick2788Silver Contributor
Looks like the workbook is totally corrupted.
I tried:
- re-naming to .zip to view the xml - could not open the compressed folder error
- uploaded to OneDrive and attempted to open with Excel for the web - would not open
- re-named .xls - would not open
- re-named to .csv - would not open
- re-named to .txt - opened in notebook with a whole bunch of spaces and no content
The last item may be the most telling if notepad is not able to show any characters (even if it's letters, numbers, and symbols).
You could try another app that's capable of opening an .xlsx. Might get lucky with Open Office.
- bijanmoudiCopper ContributorThanks for the investigation.
I'm on macOS and not able to open the file in Notepad.
I also saw some solutions for repairing the file with Excel on Windows and I am not able to test those as well:
https://support.microsoft.com/en-us/office/repairing-a-corrupted-workbook-7abfc44d-e9bf-4896-8899-bd10ef4d61ab?ui=en-US&rs=en-US&ad=US
https://support.microsoft.com/en-us/office/repair-a-corrupted-workbook-153a45f4-6cab-44b1-93ca-801ddcd4ea53?ui=en-US&rs=en-US&ad=US- bijanmoudiCopper Contributor
Patrick2788 SergeiBaklan
Could you please test these solutions as well if you have access to a Windows-based device?