Excel macro vba problems after office 365 upgrade

Question

After upgrading to office 365, excel started giving me problems. I have this happening on a couple different workbooks that I’ve use for a couple years without issue until now, and the following things i’ve noticed are happening to each of the workbooks. For example on Sheet1… I have some data on the worksheet and a couple active x buttons. The code for the active x buttons is on the Sheet1 worksheet object. After the upgrade, the active x buttons stop working so i open vba and see that Sheet1 is now actually named Sheet11 and there is a new workbook that appeared called Sheet1. On one workbook, it renamed Sheet3 as Sheet31 and a new workbook called Sheet3 has appeared. Any ideas whats going on? This picture shows a the messed up example on top and a functional one on bottom.

Another messed up example…

Answer 1

Hi John ,

I'm Mukesh and I will be happy to help you out with your question.

This issue has been reported by many users that the July update is breaking Macro in Excel. The workaround for now is to uninstall the recent update .

Fixes or workarounds for recent issues in Excel for Windows https://support.microsoft.com/en-us/office/fixes-or-workarounds-for-recent-issues-in-excel-for-windows-49d932ce-0240-49cf-94df-1587d9d97093

Until we get a official fix avoid updating the office apps.

I hope this information helps. If you have any questions please let me know and I will be glad to help you out.

Help the next person who has this issue by indicating if this reply solved your problem. Click Yes or No below.

Best regards
Mukesh

Answer 2

That might be helpful to someone who hasnt done the upgrade or is experiencing the issue on a personal computer. Unfortunately for me, the updates have already been done and this is a work computer. I dont have the option of rolling back these updates and i have no way of knowing if they will choose to install the next updates or when. So is there a way to fix the macros that got messed up? Or to prevent the problem from happening? Or if i create a new workbook using O365 and just copy and paste everything from my old workbook, would that work?

Answer 3

Hi

Thank you for posting your query. My name is Clarence, I'll be more than happy to assist you with your concern.

To resolve your query kindly do the steps below.

Open the start menu and type “reg” and select the “Registry Editor”

Navigate to: Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Excel\options

On the Edit menu, point to New, and then click DWORD Value.

Type ForceVBALoadFromSource, and then press Enter.

In the Details pane, right-click ForceVBALoadFromSource, and then click Modify.

In the Value data box, type 1, and then click OK.

Go to this link for your reference and other troubleshooting procedures https://stackoverflow.com/questions/69018012/vba-workbooks-stop-working-with-upgrade-to-excel-365-vba-compiling-issue

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.'

Do not hesitate to message us if you need further assistance.

Give back to the Community. Help the next person who has this issue by indicating if this reply solved your problem. Click Yes or No below.

Best Regards,
Clarence

Answer 4

CLARENCE0403 please do not instruct an end user to go mess around the Registry on a work computer (they likely wouldn't have access anyway).

Instead direct them to contact their company's IT Support and mention this Thread.

Sincerely,

An Incident Manager with 10+ years experience in IT Support.

Answer 5

I appreciate the concern and you are correct, we dont have rights to mess with the registry. The way i thought best to handle this was to submit an IT ticket and in the ticket I put a link to this forum post. This will allow them to see my post with a more detailed explanation of the problem, and consider the responses from all the fine folks on this forum in case they need any ideas for the fix. Ill post what they ended up doing to fix it as soon as they get to my ticket (hopefully in the next couple days).