This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi
The last windows update batch contained update KB2553154 for office 32 bit.
This update breaks all COM and Active x controls in Excel (i.e. buttons, combo boxes etc.). Like many businesses we use Excel with these controls extensively and this update is crippling Excel for our users.
We have installed and uninstalled it on a number of machines both Windows 7 and Windows 8 and have proved this update is causing the issue.
PLEASE Microsoft withdraw or fix this update we can hardly go around all our pc's worldwide and manually uninstalling it.
Regards
A customer wondering if you test your updates before releasing them
A family of Microsoft spreadsheet software with tools for analyzing, charting, and communicating data.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Quit Excel.
Start Windows Explorer.
Select the system drive (usually C:).
Use the Search box to search for *.exd
Delete all found files.
(Thanks to Excel MVP RoryA for this tip)
I know that this is way beyond when you posted this but I was able to fix this problem by updating Microsoft Office to the latest service pack. Then installing excel2010-kb2956142-fullfile-x86-glb.exe for Office 2010 andexcel2013-kb2956145-fullfile-x86-glb.exe for Office 2013. Hope this might help out someone else out there trying to figure out this problem. Also this page has some information on fixes as well. https://support.microsoft.com/en-us/kb/3017349
Appreciate the question and the answer because we've been scrambling to figure out what happened this morning as well.
As suggested in the original question, will Microsoft issue a patch/fix for this in a coming update?
I'm sure they will fix it eventually, but as far as I know, the bug hasn't been acknowledged by Microsoft yet.
The problem extends to
And would also appear to extend to both x86 and x64 bit platforms.