Download ID=33186 you can read about it here: Studio/feedback/details/595632/inconsistent-hanging-with-devenv-2010 As pointed out in the comments here, for VS2017 you will need to create the DWORD HKEY_CURRENT_USER\Software\Microsoft\Visual Studio.0_[IDKey]_Config\MSBuild\Enable Out Of Proc Build Replace [IDKey] with the ID suffix of the existing 15.0 subkey of Visual Studio.For example, if under Visual Studio you see the key "15.0_abcd1234" it would be "15.0_abcd1234_Config".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.Long story short: it's a known issue, it won't be solved, and Microsoft advices to move away from Visual Studio Setup projects (.vdproj).
To update the private registry you can use Regedit. Now the registry structure will appear and you can navigate down to the Microsoft\Visual Studio.0_Config\MSBuild Create a new DWORD Enable Out Of Proc Build with a value of 0.To belabor the obvious: IP addresses are 32 bit values written as four numbers (the individual bytes of the IP address) separated by dots (periods).Each of the four numbers has a valid range of 0 to 255.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.