Microsoft should FIX - "Errors were detected while saving (filename)"

Asha Kanta Sharma 81 Reputation points
2020-07-27T18:53:59.793+00:00

Microsoft must FIX this decade long bug with appears out of nowhere and has ruined a lot of months of work of my life. Please fix the below error message. It is even appearing in latest Office 2019.

"Errors were detected while saving (filename). Microsoft excel may be able to save the file by removing or repairing some features. To make the repairs in a new file click Continue. To cancel saving the file click Cancel."

THIS ERROR/BUG HAS RUINED MY LIFE PROFESSIAONLLY.

FIX IT WITHOUT FURTHER DELAY...

Excel Management
Excel Management
Excel: A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.Management: The act or process of organizing, handling, directing or controlling something.
1,643 questions

22 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. WhyNot Nera 0 Reputation points
    2023-09-30T03:02:45.8266667+00:00

    How, To download this spreadsheet, simply click File --> Download --> Microsoft Excel. You'll then be able to open this in your spreasheet tool, and can delete this comment

    0 comments
  2. Nguyen, Vincent 0 Reputation points
    2023-10-28T04:07:03.6433333+00:00

    Hi All,

    I tried all the ways to fix but all suggestions didn't not work for me until I had the IT guy helps.

    The solution is: I uninstalled the current version of MS Office, after that I re-installed the MS office again ( I'm using MS 10).

    Whenever this issue happened, I did this step again.

    It completely solve the issue.

    Hope this help to you guys also.

    Thank.

    0 comments
  3. ATKI 0 Reputation points
    2023-12-18T11:27:33.8266667+00:00

    Hi,

    I encountered this problem today on a Macro-Enabled file that I had open while changing my Microsoft password. I am tying the occurrence of this problem when saving with password changing, as I did not do anything else in particular with the Excel file that I didn't do since I created it 4 years ago.

    After reading through various solutions, I tried the following:

    1. Saving the file with another name: file wouldn't allow me to save it with a new file name, I received the same error again
    2. Did an inspection of the document with Document Inspector and noticed several errors in its results
    3. Copied and pasted all sheets + VBA code to a new file - this worked

    But I wanted to know where the problem was, so I opened both the new (solved) file and the old (with error) file with a compression tool and checked internal file sizes. I noticed a big difference in the xl\vbaProject.bin files between the 2 Excel files.

    I opened the bad file in Excel once again then went to VBA and commented all my VBA codes (didn't export modules or anything, just added comments to the entire VBA code). Then I saved the Excel file normally (CTRL+S) and saving worked without issue. Then I removed the comment characters I previously added and saved the file and it worked again (it is now fixed).

    In conclusion, I still don't know exactly what the problem was, but it appeared while changing the Microsoft password with the Excel file open, then was fixed by commenting all the VBA code inside + saving, then removing all previously added comments from all VBA code + saving again.

    I hope this helps.

    0 comments
  4. Bob Zabcik 0 Reputation points
    2024-01-17T04:28:54.89+00:00

    Hi All! I have run into the many forms of this problem over the years and created this GitHub repository to hold VBA code you may find helpful in recovering from and more importantly, avoiding it altogether. Good Luck Everyone! Hopefully Microsoft will catch a clue on this but I'm personally not hopeful.

    0 comments
  5. melsey 0 Reputation points
    2024-02-29T20:05:47.89+00:00

    Thought I would share my experience with this horrendous Excel error. I too lost a lot of work to the error. I've started doing a SAVE AS every once in a while so I build up a number of old backup files. All my versions will be working, then I usually encounter this error when I do another copy. I then try to open the previous save as version, and I find that file does the same thing! Even though it was working 100% perfectly minutes or days ago. I usually have to go back 2 or 3 older copies to get one that works. How can a file work one day perfectly, and I don't touch it, and then all of a sudden it has the same save bug? Now, in addition to doing a save as, I copy all the VBA code/modules/classes/etc to text files as a backup. As sometimes when I get the error, all my modules will be inaccessible so I can't copy the text out of them into another file, once the error occurs.

    0 comments