All of a sudden Excel's macros are no longer working in some Excel sheets.

I have been able to find the culprit update: KB2553154

From: http://stackoverflow.com/questions/27411399/microsoft-excel-activex-controls-disabled

 fix is to simply delete the file MSForms.exd from any Temp subfolder in the user's profile. For instance:

C:\Users\[user.name]\AppData\Local\Temp\Excel8.0\MSForms.exd

C:\Users\[user.name]\AppData\Local\Temp\VBE\MSForms.exd

C:\Users\[user.name]\AppData\Local\Temp\Word8.0\MSForms.exd

On the other hand i have  a user that has the issue but th eupdate is not there, i have uninstalled Office 2010 and installed 2013 but Macros are blocked

Have this pesky problem here in our office, 1 machine is a 2007 the rest are 2013. Disabled the update on the 2007 machine yesterday, Macros started working. today there not. Looked for the .exd files, non on this machine. looked for the .exd files on the other 2013 machines, found them, deleted them. macros still not working.

JZ

Deleting the .exd files did not work for us either. Haven't seen anything much other than an InfoWorld article.  Would be good to hear from MS whether this is handled.

http://www.infoworld.com/article/2858280/microsoft-windows/botch-brigade-kb-2553154-2726958-clobber-excel-activex-kb-3011970-silverlight-kb-3004394-root-cert.html

Hi,

We have realized this issue since the recent update, we have reported this problem and will keep you updated once there's any progress.

Regards,

Microsoft documented the workaround:

https://support.microsoft.com/kb/3025036

There is a way to rename the *.exd files in VBA even when Excel is running, which can also fix the issue. I've posted the VBA snippet on my website. Developers can add the snippet to the spreadsheets they're distributing, and their spreadsheets should be immune to the Microsoft patches. It's not an elegant solution, but it works for now.

• Edited by Yi Hu Tuesday, December 16, 2014 11:05 PM

Have you tried all the locations?

There is this script available here: https://onedrive.live.com/?cid=9170ff37ce80e88a&id=9170FF37CE80E88A%212885&ithint=file,bat&authkey=!AE0wp5AQ0T5sqbo

There is a way to rename the *.exd files in VBA even when Excel is running, which can also fix the issue. I've posted the VBA snippet on my website. Developers can add the snippet to the spreadsheets they're distributing, and their spreadsheets should be immune to the Microsoft patches. It's not an elegant solution, but it works for now.

• Edited by Yi Hu Tuesday, December 16, 2014 11:05 PM

Tried all of those, removed not only the *exd files but the folders as well.  No dice.  The problem still exists.

It also appears that Office 365 installed on a clean machine with no prior Office installed is unaffected, but Office 365 on a machine with a prior version IS affected. 

Please be aware that any Excel Macro enabled workbook you save or create after you have install the patch will be incompatible or not work with installations without the patch.

Tried all of those, removed not only the *exd files but the folders as well.  No dice.  The problem still exists.

It also appears that Office 365 installed on a clean machine with no prior Office installed is unaffected, but Office 365 on a machine with a prior version IS affected.&n

• Proposed as answer by BBB-BuddhasBellyButton Thursday, March 12, 2015 8:20 AM
• Edited by BBB-BuddhasBellyButton Thursday, March 12, 2015 8:30 AM

Dear Microsoft,

I work for a company with 21.000 users.

Alot of these users are experiencing this problem with their Excel macro's.

Microsoft cannot rollout a patch which kills Excel functions, and get away with a fix that does not work in most cases I have encountered.

Microsoft screws things up and we are left with a fix (which does not work in many cases) we have to apply to 200+ business workstations? We are not in the business of cleaning up after Microsoft dumped crap on our floor.

Microsoft has to come with a proper patch to resolve this problem for all users, or at least provide us with clues on where to check for if the Fix-it does not work.

If these Macros do not work on a specific laptop, it does not work for all users on this specific laptop.

Even users who will logon for the first time on such a laptop will have the same problem. These laptop users have no roaming profiles, so a totally new profile is created at logon without any EXD files in it.

We also see this problem on newly installed workstations with KB2553154 installed, so Excel is never even used and there is no trace of any EXD files on these workstations. How does MS explain that?

Please get your act together and come up with a proper solution without silly fix-it's.

For now we have to uninstall KB2553154 as a workaround.

• Edited by Daytona12 20 hours 12 minutes ago

Dear Microsoft,

I work for a company with 21.000 users.

Alot of these users are experiencing this problem with their Excel macro's.

Microsoft cannot rollout a patch which kills Excel functions, and get away with a fix that does not work in most cases I have encountered.

Microsoft screws things up and we are left with a fix (which does not work in many cases) we have to apply to 200+ business workstations? We are not in the business of cleaning up after Microsoft dumped crap on our floor.

Microsoft has to come with a proper patch to resolve this problem for all users, or at least provide us with clues on where to check for if the Fix-it does not work.

If these Macros do not work on a specific laptop, it does not work for all users on this specific laptop.

Even users who will logon for the first time on such a laptop will have the same problem. These laptop users have no roaming profiles, so a totally new profile is created at logon without any EXD files in it.

We also see this problem on newly installed workstations with KB2553154 installed, so Excel is never even used and there is no trace of any EXD files on these workstations. How does MS explain that?

Please get your act together and come up with a proper solution without silly fix-it's.

For now we have to uninstall KB2553154 as a workaround.

• Edited by Daytona12 Friday, May 29, 2015 11:16 AM