Freigeben über

"Unspecified Automation Error" after applying MS12-060

  • Artikel

MS12-060 is a security update that was released Tuesday, August 14, 2012. This update replaced MS12-027. Some may be seeing "Unspecified Automation Error" when running your Microsoft Office VBA code after installing MS12-060.

Update: We have redeployed the MS12-060 update that contains the fix for this issue automatically built in.  The update is now available from the Microsoft download center.

These KB articles have been updated with mention of the workarounds, a fix it package and a link to download the new update.  You do not need to install the original update in order to install the new update:

2007
https://support.microsoft.com/KB/2687441

2010
https://support.microsoft.com/KB/2597986

Office Sustained Engineering Blog has been updated with a resolution.
https://blogs.technet.com/b/office_sustained_engineering/archive/2012/08/24/ms12-060-not-initiating-with-certain-controls.aspx

 

For more information on MS12-060, review the complete security bulletin:

Microsoft Security Bulletin MS12-060 - Critical
Vulnerability in Windows Common Controls Could Allow Remote Code Execution (2720573)
https://technet.microsoft.com/en-us/security/bulletin/MS12-060

Comments

  • Anonymous
    January 01, 2003
    A batch file that contains the following lines could make things easier by detecting the OS bitness and running the appropriate regsvr32 command: if exist %systemroot%SysWOW64cscript.exe goto 64 %systemroot%system32regsvr32 /u mscomctl.ocx %systemroot%system32regsvr32 mscomctl.ocx exit :64 %systemroot%sysWOW64regsvr32 /u mscomctl.ocx %systemroot%sysWOW64regsvr32 mscomctl.ocx exit To run the regsvr32 commands silently, add a “/s” to each of the above regsvr32 commands – i.e., %systemroot%system32regsvr32 /u mscomctl.ocx /s

  • Anonymous
    August 17, 2012
    The second command retrieves the following error popup. What am I supposed to do? [Window Title] RegSvr32 [Content] The module "C:WindowsSystem32MSCOMCTL.OCX" was loaded but the call to DllRegisterServer failed with error code 0x80004005. For more information about this problem, search online using the error code as a search term. [OK]

  • Anonymous
    August 18, 2012
    see this link (bottom portion related to the August 12th update) This batch file works if run in Administrator Mode. www.getfaxing.com/.../index.php

  • Anonymous
    August 23, 2012
    This link saved a lot of time and unnecessary frustration caused due to unknown errors.

  • Anonymous
    September 06, 2012
    I have been very frustrated trying to resolve this problem on my own. Thanks so much--your link saved time and sanity.

  • Anonymous
    September 09, 2012
    Thanks for this, saved us a lot of time. Our IT dept keep pushing out MS patches and crippling BIP!

  • Anonymous
    September 18, 2012
    Worked for me on a 64 system with Office 2007. I just wish one would not have to be so computer savvy to fix what Microsoft breaks.

  • Anonymous
    October 09, 2012
    Big thanks from my side. It really works.

  • Anonymous
    July 12, 2013
    Thank you so much... It worked.........

  • Anonymous
    July 15, 2013
    Confirmed, fixed a regression caused by a Windows 7 update to Word 2010. "Automation Error" is now gone after deleting the *.exd files as described by your link (getfaxing.com).

  • Anonymous
    August 28, 2013
    You're welcome. We still see this problem after 1 year! We created a batch/exe to fix the issue for our customers but we removed  last year after Microsoft finally released a fix for it.  I recommend deleting those EXD files first, and if you still have problems to go ahead with the Microsoft "FixIt" patches listed on our page.