Solution: An error occurred while validating. HRESULT = '8000000A'

If you face the error message “An error occurred while validating. HRESULT = '8000000A'” while building Visual Studio setup project from command line in Visual Studio 2012 or above IDE environment, the reason is because the new IDEs do not support build outside the own process.


But there is a tweak which will help you to enable the same and you will now be allowed to build the MSI setup project from the command line itself.


Solution: An error occurred while validating. HRESULT = '8000000A' (


The solution towards “An error occurred while validating. HRESULT = '8000000A'” error message is very simple. It’s just a registry tweak that you have to perform as a workaround.


For this to work, open your Windows Registry with administrative privilege and navigate to the following registry key path: “HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\11.0_Config\MSBuild” for Visual Studio 2012 IDE or, to the registry path “HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\12.0_Config\MSBuild” for the Visual Studio 2013. If you are using Visual Studio 2015, then the registry key that you have to navigate to is “HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0_Config\MSBuild”.


Registry entry to enable out of proc build in Visual Studio (


In that path, create a DWORD key with the name “EnableOutOfProcBuild” and set it’s value to “0” (zero). Now restart the build process from the command line and everything will be working as you expected.


Hope this small Tips & Tricks was helpful. Do let me know, if this helped you. Stay tuned to my blog for new articles, tips. Don’t forget to read my other posts by the time I write and publish a new post. Have a great day ahead!



If you have come this far, it means that you liked what you are reading. Why not reach little more and connect with me directly on Twitter, Facebook, Google+ and LinkedIn. I would love to hear your thoughts and opinions on my articles directly. Also, don't forget to share your views and/or feedback in the comment section below.


  1. Hi Kunal,
    I am creating a build using TFS 2015 in which I want to create .msi using a command. After changing the registry key, it works in direct command but it still does not work through the TFS build.
    Subodh Sohoni

    1. Hello Subodh sir,

      Not sure about this. Might be, you have to check in TFS build configuration. Are you getting any error? Could you please share me the error message? Then I can investigate it.

      Kind Regards,
      Kunal Chowdhury

  2. Hi Kunal,

    I hat exact the same issue here. But now this setting disappear in random intervals! I have to set this setting again and everythings works again. Did you have maybe the same Problem? What could be reason for this effect? Why are the registry settings disappear?

    1. Hi Pow-Lee,

      This might be due to system policy which is resetting your registry changes. Please contact your system administrator to resolve this issue.


  3. You also need to run the TFS/TeamCity build service as an administrator. Then your problems will go away :)

  4. It worked for me .Thanks Kunal

  5. It works!!! Thanks a Lot Kunal

  6. Hi Kunal,

    Would you happen to know what the solution is for Visual Studio 2017? Based on the information provided here,, it looks like the solution you provided will no longer work. Any ideas on how to solve this?

    1. As a followup, I believe I've found a working solution by editing the private registry in the user AppData. I can imagine this will break with updates to visual studio and the same fix will need to be applied but following the steps to edit the registry that I found detailed here: - Starting at..."Instead, the VS 2017 private registry is stored in your AppData folder:". This section details how to find and edit the private registry.

      Adding EnableOutOfProcBuild as a registry value allows installer projects to build via command line as detailed in this original post. Whether this solution is a good long term one will remain to be seen but this works right now.

    2. Further information that I've found, it looks like you can create the config registry value without editing the visual studio private registry. This may be a safer, long term answer:

      From Microsoft Rep in the comments -

      To create the EnableOutOfProc setting for MSBuild you need to create a new Key with the same Id as the current 15.0_[your-ID] key with the _Config suffix.

      Ex: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\5.0_[IDKey]_Config\MSBuild\EnableOutOfProcBuild

      I haven't tried this yet but I suspect it also works.

    3. Yes, I believe that too will work but I have yet to check this.


© 2008-2017 - Microsoft Technology Blog for developers and consumers | Designed by Kunal Chowdhury
Back to top