Forum Discussion
Macros suddenly run much slower
I have the same problem.
I have a large spreadsheet with one macro that takes about 10 minutes to run. When I open the spreadsheet, Excel is using about 400MB of RAM. As the macro runs, the amount of RAM increases. When it's finished, Excel is using about 1,600MB of RAM. After that, every action is Excel spikes the CPU up to 100%.
Looks to me like a recent update introduced some sort of memory release issue.
https://support.microsoft.com/en-us/topic/how-to-revert-to-an-earlier-version-of-office-2bd5c457-a917-d57e-35a1-f709e3dda841
- Steve_PigsoftFeb 14, 2022Copper Contributor
Very many thanks for this recommendation (to work round the current version of Excel for Microsoft 365 (Win 10) that is currently very slow at running macros AND is also very slow to close after running macros, compared with previous Excel 365 versions):
ie. To roll back to an earlier version of Excel 365 – I am pretty sure a roll back to an earlier version would fix the problem for me too. However:
My current installed Microsoft Excel for Microsoft 365 is shown as
MSO Version 2201 Build 16.014827.20180 (32 bit).
As this is neither a version from Microsoft 365 Apps for enterprise nor Microsoft 365 Apps for business, I don’t think I am able to follow the path described via https://support.microsoft.com/en-us/topic/how-to-revert-to-an-earlier-version-of-office-2bd5c457-a917-d57e-35a1-f709e3dda841because - “This article doesn’t apply to MSI versions of Office.”
Is there an equivalent rollback procedure for MSO versions of Microsoft 365? I couldn’t find one.
Ideally, we all need a fix to the underlying problem with Excel 365's current macro-run-speeds as, even for those able to roll-back to earlier versions and with auto-update deselected, the roll-back fix is only a work-round and prevents ANY future updates to Office components? How do we ensure that this fault in the current releases of Excel is flagged to Microsoft for a fix in a later update release?
- Andrew__MaynardFeb 13, 2022Copper ContributorThis fix worked for me too