Forum Discussion
Excel Macros disappear from xlsm file
Hi GeorgieAnne
thanks a lot for you answer. Just today I have sent out an all staff email, that in case of crash of Excel a restart of the computer has to happen immediately.
But anyway Excel is behaving strange in the last days (I am not really following up when there is an update in the background - e.g. I have realized just a few days ago that the appearance of linked excel files pop up window has been changed) and as mentioned we have never experienced such crashes before and it looks like it happens with xlsm files and not with xlsx. But I really hope that this is just a transitory period.
It would be interesting to know if such issues have popped up in case of other users more frequently these days or not
But for sure I will give a feedback in this chat
Cheers
Peter
Hi, thank you for Sharing the Excel Macro problem started in December Excel Version 2311. I have also struggled with it for almost a month. But I think I might have found a solution? well, Microsoft might have solved the problem:
On 5 Jan 2024, I uninstalled and reinstalled Office 365, and made sure Excel is updated to latest version 2312 (released on January 04) - https://learn.microsoft.com/en-us/officeupdates/current-channel
And since then, I haven't had Macro enabled Excel crashed and Macro disappeared.
I schedule update a couple of Macro Enabled Excel files every 30 mins, and since Friday, it still update fine.
Just want to share this with you guys.
Cheers
- colleen4898Feb 19, 2024Copper Contributor
JazzTea Can you advise if you are still issue free? We are experiencing the same issues on a daily basis. If this fix seems to work, I will get the upgrades done as soon as possible. We have over 60 users in macro enabled excel everyday.
- PeterNagyFeb 19, 2024Copper Contributor
Hi I just can confim that with the 32bit version everything was fine. I have reinstalled the 64 bit version just a few days ago, so I have no final conclusion on this
Cheers
Peter
- colleen4898Feb 19, 2024Copper Contributor
my apologies for my lack of knowledge. So much to learn. what are the dangers of going back to 32-bit? we have been 64 bit for so long
- PeterNagyJan 11, 2024Copper ContributorHi,
thanks for the info. We have update our office version as well two days ago. Since then we have not experienced the big crash. BUT when we are working with excel files with macros then we get a message like there is some problem with your excel.. (we get it in Hungarian due to that I do not know the exact words in English for this message and there is no error number). Then I try to save as the file and get the answer that are problems with saving the file and I get the information that the file can only be save with minimal function in an XLSB format ... and then I get the message that the file has been damaged seriously, excel has tried to save data and formulas, but it may happen that there is a data loss...
I such case what I can do that I go back to my daily backups and take the saved file from the last day and start the work again.
So the trouble goes on and we still start everyday with a fear when opening excel and asking ourselfs what will happen today.
It would be great if Microsoft would be a little more transparent of the processes happening in the background (OK it can happen that they also do not know the reasons...)
Cheers
Peter- MLoya168Jan 11, 2024Copper ContributorYep, this is the exact issue I'm experiencing still. Going back to an earlier backup is a workaround but it definitely hinders daily productivity. I too wish that Microsoft would at least acknowledge this issue.
- PeterNagyJan 11, 2024Copper ContributorHi,
everyone reading this issue, should take it seriously as we are experiencing today it in more cases... unfortunately our backup saving happens at 8 pm and all the work with macros after this disappeared (actually it is there but we can not use the file).
Anybody has experience how to read the VBAproject.bin file? (when you change the extension of your xlsm file to zip and you go to the xl library this file is there and I can see the work from yesterday evening, but this file has to be "Translated" to receive a usable output) The symptoms are the same as at the big crash, in the VBA manager you can see the name of your modules, but if you click on them the wording of the macros do not appear)
Thanks for the help in advance
Peter
- MLoya168Jan 08, 2024Copper ContributorPlease keep us all posted on this. While I'd like to believe that Msoft resolved this with the update, I'm hesitant to believe that.
- RBinNCFeb 09, 2024Copper Contributor
Unfortunately, they haven't and it soooo obviously related to one of the recent builds. I have Version 2401 Build 16.0.17231.20194 that just came out on 2-1-24. Been using this very simple macro for years and now the macro doesn't show up in the Macro list and when I run it from the Visual Basic button, I get:
And since MS has to know that their updates are not well QAed, why don't they automatically create a restore point before updating our computers? My fault for not turning off automatic updates, the updates need to season a couple of months before turning them loose on my computer.
- CO_Data_WranglerFeb 15, 2024Copper Contributor
RBinNC I encountered the same issue this morning.
Try this: open the VBA Developer window for the workbook and go to:
Tools --> References
and be sure the "AccessibilityCplAdmin 1.0 Type Library" is checked.For whatever reason, that seemed to clear up the error for me.
Hope it works for y'all, too.