none
Excel 2010 macros does not work after updates 9.Dec.2014

    Question

  • After installation of several security/program updates that came yesterday, 9.Dec.2014, the command buttons in my Excel work sheets does not work anymore. However, I can run the macros manually in debug mode in VBA. I have tried enabling macros and ActiveX in the trust center, but no change.

    Wednesday, December 10, 2014 2:12 PM

Answers

  • Close Excel.

    Start Windows Explorer.

    Select your system drive (usually C:)

    Use the Search box to search for *.exd

    Delete all the files it finds.

    Start Excel again.

    (Thanks to Excel MVP RoryA for this tip!)


    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    • Proposed as answer by mega_IT Wednesday, December 10, 2014 7:31 PM
    • Marked as answer by George123345Moderator Monday, December 22, 2014 6:58 AM
    Wednesday, December 10, 2014 2:29 PM

All replies

  • Close Excel.

    Start Windows Explorer.

    Select your system drive (usually C:)

    Use the Search box to search for *.exd

    Delete all the files it finds.

    Start Excel again.

    (Thanks to Excel MVP RoryA for this tip!)


    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    • Proposed as answer by mega_IT Wednesday, December 10, 2014 7:31 PM
    • Marked as answer by George123345Moderator Monday, December 22, 2014 6:58 AM
    Wednesday, December 10, 2014 2:29 PM
  • Hi

    Thanks for posting the question. I am experiencing the same issue on my PC with Excel 2010. 

    I tried inserting an ActiveX control on a new workbook and still getting the same error message "cannot insert object". 

    I tried Hans Vogelaar's solution but it did not work.

    Thanks

    Fowmy



    • Edited by Fowmy Wednesday, December 10, 2014 3:27 PM
    Wednesday, December 10, 2014 3:25 PM
  • After installation of several security/program updates that came yesterday, 9.Dec.2014, the command buttons in my Excel work sheets does not work anymore. However, I can run the macros manually in debug mode in VBA. I have tried enabling macros and ActiveX in the trust center, but no change.

    I experience the same problem with Excel 2007 and Word 2007.

    To be more precise, I cannot insert ActiveX Controls (for instance a Command Button) on a worksheet (Excel) or a page (Word), but it works as previously in PowerPoint and when inserting in a user form created in the Visual Basic Editor. Furthermore, no code is executed clicking on Controls inserted on a worksheet or page in a previously created file. When running code referencing such a Control I get a run time error.

    The error message shown when inserting a Control in Excel 2007 is: "Cannot insert object".

    The error message shown when inserting a Control in Word 2007 is: "The program used to create this object is Forms. That program is not installed on your computer. To edit this object, you must install a program that can open the object."

    EDIT:
    Renaming the MSForms.exd in the following locations solved the problem.

    • C:\Users\[user name]\AppData\Local\Temp\Word8.0
    • C:\Users\[user name]\AppData\Local\Temp\Excel8.0

    New MSForms.exd files were automatically created when restarting the applications.

    Thank you Hans Vogelaar for the solution.

    • Edited by Björn_x Wednesday, December 10, 2014 5:38 PM Solution found
    Wednesday, December 10, 2014 5:25 PM
  • Hello Fowmy,

    That appears to be a slightly different problem.

    • Do you have 32-bit or 64-bit Office 2010?
    • Which ActiveX control did you try to insert? Not all ActiveX controls can be inserted on a worksheet.

    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    Wednesday, December 10, 2014 5:28 PM
  • Same problem in Excel 2010.  In addition, in design mode I can select a button that was already there but the button's properties do not show up on a property sheet. In fact there are no property sheets listed for any of the buttons on the ss.  Same workbook runs properly in Excel2013, and it ran properly in 2010 until today.

    EDIT: Thanks Hans, deleting the .exd files solved the problem. 

    • Edited by JerryBrier Wednesday, December 10, 2014 11:22 PM
    Wednesday, December 10, 2014 5:34 PM
  • Have you tried removing all .exd files?

    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    • Proposed as answer by Yoda5152 Tuesday, January 06, 2015 11:40 PM
    Wednesday, December 10, 2014 5:41 PM
  • I have the same problem. Our office has a series of Excel documents with ActiveX controls with VBA macros and none of them are functioning. I can't even create a new Excel doc and insert a simple ActiveX control button as of today. This is ridiculous. F'n crap. Our office is non-functional right now.

    Wednesday, December 10, 2014 6:13 PM
  • Thanks Hans !

    It works perfectly !

    I have MS Office 2013 Professional (64 bit) and I got the issue with a file Excel 2010 in .xlsm !

    This solution fixed my problem easily !

    Thank you again !

    Eric

    Wednesday, December 10, 2014 6:56 PM
  • Thanks Hans.  I knew that the problem must have had to do with Patch Tuesday since all of the computers for one of my clients were affected, and one of our test computers, which had not been patched, was able to run the Excel 2010 VBA scripts in their files without a problem.  It was going to be a lot of removing of updates and testing until I ran upon your solution.  My client has returned from panic to peace.  Thanks again.
    Wednesday, December 10, 2014 8:07 PM
  • Hans: Your solution works Perfectly. Thank you so much.

    jmkester@live.com


    Thursday, December 11, 2014 2:19 AM
  • has anyone been able to identify which update was the culprit?
    Thursday, December 11, 2014 3:32 AM
  • thanks hans.

    its ok!

    Thursday, December 11, 2014 3:44 AM
  • Hans,

    I've just run the automatic updates supplied by Microsoft.  This created the same issue that we are discussing.  I've tried removing all of the .exd files (technically they are in the recycle bin) with no effect.  I cannot click an ActiveX button nor can I add a new button.  Have you any other suggestions?

    Thanks, Don

    Thursday, December 11, 2014 3:59 AM
  • I think that may be Microsoft update Office bug, I also have same problem for Excel2010 VBA. The problem be solved after deleted file named MSForms.exd on path C:\Users\[user name]\AppData\Local\Temp\Excel8.0
    Thursday, December 11, 2014 5:25 AM
  • I have the same problem at one of our clients. The work around as suggested by Hans works on half of the PC's on the other ones the problem persits.

    I will try to find differences between the systems.

    Any other suggestions except deleting the .exd files?

    Thursday, December 11, 2014 7:03 AM
  • If removing .exd files doesn't work, you could try a system restore to before the updates released on December 9, 2014 were released.

    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    Thursday, December 11, 2014 7:21 AM
  • Hi, Hans Vogelaar

    I'm experiencing a similar problem in Excel 2013 but I can't find any .exd file in my computer.

    Is there any other solution except system restore.


    Thursday, December 11, 2014 7:42 AM
  • Thanks for your prompt reply, system restore to a point before the update dit not help unfortunately.

    If it is an .xlsb nothing happens when i run a macro.

    If it is an .xlsm and i make a simple macro that just show a hidden tab (sheets("").visible=true) I get error 57121. 

    It works on system A (after deleting .exd files).

    It does not work on System B (after deleting .exd files and system restore).

    Both systems are windows 7 pro with Office 2010.

    Any suggestions?

    • Proposed as answer by Steven YSong Thursday, December 11, 2014 8:50 AM
    • Unproposed as answer by Steven YSong Thursday, December 11, 2014 8:50 AM
    • Proposed as answer by pootruck Thursday, December 11, 2014 12:59 PM
    • Unproposed as answer by pootruck Thursday, December 11, 2014 12:59 PM
    Thursday, December 11, 2014 8:03 AM
  • Same Problem here. Different problems on different PCs with same updates.

    I read in a Forum that a new Useraccount would help, but I did not have the time to test it yet. Any experiences?

    Did anyone contact MS?

    Edit:
    Deleting the *.exd files worked on some PCs here
    • Edited by Eldrior Thursday, December 11, 2014 9:26 AM
    Thursday, December 11, 2014 8:55 AM
  • Hi All,

    I have collected this information, and reported it with internal ways. If there are any updates, we will let you know.

    Thanks for you understanding.

    Regards,

    George Zhao
    TechNet Community Support


    It's recommended to download and install Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office programs.


    Thursday, December 11, 2014 9:02 AM
    Moderator
  • Han' s solution is worked for me.

    Thanks a lot, i' ve been searching for a solution for hours.

    Thursday, December 11, 2014 10:32 AM
  • Thanks Hans, it works.

    I have Office 2013 Professional (32 bit).

    Dave.


    Davide, Spinea IT

    Thursday, December 11, 2014 11:18 AM
  • I have the same issue here on all machines (12).

    Problem resolved by;-

    Renaming the MSForms.exd in the following locations solved the problem.
    • C:\Users\[user name]\AppData\Local\Temp\Word8.0
    • C:\Users\[user name]\AppData\Local\Temp\Excel8.0

    New MSForms.exd files were automatically created when restarting the applications.

    Thank you Hans Vogelaar for the solution.

    Thursday, December 11, 2014 11:44 AM
  • i can confirm that renaming MSForms.exd also worked for me.
    Thursday, December 11, 2014 12:00 PM
  • Try removing the update KB2596927.

    Close office programs.

    Control panel, Programs and features, View installed updates and search for KB2596927 then uninstall.

    Hope this helps

    Pat

    Thursday, December 11, 2014 1:01 PM
  • These are the problematic updates:

    • Security Update for Microsoft Office 2007 suites (KB2596927)
    • Security Update for Microsoft Office 2010 (KB2553154)
    • Security Update for Microsoft Office 2013 (KB2726958)

    Uninstall the relevant one and you will be fine. To avoid future re-installation it may be necessary to make changes in your Windows Update settings.

    • Proposed as answer by Pedro Wave Friday, December 12, 2014 5:24 PM
    Thursday, December 11, 2014 1:38 PM
  • We also had issue with Excel worksheets with VBA after the updates.  Getting error message "Object doesn't support this property or method.  We were able to get worksheets to work by 1. Logging in as a different user or 2. Removing the recent updates.

    We are going to try Hans suggestion of removing the .exd files from the problematic user profiles.

    Thursday, December 11, 2014 2:14 PM
  • yes after removing exd files all work fine
    Thursday, December 11, 2014 3:07 PM
  • Hans, Corporate WILL NOT allow us to do the system restore on the 125 computers in our office.  If you have pull with Microsoft, they need to fix this quickly!!

    Don

    Thursday, December 11, 2014 3:53 PM
  • Thanks! This worked great!! 

    How do I make changes in my Windows Update setting to prevent this from re-installing?

    Thursday, December 11, 2014 4:04 PM
  • Tommy,

    Thank you, this worked for me on my two machines.

    • Edited by derolp Thursday, December 11, 2014 4:07 PM
    Thursday, December 11, 2014 4:06 PM
  • Removing all .exd files from both my PC's worked. Search did not find any however so I had to manually goto C:\Users\[user name]\AppData\Local\Temp\Excel8.0 and C:\Users\[user name]\AppData\Local\Temp\VBE and found 3 files on one PC and only 1 file on the other. All is working fine now. You are a life saver!!!!!

    Thanks,

    Hans

    Thursday, December 11, 2014 4:10 PM
  • Hey Microsoft another excellent patch, 405 machines down across 5 countries  

    Thursday, December 11, 2014 4:15 PM
  • Thanks! This worked great!! 

    How do I make changes in my Windows Update setting to prevent this from re-installing?

    If you start Windows Update and let it search for updates, it should find the culprit. Depending on your Office version:

    • Security Update for Microsoft Office 2007 (KB2596927)
    • Security Update for Microsoft Office 2010 (KB2553154)
    • Security Update for Microsoft Office 2013 (KB2726958)

    Right-click it and select the option to hide it.


    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    Thursday, December 11, 2014 4:18 PM
  • Great answer

    Macros under Excell 2007 now working fine

    Thursday, December 11, 2014 4:41 PM
  • Thanks for all the helpful information, here's my experience so far:

    Office 2007 on Win7 x64:

    - KB2596927 is installed, fixed it by removing all *.exd from the Temp folders.

    Office 2010 x32 on Win7 x64:

    - Erasing all *.exd files didn't work, had to uninstall KB2553154.

    Office 2013 x32 on Win8 x64:

    - Erasing all *.exd files didn't work, had to uninstall KB2726958.

    Office 2013 x64 on Win7 x64:

    - Machined updated on 12/11 and broke all the buttons.  Still looking for the culprit since the KB numbers are different from Office 32-bit.


    • Edited by L0c0 Thursday, December 11, 2014 5:04 PM
    Thursday, December 11, 2014 5:04 PM
  • Ok this fix does work by deleting the *.exd's, now how do i fix 100 computers????

    Steve Hughes

    Thursday, December 11, 2014 5:25 PM
  • Same problem for us, deleting exd files isn't working for everyone. 85 users without access to Active X macro functionality
    Thursday, December 11, 2014 6:00 PM
  • Absolutely spot on perfect! after 2hrs of searching the web finally someone who really knows what there talking about!

    After windows 7 auto update last night, my visual basics buttons would not respond, thanks so much for this, you were a great help, this fixed it instantly!!!

    Thursday, December 11, 2014 6:19 PM
  • Thanks, L0c0. May I add another setup to your list:

    Office 2010 x64 on Win7 x64

    KB2553154 is installed, fixed it by removing all *.exd from the Temp folders.

    However, I then actually removed the update and hid it as mentioned above, since I had noticed that the last (restart) phase of the update had claimed to do something like 29,000 registry updates and I was bothered about the sort of mess that might have made of the  registry.


    • Edited by John Ash Thursday, December 11, 2014 10:35 PM
    Thursday, December 11, 2014 10:22 PM
  • Same problem here. Solution works for me too!
    Thursday, December 11, 2014 10:30 PM
  • Hi I havent been able to fix it. 

    I have windows xp and office 2010

    Please Help

    Friday, December 12, 2014 12:24 AM
  • Thanks Hans - I have now set my WSUS up so that these updates are Approved for Removal and then gone around and manually removed the update where necessary so that staff needing to use these types of controls in Excel files can get on with their work.

    Windows 7:

    Start > Control Panel > Program and Features
    Link on the left side panel: View installed updates

    Look through the list of updates for the KB numbers - they are grouped by product i.e. Microsoft Office 2010
    Select the update: i.e. Security Update for Microsoft Office 2010 (KB2553154) 32-Bit Edition
    Click Uninstall at the top of that updates panel

    If you have all Office software closed out of prior to uninstalling the update you will find that you won't need to restart your computer.

    Cheers, Jeff

    Friday, December 12, 2014 1:00 AM
  • You are a genius. You should be working for Microsoft 

    Thanks a lot. 

    Friday, December 12, 2014 3:41 AM
  • What happens if you can't find any *exd files or indeed MSforms??
    Friday, December 12, 2014 9:19 AM
  • You do not have to uninstall updates anything.

    This is a link to bat file fixed ActiveX problems in Excel and Word

    In this file you can find this line:

    @del "C:\Documents and Settings\%USERNAME%\Application Data\Microsoft\Forms\*.exd" /s
    @del "C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Forms\*.exd" /s
    @del "C:\Users\%USERNAME%\AppData\Local\Temp\Excel8.0\*.exd" /s
    @del "C:\Users\%USERNAME%\AppData\Local\Temp\VBE\*.exd" /s 
    @del "C:\Users\%USERNAME%\AppData\Local\Temp\Word8.0\*.exd" /s

    I's safe to use with no admin rights

    Regards


    Oskar Shon, Office System MVP - www.VBATools.pl
    if Helpful; Answer when a problem solved

    Friday, December 12, 2014 9:21 AM
  • Thanks Oskar

    What do I need to do with these...?

    (Sorry I'm a bit of a novice).

    Thanks

    Friday, December 12, 2014 9:28 AM
  • Hi

    I had the same problem in Office2007 (win 2007)

    renaming files *.exd in that directories (...\Excel8.0 and ...\Word8.0 ) solved this problem

    Thanks Bjorn_x

    Regards Paul

    Friday, December 12, 2014 11:01 AM
  • Win XP. Office 2010 & IE8 (quite!)

    Most updates are not advised because this machine belongs to a Volunteer Organisation and many people (none young) use the machine and few meet normally. So any changes must be considered carefully. And paid for! (All contributions greatfully received)

    the lesson here is that searching for the *.exd files (on XP) needs three boxes ticked.

    1) Win Explorer - show hidden files

    2) Win Explorer Search - Search hidden files

    3) Win Explorer Search - Search sub folders

    none of which are obvious or set (to prevent inadvertant mess by naive users).

    FWIW the folders I needed, for each user on one machine, were:

    C:\Documents and Settings\(user)\Local Settings\Temp\Excel8.0

    C:\Documents and Settings\(user)\Local Settings\Temp\VBE

    Every installation (and there are several) is different. Such is the situation in volunteer organisations. Micro$oft hasn't been entirely helpfull this time!

    Friday, December 12, 2014 11:46 AM
  •  Hi,

    Deleting the exd filed did not work for me. Does anyone know the KB update number for Excel 2013 64 bit so I can delete the update?

    Thanks

    Friday, December 12, 2014 1:16 PM
  • As far as I know, it's update KB2910929.

    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    Friday, December 12, 2014 1:48 PM
  • The fixed worked for me on about 10 computers running 2007 professional plus and 2010 professional plus. Thanks so much! 

    How ever I have one computer that is still not functioning. Every time you run any ActiveX item in word the MSForms.exd file in the Word8.0 folder recreates its self. I cant find a way to stop this. I have tried uninstalling and switching from 2007 to 2010 back to 2007 with no results.

    If any one has any advice i would really appreciate it.

    Friday, December 12, 2014 2:59 PM
  • Thanks Hans Vogelaar for the solution. Worked like a charm. The question I have is why did the .exd files cause that odd problem?
    Friday, December 12, 2014 3:34 PM
  • Thanks for the info but I am the same problem with users of office 365 pro.

    Removing *.exd do not work and update on windows 8.1 are not showing any office update to install.

    Can anyone point me in the right direction please

    Neil

    Friday, December 12, 2014 3:58 PM
  • The title of this thread is wrong; macro's are unaffected. ActiveX controls are broken. Removal of the .exd files worked for me, see: http://excelmatters.com/2014/12/10/office-update-breaks-activex-controls/

    and also:

    http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2014/12/11/forms-controls-stop-working-after-december-2014-updates-.aspx

    Friday, December 12, 2014 4:19 PM
  • Thanks Hans Vogelaar for the solution. Worked like a charm. The question I have is why did the .exd files cause that odd problem?

    The .exd files are created automatically the first time an ActiveX control is used; they are some kind of cache. Apparently, the cached versions aren't compatible with the December 9, 2014 update. After deleting these files, the updated version of Excel creates a new, compatible version.

    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    Friday, December 12, 2014 4:22 PM
  • Thanks for the info but I am the same problem with users of office 365 pro.

    Removing *.exd do not work and update on windows 8.1 are not showing any office update to install.

    Can anyone point me in the right direction please

    Neil


    Alas, I don't know of a solution for Office 365.

    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    Friday, December 12, 2014 4:24 PM
  • I just noticed this issue on two of my machines.

    I fixed it on one earlier this morning by deleting the .exd, but minutes later, another of my users called to report the issue.  Deleting the .exd files did nothing.

    The other machine affected at the moment is my own.  While running tests, I found out that I no longer have the ability to press those buttons, even after deleting the .exd files.

    Thing is, it worked yesterday...and the last Windows Updates done on my machine ran on 11/24/2014.

    I also do not have any of the KB's mentioned in this thread.

    The systems we run are on Win7 x64 and we have Office 2007 Professional.

    Thanks in advance, guys!

    Friday, December 12, 2014 4:33 PM
  • Hello,

    For computers where after you delete the exd and the ActiveX button don't work anymore.

    First check if the hotfix below is installed.

      • Security Update for Microsoft Office 2007 suites (KB2596927)
      • Security Update for Microsoft Office 2010 (KB2553154)
      • Security Update for Microsoft Office 2013 (KB2726958)

    You can see it in Windows update installation History.

    In my case, the Hotfix installation KB2726958 was failed. I have installed it again, launch Excel and .... ActiveX button don't work more.

    I have deleted one more time the Exd file, launch excel and bang ! problem resolved.

    Now, thanks to Microsoft to found quickly a solution. We can't do it computer by computer ...

    Friday, December 12, 2014 5:20 PM
  • Thanks Tommy, it worked for me!
    Friday, December 12, 2014 5:28 PM
  • After removing Security update for Microsoft office 2010 (KB2553154), it works for me...i can insert, get the property for active x button.....Thanks Pedro
    Friday, December 12, 2014 6:20 PM
  • Help!! after removing the .exd files Active x controls worked on the development computer but that .xlsm file will not work on other computers that have not had the original update. Userform text boxes, sheets, activex controls cause debug mode since the object does not exisit. Any ideas
    Friday, December 12, 2014 7:44 PM
  • I'd uninstall the faulty update - see above for the KB numbers for different versions of Excel.

    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    Friday, December 12, 2014 8:05 PM
  • These numbers are the same for Office versions 32 and 64 bits in the next link.

    Microsoft Security Bulletin MS14-082 - Important

    Microsoft Office Suite and Other Software

    Component

    Maximum Security Impact

    Aggregate Severity Rating

    Updates Replaced

    Microsoft Office Suites and Components

    Microsoft Office 2007

    Microsoft Office 2007 Service Pack 3
    (2596927)

    Not applicable

    Remote Code Execution

    Important

    974234 in MS09-060

    Microsoft Office 2010

    Microsoft Office 2010 Service Pack 2 (32-bit editions)
    (2553154)

    Not applicable

    Remote Code Execution

    Important

    None

    Microsoft Office 2010 Service Pack 2 (64-bit editions)
    (2553154)

    Not applicable

    Remote Code Execution

    Important

    None

    Microsoft Office 2013 and Microsoft Office 2013 RT

    Microsoft Office 2013 (32-bit editions)
    (2726958)

    Not applicable

    Remote Code Execution

    Important

    None

    Microsoft Office 2013 Service Pack 1 (32-bit editions)
    (2726958)

    Not applicable

    Remote Code Execution

    Important

    None

    Microsoft Office 2013 (64-bit editions)
    (2726958)

    Not applicable

    Remote Code Execution

    Important

    None

    Microsoft Office 2013 Service Pack 1 (64-bit editions)
    (2726958)

    Not applicable

    Remote Code Execution

    Important

    None

    Microsoft Office 2013 RT [1]
    (2726958)

    Not applicable

    Remote Code Execution

    Important

    None

    Microsoft Office 2013 RT Service Pack 1 [1]
    (2726958)

    Not applicable

    Remote Code Execution

    Important

    None

    [1]This update is available via Windows Update.

    Saturday, December 13, 2014 9:54 AM
  • It worked for me. Thank you.
    Sunday, December 14, 2014 6:10 AM
  • The method to remove the .exd files did not work for me.

    I have installed  Excel 2010 and 2013 on the same computer

    which has been working without problems so far.

    There was no security update for Excel 2013 installed but only for Excel 2010.

    When I uninstalled the security update for Excel 2010, Excel 2013 now also works again.

    This issue was really a pain.

    Sunday, December 14, 2014 3:06 PM
  • This, finally, fixed the problem for me (on 3 computers):

    * Search & erasing all *.exd files then,

    * Office program or suite: REPAIR (seems to fully reinstall, have keys or account info ready)

    I have turned off all Office automatic updates... now...

    I understand this is not a viable solution for those managing many computers.


    Marcel Saucier (An old DOS guy since 1983...)


    Sunday, December 14, 2014 4:08 PM
  • I have a machine with Excel 2010 and has stopped automatic update since Nov 2015 so
    it could run excel files with active control perfectly.

    However I got some machines with Excel 2007 and they have been updated and failed for the active control. So I deleted the xsd files,  and it works ok for Excel 2007.

    But when I use the machines with Excel 2010 to open that file, there were some problems:

    1) Worksheets("MySheet") .Range will cause "Application-defined or object-defined error" for sheets with Active controls object

    2) When I tried to delete the Active controls object, the excel program will stop with the following error log:

    Faulting application name: EXCEL.EXE, version: 14.0.7128.5000, time stamp: 0x5398dfdc
    Faulting module name: VBE7.DLL, version: 7.0.16.28, time stamp: 0x506f83c8
    Exception code: 0xc0000005
    Fault offset: 0x002092a5
    Faulting process id: 0x276c
    Faulting application start time: 0x01d015b0cbbb2c97
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\EXCEL.EXE
    Faulting module path: C:\PROGRA~2\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL
    Report Id: 17c5f8be-81a4-11e4-abe9-50e549813088

    I have deleted all the xsd file for the machine with Excel 2010 but got no luck :/

    Monday, December 15, 2014 2:19 AM
  • Hi All,

    Update 2:

    Please see this blog, follow the methods and check if they are help.

    http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2014/12/13/forms-controls-stop-working-after-december-2014-updates-.aspx

    Regards,


    George Zhao
    TechNet Community Support


    It's recommended to download and install Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office programs.

    Monday, December 15, 2014 4:10 AM
    Moderator
  • If you need to distribute your Excel files, there is a way to rename the MSForms.exd files in VBA even when Excel is running, which can also fix the issue. I've posted the VBA snippet in the link below. Add the snippet to the spreadsheets you're distributing. Then they should be immune to the Microsoft update.


    • Edited by Yi Hu Tuesday, December 16, 2014 11:04 PM
    Tuesday, December 16, 2014 6:11 PM
  • Hi all,

    Microsoft has release the fix when Dec.19, please try it with below link:

    https://support.microsoft.com/kb/3025036/EN-US?wa=wsignin1.0

    Hope it's helpful.

    George Zhao
    TechNet Community Support


    It's recommended to download and install Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office programs.

    Monday, December 22, 2014 6:59 AM
    Moderator
  • Hello,

    what do I do when I have an excel saved with the new KB, but on my computer I don't have the new KB.

    I'm unable to install the new KB since I'm not the administrator and this won't be done by the IT department for some months?

    I can't use these exdel's anymore...

    Thanks,

    Wouter

    Tuesday, December 30, 2014 1:41 PM
  • This fixed a constant and time consuming problem for me.    Thanks a ton!
    Monday, January 05, 2015 9:52 PM
  • Thank you so much, the bat file worked for me. (Office 2013 32bit (365), win 7)
    Wednesday, January 07, 2015 3:55 PM
  • I have exactly the same issue; my computer works after the *.exd solution but any vba excelsheet that I edit is not working on other computers. Even editing just  a cell value triggers this problem. Also, if someone else logs into his account on my machine, the same issue is generated.

    Since I am working in a corporate envireonment, the proposed solution for me now is to REINSTALL WINDOWS completely. I do not want to do this, it fels like overkill and also costs a lot of time.

    Does anybody have a suggestion for this?

    Maarten

    Monday, January 12, 2015 11:20 AM
  • I have a machine with Excel 2010 and has stopped automatic update since Nov 2015 so
    it could run excel files with active control perfectly.

    However I got some machines with Excel 2007 and they have been updated and failed for the active control. So I deleted the xsd files,  and it works ok for Excel 2007.

    But when I use the machines with Excel 2010 to open that file, there were some problems:

    1) Worksheets("MySheet") .Range will cause "Application-defined or object-defined error" for sheets with Active controls object

    Hi, well we've got several machines with Seven 64 bits and Office 2010 32 bits and Seven 32 bits with Office 2010 32 bits. We experiment the same problem although we deleted all .exd on all machines after verified kb was install before of course. Primary i thought everything was good until one user imported data (with active X) from another workbook and error appear on a line like Worksheets("MySheet") .Range as you wrote. I tried to replace the name of the worksheet with the number in the workbook Worksheets(1) .Range for example and it was good until another line in the code provide an error whereas it ran well before... at this time i don't have the solution, i'll try to repair office, or desinstall / reinstall it

    Monday, January 12, 2015 2:13 PM
  • Hi guys, that what i did as i've got problem whereas our computers were up to date with the kb2553154 (Windows 7 32 and 64 bits - and office 32 bits), with .exd files deleted manually (i did it), and by the fact that errors appeared like "Worksheets("MySheet") .Range will cause "Application-defined or object-defined error" for sheets with Active controls object". Of course .exd files were delete before.

    I deleted the KB2553154, reboot, deleted the .exd files, didn't update with the kb2553154, same errors " Application-defined or object-defined error" for sheets with Active controls object.

    So i did the update kb2553154, no reboot, open a blank excel workbook, added an active X control, had the initial error, closed Excel, deleted .exd files, open a new workbook, added an active X control and didn't have initial error.

    So reopen the files where i've got errors ("Application-defined or object-defined error for sheets with Active controls object : Worksheets("MySheet") .Range ), and i didn't have errors anymore on my files.

    So for me the solution is, even if you deleted the .exd (of MS FixIt) after the KB2553154 update, to delete the update (KB2553154), reinstall it, and delete another time the .exd files, for your Xl files (with Active X controls) run correctly.

    Tuesday, January 13, 2015 2:23 PM
  • Thanks - worked perfectly, but why?

    What is exd?

    Why did it appear now?

    Will it affect other users?

    Tuesday, January 20, 2015 3:49 AM
  • When you first use an ActiveX control, Office creates a cached version of the control and stores it in a .exd file. This will speed up subsequent uses.

    However, Microsoft released an update in December 2014 that changed the behavior of ActiveX controls. The cached versions in the .exd files were no longer compatible with the new version, so they didn't work anymore.

    By deleting the .exd files, you force Office to create new ones that are compatible with the update.

    Sadly, your updated workbooks may not work for users that still have the old .exd files.


    Regards, Hans Vogelaar (http://www.eileenslounge.com)


    Tuesday, January 20, 2015 6:50 AM
  • Hi Hans,

    I was able to get your solution to work for one computer. Now I'm waiting to see if it works on a coworker's computer from a different office. I'm wondering though, I may end up having to step several people through the process, and I noticed that all the files in question are in the Temp folder. For simplicity's sake, would having them run disk cleanup with Temp files checked essentially end up doing the same thing?

    Thanks for all your help!


    • Edited by Lindsay999 Friday, January 23, 2015 3:08 PM
    Friday, January 23, 2015 2:26 PM
  • It's worth a try - why don't you experiment?

    Running a utility such as http://www.piriform.com/ccleaner may help too.


    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    Friday, January 23, 2015 2:40 PM
  • 'I would suggest using the folloiwng Macro under the Workbook_open method, the below functions will rename the original .exd file, so that a fresh .exd will be created automatically.

    'If the renamed one already exists the previos copy will be deleted. so that the application will be error free and Temp folder wont be filled with .exd files.


    Private Sub Workbook_Open()
     ' Delete the two .xsd files in (/VBE) and (/Excel8.0) Folders
        RemoveAndRenameMSFormsFiles
    End Sub

     

    Public Sub RemoveAndRenameMSFormsFiles()
    On Error Resume Next
      Const tempFileName As String = "MSForms - Copy.exd"
      Const msFormsFileName As String = "MSForms.exd"
      On Error Resume Next

      'Try to rename the C:\Users\[user.name]\AppData\Local\Temp\Excel8.0\MSForms.exd file
      RenameFile Environ("TEMP") & "\Excel8.0\" & msFormsFileName, Environ("TEMP") & "\Excel8.0\" & tempFileName
      'Try to rename the C:\Users\[user.name]\AppData\Local\Temp\VBE\MSForms.exd file
      RenameFile Environ("TEMP") & "\VBE\" & msFormsFileName, Environ("TEMP") & "\VBE\" & tempFileName
    End Sub

    Private Sub RenameFile(fromFilePath As String, toFilePath As String)
      If CheckFileExist(fromFilePath) Then
          DeleteFile toFilePath
          Name fromFilePath As toFilePath
      End If
    End Sub

    Private Function CheckFileExist(path As String) As Boolean
      CheckFileExist = (Dir(path) <> "")
    End Function

    Private Sub DeleteFile(path As String)
      If CheckFileExist(path) Then
          SetAttr path, vbNormal
          Kill path
      End If
    End Sub

     

    Tuesday, January 27, 2015 9:32 AM
  • All Win 7 and some Win XP workstations in my mix of 60 workstations were fixed with the deleting of the .exd file.  However there were some Win XP stations that were not being fixed.  I found that if I copyied a version of the mxforms.exd file from a station that WAS working to the station that WAS NOT working also fixed the problem on the stubborn fixes.  It seemed that in some cases an errant file was still being created.
    Tuesday, January 27, 2015 1:22 PM
  • Thanks for your advice..it works..
    Monday, February 02, 2015 5:24 PM
  • It worked for my problem with Excel 2010 VBA, but I have the same problem in Excel 2013 and this solution does not work. have you any other suggestions?
    Friday, February 27, 2015 6:03 PM
  • Among the monthly updates for March 2015 is a series of updates that should correct the problem. Use Windows Update to get them.

    The relevant updates are:

    Word 2007: http://support.microsoft.com/KB/2956109
    Excel 2007: http://support.microsoft.com/KB/2956103
    PowerPoint 2007: http://support.microsoft.com/KB/2899580
    Word 2010: http://support.microsoft.com/KB/2956139
    Excel 2010: http://support.microsoft.com/KB/2956142
    PowerPoint 2010: http://support.microsoft.com/KB/2920812
    Office 2013: http://support.microsoft.com/kb/2920754
    Word 2013: http://support.microsoft.com/KB/2956163
    PowerPoint 2013: http://support.microsoft.com/kb/2965206


    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    Tuesday, March 10, 2015 11:17 PM
  • I get reports from customers that this update broke their macros:

    Excel 2010: http://support.microsoft.com/KB/2956142

    Wednesday, March 11, 2015 5:59 AM
  • I've got users who run Microsoft Excel Home and Student 2010 on win 7 pro 64 bits who have got error 32809 with an excel file with activeX controls, this time.

    The KB2553154 is not installed on the computer and if i search it Windows update don't find it too... That's the starting point for my Customer.

    I run the FixIT to erase all .exd, test again, same error. The file i test was created on win 7 pro 32 bits and excel 2010 professionnal 32 bits (kb 2553154 installed on the computer and fixit ran too so OK for the .exd on the computer where the file with activeX was created)

    The error is on a simple line like worksheets("name_of").range("cell_of").value = "my_value" for example.

    On my firm i had to desinstall the kb2553154 to reinstall it and run the fixit another time because of only running the fixit didn't resolve the problem (win 7 pro 64 bits with office 2010 pro 32 bits), do you remember ? It was just at the beginning of the year !! With the security update kb2553154. 

    What can i say to my customers, this time : "guys it's time for some bucks to purchase office 2010 pro if you would run my files" ???? With an older version of my files, they didn't have the problem, if open it now, i've the same error : 32809 Impossible to compile the project, no references missing... I run the file on my computer (win 7 pro 32 bits excel 2010 pro 32 bits and the kb2553154) : no problem. I run the file on win 7 pro 64 bits and excel 2010 pro 32bits and the kb2956142 : no problem. I lose my Latin...

    Wednesday, March 25, 2015 3:08 PM
  • Hi Hans Vogelaar,

    On opening excel file containing ActiveX controls, '*.exd' file generated in TEMP folder.

    Do we need to delete this file every time, Because i am using Macro enable Excel file which has created in both 2010 and 2013 updates. Once i have deleted the file and again opening 2013 macro enable file, the '*.exd' file generated in the Temp folder, and after this if i tried opening 2010 Macro enable excel, it showing error message.

    Is there any permanent solution for this issue.

    Anoop

    Monday, May 11, 2015 5:29 AM
  • Make sure that both Excel 2010 and Excel 2013 are fully updated. It shouldn't be necessary to remove the .exd files after that.

    Regards, Hans Vogelaar (http://www.eileenslounge.com)

    Monday, May 11, 2015 2:03 PM
  • If you are in an enterprise environment and macros still do not work on client user profiles after all the updates are installed on machines, you can fix this issue by changing the Office 2010 GPO setting for Check ActiveX Objects to: Override IE kill bit list

    Office 2010 GPO > ADM > Microsoft Office 2010 > Security Settings > Trust Center > Check ActiveX objects: change to Override IE kill bit list

    Office 2010 GP Admin Templates
    https://www.microsoft.com/en-au/download/details.aspx?id=18968

    GP for Office 2010
    https://technet.microsoft.com/en-us/library/cc179176%28v=office.14%29.aspx#Administrative_templates

    http://blogs.technet.com/b/srd/archive/2008/02/06/the-kill_2d00_bit-faq_3a00_-part-1-of-3.aspx

    Regards,
    Adrian
    Friday, May 29, 2015 10:25 AM
  • We had the Problem in June 2015 on fresh installed complete patched new Computers...

    Our solution was to install in Office 2007 the following Update: mso2007-kb2984939-fullfile-x86-glb.exe

    Good Luck @ all and thanks to all People in this thread....

    Friday, June 12, 2015 9:40 AM
  • I tried to install the vb6 common dialog controls sp3 but they would not take.   I had to install and old VB6 application that was compiled with all the controls included in the build.  After that, excel would run the old macro's.  

    This issue has plagued me for months but this fixed it.  Finally.

    The clue was from another post that had me look under tools/references in the developer.  In there it could be seen that this control was missing.



    Friday, September 11, 2015 3:37 PM
  • Excellent! worked like magic for me.  I was using Excel 2007 and the macros and the links worked perfectly until i upgraded to 2010 and the macro links were simply not responding.

    But Voila, followed Hans suggestion step by step and bingo!

    Tuesday, April 05, 2016 9:27 AM