{"id":29,"date":"2014-12-11T09:09:00","date_gmt":"2014-12-11T09:09:00","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=29"},"modified":"2024-10-01T15:00:28","modified_gmt":"2024-10-01T13:00:28","slug":"december-update-blocks-activexmacro-execution-in-excel-2013","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2014\/12\/11\/december-update-blocks-activexmacro-execution-in-excel-2013\/","title":{"rendered":"December Update blocks ActiveX\/Macro execution in Excel 2013"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2012\/07\/Office1.jpg\" alt=\"\" width=\"55\" height=\"60\" align=\"left\" \/>Microsoft has released some Security Updates on December Patch day (2014\/12\/09), also some critical patches (see Security Bulletin <a href=\"http:\/\/technet.microsoft.com\/en-us\/security\/ms14-082\" target=\"_blank\" rel=\"noopener\">MS14-082<\/a>) for Microsoft Office. It seems that security update <a href=\"https:\/\/web.archive.org\/web\/20150312002134\/http:\/\/support.microsoft.com:80\/KB\/2553154\" target=\"_blank\" rel=\"noopener\">KB2553154<\/a> for Microsoft Office 2010 causes serious issues. Some users are reporting, that ActiveX controls and macros fails in Excel 2013. Here a few insights and [hopefully] a cure.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/5f19e4aa020944d68c8dc3b3b01ec49c\" alt=\"\" width=\"1\" height=\"1\" \/>I stumbled uppon this problem browsing some user comments within my German article <a href=\"https:\/\/web.archive.org\/web\/20240101004134\/http:\/\/www.borncity.com\/blog\/2014\/12\/10\/microsoft-dezember-2014-patchday-nachlese\/\" target=\"_blank\" rel=\"noopener\">Microsoft Dezember 2014-Patchday-Nachlese<\/a>. Some reader wrotes, that since patch day Excel 2013 macros won't work anymore. Buttons to invoke macros wasn't functional anymore (he wrotes, that it affected protected sheets, but I guess, it affects all VBA macros using ActiveX controls).<\/p>\n<p>The user mentioned above was able to fix things using a system restore in Windows \u2013 but as an admin he had to troubleshoot 80 clients. So my proposal was, to uninstall the related updates addressed in Security Bulletin <a href=\"http:\/\/technet.microsoft.com\/en-us\/security\/ms14-082\" target=\"_blank\" rel=\"noopener\">MS14-082<\/a>, Security Bulletin <a href=\"http:\/\/technet.microsoft.com\/en-us\/security\/ms14-082\" target=\"_blank\" rel=\"noopener\">MS14-082<\/a> includes several patches:<\/p>\n<ul>\n<ul>\n<li>Security Update for Microsoft Office 2007 suites (<a href=\"https:\/\/web.archive.org\/web\/20150228181652\/http:\/\/support.microsoft.com:80\/kb\/2596927\" target=\"_blank\" rel=\"noopener\">KB2596927<\/a>)<\/li>\n<\/ul>\n<\/ul>\n<ul>\n<ul>\n<li>Security Update for Microsoft Office 2010 (<a href=\"https:\/\/web.archive.org\/web\/20150312002134\/http:\/\/support.microsoft.com:80\/KB\/2553154\" target=\"_blank\" rel=\"noopener\">KB2553154<\/a>)<\/li>\n<\/ul>\n<\/ul>\n<ul>\n<ul>\n<li>Security Update for Microsoft Office 2013 (<a href=\"https:\/\/web.archive.org\/web\/20150228161623\/http:\/\/support.microsoft.com:80\/kb\/2726958\" target=\"_blank\" rel=\"noopener\">KB2726958<\/a>)<\/li>\n<\/ul>\n<\/ul>\n<p>Uninstall of Update <a href=\"https:\/\/web.archive.org\/web\/20150312002134\/http:\/\/support.microsoft.com:80\/KB\/2553154\" target=\"_blank\" rel=\"noopener\">KB2553154<\/a> for Microsoft Office 2010 solved the macro problem. At this point I was prepared, to do a deeper web search.<\/p>\n<h3>Here comes a workaround<\/h3>\n<p>I noticed, that somebody has already <a href=\"https:\/\/web.archive.org\/web\/20170717024422\/http:\/\/www.techygeekshome.co.uk:80\/2014\/12\/windows-update-causes-activexvbscript.html\" target=\"_blank\" rel=\"noopener\">reported that issue<\/a>, but user comments indicates, that this issue was gone within a fresh user profile. Somebody tracked it down to the following workaround: Just search for file <em>MSForms.exd, <\/em>which shall be located in temporary folder<\/p>\n<p><em>C:\\Users\\user.name\\AppData\\Local\\Temp\\Excel8.0\\<\/em><\/p>\n<p>and delete <em>MSForms.exd<\/em>. The file should rebuild during next Excel 2013 launch, and all VBA macros should work (shall be able, to use ActiveX controls). I haven't tested it yet \u2013 maybe somebody, who has successfully used the workaround can drop a comment.<\/p>\n<h3>Update: Microsoft has released a\u00a0FixIt<\/h3>\n<p>Microsoft has published KB article 3025036\u00a0(\"Cannot insert object\" error in an ActiveX custom Office solution after you install the MS14-082 security update), that discusses this issue. This article also provides download links for\u00a0FixIt solutions. Just download the appropriate FixIt and execute the .exe program. Afterward Excel show work as estimated. Hope that helps.<\/p>\n<p><strong>Further links<br \/>\n<\/strong><a href=\"http:\/\/stackoverflow.com\/questions\/27411399\/microsoft-excel-activex-controls-disabled\" target=\"_blank\" rel=\"noopener\">A discussion at stackoverflow<\/a><br \/>\n<a href=\"http:\/\/answers.microsoft.com\/de-de\/office\/forum\/office_2013_release-excel\/fyi-dezember-update-kb2553154-kann-excel-2013\/8343010f-4274-4835-8c78-e125485ec8d1\">FYI: Dezember-Update KB2553154 kann Excel 2013 Makro-Ausf\u00fchrung blockieren<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft has released some Security Updates on December Patch day (2014\/12\/09), also some critical patches (see Security Bulletin MS14-082) for Microsoft Office. It seems that security update KB2553154 for Microsoft Office 2010 causes serious issues. Some users are reporting, that &hellip; <a href=\"https:\/\/borncity.com\/win\/2014\/12\/11\/december-update-blocks-activexmacro-execution-in-excel-2013\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[13,12,3,14],"class_list":["post-29","post","type-post","status-publish","format-standard","hentry","category-office","tag-excel","tag-office-2013","tag-patchday","tag-trouble"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/29","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=29"}],"version-history":[{"count":1,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/29\/revisions"}],"predecessor-version":[{"id":35065,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/29\/revisions\/35065"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=29"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=29"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=29"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}