Visual Studio 2010 Macros Stop Working after February 2014 Windows Update

Installing recent February 11, 2014 Windows updates breaks Visual Studio 2010 macros functionality. Macros just don’t run any more without an error message. More specifically, it is MS14-009 update “Vulnerabilities in .NET Framework Could Allow Elevation of Privilege (2916607)” (rated as Important) breaks macros. And more specifically it is the Elevation of Privilege part of this update.

MS14-009 includes several updates for different OS and .NET versions. To restore Visual Studio 2010 macros functionality you need to uninstall the Elevation of Privilege patch specific for your machine. For example, on a Windows 8.1 machine you need to uninstall KB 2898871:

Uninstalling KB2898871 Windows Update

Uninstalling KB2898871 Windows Update

Windows update to uninstall to restore macros functionality in Visual Studio 2010
.NET 4.5.1 .NET 4.5 .NET 4
Windows 8.1 KB2898871
Windows 8 KB2898870 KB2898865
Windows 7 KB2898869 KB2898864 KB2898855
Windows XP KB2898855

The Visual Commander extension (a modern alternative to Visual Studio macros) is not affected by this Windows update.

Update (February 18): To restore Visual Studio 2010 macros functionality without removing Windows updates, you can add the AllowDComReflection configuration setting (published by Jens) to vsmsvr10.exe.config, vsaenv10.exe.config and devenv.exe.config files (note, you need to run your editor with admin rights for correct modification of these files):

        <AllowDComReflection enabled="true"/>

On a 64-bit Windows machine default paths to these files are:

"C:\Program Files (x86)\Common Files\Microsoft Shared\VSA\9.0\VsaEnv\vsmsvr10.exe.config"
"C:\Program Files (x86)\Common Files\Microsoft Shared\VSA\9.0\VsaEnv\vsaenv10.exe.config"
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe.config"

Each of these files already has the runtime section, you just need to add the <AllowDComReflection enabled="true"/> line:

Adding AllowDComReflection to vsmsvr10.exe.config

Adding AllowDComReflection to vsmsvr10.exe.config

To restore Visual Studio 2008 macros functionality, you need to add AllowDComReflection to the following files:

"C:\Program Files (x86)\Common Files\Microsoft Shared\VSA\9.0\VsaEnv\vsmsvr.exe.config"
"C:\Program Files (x86)\Common Files\Microsoft Shared\VSA\9.0\VsaEnv\vsaenv.exe.config"
"C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe.config"

Update (February 25): Microsoft published KB2934830 “Marshaling of reflection types may not work over DCOM after you install a security update from security bulletin MS14-009″. It acknowledges that macro functionality in Microsoft Visual Studio may not work as expected after installing MS14-009. As a workaround to restore the functionality of Visual Studio macros, the article suggests updating one of the following application configuration files, depending on the version of Visual Studio that is installed on the system:

Visual Studio 2010 c:\Program Files (x86)\Common Files\Microsoft Shared\VSA\9.0\VsaEnv\Vsmsvr10.exe.config
Visual Studio 2008 c:\Program Files (x86)\Common Files\Microsoft Shared\VSA\9.0\VsaEnv\Vsmsvr.exe.config
Visual Studio 2005 SP1 c:\Program Files (x86)\Common Files\Microsoft Shared\VSA\8.0\VsaEnv\Vsmsvr.exe.config

You need to add the AllowDComReflection configuration switch in the <runtime> section of an .exe.config file as follows:

 <?xml version ="1.0"?>
         <AllowDComReflection enabled="1"/>
This entry was posted in Visual Studio news and tagged , . Bookmark the permalink.

59 Responses to Visual Studio 2010 Macros Stop Working after February 2014 Windows Update

  1. Anonymous says:

    thx for help

  2. Anonymous says:

    Its true, same happened to me.
    Unistalling both KB2898869, KB2901126 solved the problem.

  3. Anonymous says:

    I’ve the same problem, but I’m (comprehensible) not allowed to uninstall security updates.
    So, is there a way to use macros anymore AND be protected against attacks?
    Both is desirable. I think…!

  4. Anonymous says:

    Uninstalled KB2898869. It’s working now.

  5. Anonymous says:

    Thank you very much. You’ve saved me a lot of frustration

  6. Anonymous says:

    Uninstalled KB2898855v2 and it’s working now too ! Thanks !

  7. chafferm says:

    Many thanks for your help.

    Unistalling both KB2898869, KB2901126 solved the problem.


  8. Anonymous says:

    thank you!

  9. Anonymous says:

    It also breaks VS 2013 Express for Desktop on Win 8.1

    • This is new to me. Can you please describe what is broken in VS 2013 Express now?

      • Anonymous says:

        You can’t even launch VS.
        It just show a message saying “Operation could not be completed. No such interface supported.”
        It also broke some of my wpf applications but, oddly enough, only some of them.

        After uninstalling KB2898871 it works again, so I have just hidden the update, so Windows doesn’t decide to re-apply it.
        Apparently it breaks more than it fixes. ;o)

  10. Ken Schenke says:

    This update also broke macros in VS 2008 on my 64-bit Windows 7 system. I had to uninstall KB2898857 to fix it.

  11. zhaojun meng says:

    This update broke macros in VS 2008 on may 64-bit Windows 7, too. Uninstall KB2898857 fixed it.

  12. Hermann Seib says:

    Would it be theoretically possible to extend Visual Commander so that it can also be used in VS.NET up to 2008?

  13. Tim Phoenix says:

    On my Win7-64bit, uninstalling KB2898869 launches “Update KB2858725 Uninstallation”, which fixed the problem. After reboot, it immediately offers the KB2898869 update again. Hide it so it won’t reinstall.
    After buying VS 2012, I’ve never used it due to the removal of macros; I’ve stuck with 2010. Then this happened.
    Christ, I get so tired of MS breaking my stuff!

    I’m going to give Visual Commander a try. Thanks for the help.

  14. Anonymous says:

    Thank you
    Uninstalling KB2898869 fixed this issue for me :-)

  15. Anonymous says:

    For VS 2008 on XP uninstalling KB2898856 worked for me.

  16. says:

    Removing KB2898869 on Win7 fixed the issue.

  17. Anonymous says:

    Cheers. You’ve saved me many hours. Good ol’ microsoft updates!

  18. Anonymous says:

    Thanks for this help. Win 7 64bit, ms office 2010. VS2010. I had to remove KB2898855 & KB2898855v2 Service pack 2 for Office 2010 and VS works again.

  19. Mark Beiley says:

    These updates also broke macros in VS2005. I uninstalled all of the updates from Feb 2014 (one of which was KB2898857) and macros started working again.

  20. Anonymous says:

    Thank you for your update about AllowDComReflection!

  21. Lenny Chen says:

    Modifying the config files really save the day!

  22. Jose says:

    Thanks !!!!
    Worked for me just modifying the first two .config files:
    “C:\Program Files (x86)\Common Files\Microsoft Shared\VSA\9.0\VsaEnv\vsmsvr10.exe.config”
    “C:\Program Files (x86)\Common Files\Microsoft Shared\VSA\9.0\VsaEnv\vsaenv10.exe.config”

  23. Anonymous says:

    Thanks. The XML edit did the trick.

  24. Anonymous says:

    Modifying the first two config files worked for me. Thanks for the post!

  25. BridgeSite says:

    Had the same problem with VS 2007 and Windows 7 64. Removal of KB2898857 fixed the nightmare. Is there a way to do this in VS 2007 with a config file?

  26. Anonymous says:

    Removing KB2898871 and adding to the config files don’t do trick on Wondows 8.1 Pro. Note, that VS2010 installed on the machine after windows update.

  27. Anonymous says:

    Excellent! I rely on my macros for a number of utility functions, I wasn’t relishing the though of having to re-code them as I read will be the case with VS2011

  28. Anonymous says:

    Thank you!!!

  29. Pingback: visual studio 10 에서 매크로 안먹힐때 | Tech Griffin

  30. Anonymous says:

    Config files fix (VS2010, Win7-64) worked for me too. Thanks!!!

  31. Aldo says:

    Thank you so much.
    I have changed all 3 files and my VS2005 now work

  32. gast128 says:

    I got the same problem. Many thx for posting this.

  33. Anonymous says:

    THANK YOU for the AllowDComReflection fix. So grateful!!!

  34. Anonymous says:

    Editing .config file according to “Update (25-FEB)” was only allowed with administrative rights on my windows 7 system.
    I’ve edited a copy of according config file in a different directory, and then moved the edited file back to original location.

  35. X says:

    The AllowDComReflection fix worked like a charm. Thank you!

  36. Anonymous says:

    Thx, this solved my problem.

  37. Mark Hurd says:

    I rewrote the content of the KB article to Stack Overflow acknowledging I first found your page via Google.

  38. Anonymous says:

    Awesome! Thanks!

  39. Jerry Walter says:

    This fixed my VS2005 issues with macros not running.

  40. Anonymous says:

    Thanks, Excellent….

  41. Anonymous says:

    Awesome!!! Thanks for the tip!

  42. Lelala says:

    THANK YOU, wow – i thought i have to reinstall, since i checked everything; i also changed the macro, since i thought it became buggy for some reason… :-D

  43. Mick says:

    Excellent. Yes some of us (who aren’t a fan of typing unnecessarily) do actually use visual studio macros

  44. Rubidium says:

    No solution seems to work for me :(
    I tried editing the config files as explained, both for VS2008 and VS2010 (I’m using 2010); I tried setting value to “true”, as per your instructions, and to “1″ as per KB2934830; I tried also to uninstall the only guilty update I found (KB2898869).
    Still not working.
    I did shut down VS before each attempt (and looked for it to be really not running, same for the two additional processes in C:\Program Files (x86)\Common Files\microsoft shared\VSA\9.0\VsaEnv: vsaenv10 and vsmsvr10), but not restarted the PC yet.
    Tried also to create a new test macro with a simple MsgBox in it and launching from custom toolbar: no success.

    I don’t understand what I am missing.
    Running VS 2010 SP1 on Windows 7 x64, both ITA language with Administrator user and UAC off.

    Anyone having some hint?

  45. Jairo Martinez Antonio says:

    Excellent, it works without uninstalling anything.

  46. Kris26 says:

    Thanks, this is solved my problem with out uninstalling any updates

  47. Anonymous says:

    Thank you! The config changes worked flawlessly! Much better than having to uninstall patches.

  48. Marc Bonet says:

    Adding fixed it….. thanks again!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s