We've worked around this issue by triggering the MSI build a second time when it fails a first time.Not nice, but it works most of the time (error rate is down from ~ 10% to ~ 1%). I had been scouring the internet to find why exactly it was happening, and ran across numerous Microsoft replies that were vague and unhelpful, to say the least.The problem was almost impossible to reproduce and unpredictable in its manner: The customers had several setup projects in their solution and the error appeared seemingly random during the compilation of each of them.

backdating job steve - An error occurred while validating hresult visual studio

Alternative Reason My problem had to do with Visual Studio versioning, however.

So, if your dependencies are valid and you still are getting this problem, then you resolve this if it is a problem with VS2010 .

I have been receiving this error for a while when using devenv on an automatic build.

I have gone through every website I can find, and the usual answers mention refreshing dependencies (Which I believe fixes it for manual deployment, but not for automatic) and removing the source control coding from the projects, which hasn't helped me.

I fixed it on my build-machines by using some Dev Env command line wrapper with a call to this batch file. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?And it came on even if I set all projects to be build in a current configuration and the setup project not to.The problem with the issue is that it is a race condition.I opened the Solver for Build Servers On the other hand this works for a current user account which launches this (because of HKEY_CURRENT_USER).But build-servers often use other accounts (Local System and so on).This is a known issue in Visual Studio 2010 (a race condition). We've ran into this as well, and had a very unsatisfying support call on this issue with Microsoft.