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

Asha Kanta Sharma 86 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,649 questions

22 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Steve Lipsman 30 Reputation points
    2024-02-29T20:13:35.0333333+00:00

    VBA in Workbooks Stops Working With Upgrade to Excel 365-VBA Compiling Issue
     
    In my and my client’s continuing struggles with the extremely annoying Excel VBA file corruption issues (VBA code in workbooks stop working with upgrade to Excel 365), I think I may have found something new worth trying. See the Stackoverflow link below, with the relevant proposed solution printed out. I’ve just applied this change to my PC Registry, but I’m hesitant to recommend anyone else do this as I’m clearly no expert in making such PC system changes. https://stackoverflow.com/questions/69018012/vba-workbooks-stop-working-with-upgrade-to-excel-365-vba-compiling-issue  
    I think I perhaps found an answer in this thread: https://lnkd.in/gU3E2bfG

    Per that thread: “the cause is that Excel does not correctly save the compile state of the VBA code and 64-bit Excel cannot recover from that issue when opening the afflicted Excel file (32-bit usually can). A fix was released for only Excel 2016 and not for other versions". That would indeed confirm that it is a bug within Excel and explains why we only see the issue with 365 64-bit Excel.

    That also explains why my manual compile fix works. Based on the article I found, there is a more sustainable fix. You can change Excel’s registry and force VBA to compile accurately.

    To implement the permanent fix:

    1.   Open the start menu and type “reg” and select the “Registry Editor”.
    2.   Navigate to: Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Excel\options.
    3.   On the Edit menu, point to New, and then click DWORD Value.
    4.   Type ForceVBALoadFromSource, and then press Enter.
    5.   In the Details or Name pane, right-click ForceVBALoadFromSource (that you’ve just added), and then click Modify.
    6.   In the Value data box, type 1, and then click OK.

    2 people found this answer helpful.
  2. darth pixel 6 Reputation points
    2021-10-12T06:57:27.527+00:00

    in my case the problem was deleting custom format

    stupidity of this issue is monumental

    seq

    • create custom format ie: tak;;; << try exactly this one (it will be created as t\ak;;;
    • use it on more than one cell
    • save the file - ok
    • select just one cell with new formatting
    • open formatting popup nd delete this new custom format
    • save - error

    it's 100% repeatable

    1 person found this answer helpful.
  3. RMT4160 61 Reputation points
    2023-06-11T03:25:53.8566667+00:00

    Still happening as of 06/10/2023. Excel use to be the best program to come out of microsoft and when they created this office 365 it became garbage. The following is a fix that worked for me and I can't explain how it worked:

    1. Left file open that I could not save.
    2. Opened new file and saved it as macro enabled excel file.
    3. Opened VB Project
    4. Exported all modules, forms, sheets to make sure I had a copy of them
      1. Also backed up VB code to UltraEdit.
    5. Dragged and dropped modules and forms into new workbook created in step 2. Can't drop sheets and it would not let me copy them to the new workbook.
    6. Saved newly created workbook
    7. Then the kind and merciful gods of microsoft allowed me to safe the original file. Go Figure.

    You could cut the heads of the people that developed this latest revision of excel off and they wouldn't be any dumber.

    1 person found this answer helpful.
  4. Steve Lipsman 30 Reputation points
    2024-01-05T19:16:25.2033333+00:00

    Fixing .xlsb/.xlsm Macro Files When Macros Stop Working-RESOLVED!

    1. Copy file to subfolder that is not a “Trusted Location”.
    2. Open file in Excel, without Enabling Content.
    3. Open VBA Editor, click into any line in the ThisWorkbook module, and then save the file from the VBA Editor, and then close the file.
    4. Copy the file back to where it was.
    5. Open file again to see if everything is now working.

    The above just worked for me multiple times, as I had the same frustration voiced by many others above with this random annoying error by Microsoft Excel. If I didn't know better, I'd think that Microsoft is trying to annoy so many rabid VBA developers with these annoying issues so that they switch to one of their other platforms. I hope I'm wrong about that.

    1 person found this answer helpful.
  5. Arnelo Sarmiento 5 Reputation points
    2024-01-20T01:48:15.1766667+00:00

    [SOLVED] Based on the procedure of @FEDERICO GALLERANI , Thank you.

    1. Create a backup copy of the file (from file explorer)
    2. Change file extension from .xlsm to .zip
    3. Open the .zip file and locate the file /xl/vbaProject.bin
    4. Remove this file
    5. Change the file extension back to .xlsm
    6. Your file will now work normally. You can already save any update you want in your file.
    1 person found this answer helpful.