'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Excel Macro Buttons Disabled After Office 365 Update
Question details
The user needs to restore functionality to Excel macro buttons that have become unclickable and resolve Visual Basic removal prompts following a recent software update.
- Product
- Microsoft Excel
- Device & OS
- not provided
- Scenario
- Attempting to use an existing macro-enabled workbook (.xlsm or .xlsb) immediately after installing a Microsoft 365 or Office update.
- Observed behavior
- Macro buttons are completely disabled, and Excel displays warning messages prompting the user to remove the Visual Basic code from the file.
Do not click 'Yes' to remove the Visual Basic code from your Excel files when prompted, as this will permanently delete your macros. Ensure you have created a backup copy of your workbook before attempting any fixes.
Report the Software Compatibility Bug to Microsoft
Since the macros functioned correctly prior to the update, this is likely a software bug introduced by the new Office 365 build rather than a VBA coding error.
Microsoft frequently releases updates that can inadvertently disrupt legacy features, such as ActiveX controls or VBA macros. Because this issue appeared immediately after an update, it requires an official patch from the Excel development team rather than a modification of your existing code.
Navigate to File > Account in Excel to note down your exact Office 365 build number. Also, identify your operating system version and the specific file format (.xlsm or .xlsb) you are using.
Take a screenshot or precisely copy the text of the Visual Basic removal message that Excel displays when you open the file or attempt to click a macro button.
Use the Help tab in the Excel ribbon or your Microsoft 365 admin center to reach out to Microsoft Support. Provide them with your build number and the exact error message so they can investigate the bug.
Seek Temporary Workarounds from the VBA Community
If you need an immediate workaround while waiting for Microsoft to patch the issue, consult advanced VBA developers on community forums.
Avoid Disruptive Office Updates with WPS Office
If sudden Microsoft 365 updates are breaking your workflow and disabling your essential spreadsheets, consider switching to WPS Office. It provides a highly stable environment that ensures your documents, spreadsheets, and presentations continue to work smoothly without unexpected feature deprecations.
Frequently Asked Questions
Why did my macro buttons suddenly stop working in Excel?
This typically occurs after a Microsoft Office update introduces compatibility issues or enforces stricter macro security policies by default, which can unexpectedly disable ActiveX controls or form buttons that previously functioned perfectly.
Should I let Excel remove the Visual Basic project if prompted?
No, unless you have a secure backup of the file. Allowing Excel to remove the Visual Basic project will permanently delete all your VBA code and macros from that specific workbook.
Can I roll back my Office 365 update to fix the macros?
Yes, reverting to a previous, stable build of Microsoft 365 using the Office Deployment Tool or command prompt can temporarily restore your macro button functionality until Microsoft releases an official patch for the bug.
