Home / error msb6006 mt.exe exited with code 31 Error msb6006 mt.exe exited with code 31 31/03/2021 I ran into this difficulty this particular day while moving a VS2008 solution to VS2010. The trouble occurred in either of the adhering to scenarios:Reconstruct SolutionClean followed by Build SolutionIf I did a 2nd Build after either of these, the problem did not show up. Using Google, all I really came up through was year-old blogs from Microsoft saying they are unable to recreate the trouble, or that it is resolved in a future release.You watching: Error msb6006 mt.exe exited with code 31The finest thing I found was here: Mikazo Tech Blog: Solve MT.exe Errors in Visual Studio 2010In the over short article it said that the problem is pertained to Manifest generation, and also that the solution is to turn off Manifests in settings under Linker-->Manifest. I do not need Manifests for this job, but I still wasn"t satisfied.I have actually resolved this, and also am ssuggest going to answer my very own question, bereason I haven"t found this certain error (code 31) on StackOvercirculation. visual-studio-2010 Share Improve this question Follow asked May 21 "13 at 22:43 paddypaddy 51.9k66 gold badges5151 silver badges9393 bronze badges 1 Add a comment | 11 Answers 11 Active Oldest Votes36Using procedure monitor and also dbgwatch I found msmpeng (Microsoft Security Essentials) was accessing the file, simply as soon as mt.exe wanted to have it solely. Excluding the breakthrough directory addressed the difficulty.It is still a workroughly of course.See more: Fix Nvidia Geforce Experience Runtime Error Fix, C++ Runtime Error When Trying To Upd Share Improve this answer Follow edited May 29 "13 at 13:08 Pankrates 2,91511 gold badge1919 silver badges2727 bronze badges answered May 29 "13 at 12:46 user1839019user1839019 48633 silver badges22 bronze badges 5 Add a comment | 37WARNING: This specific error deserve to additionally take place as an outcome of having actually a Windows Explorer home window open up in the folder containing the *.exe which you are currently attempting to construct. For example: Explorer open up in /.../MyProj/Debug/ while trying to build the Debug version of your code in Visual Studio. I was angry through myself for ~10min before realizing this. Share Improve this answer Follow edited Sep 4 "15 at 15:13 answered Feb 1 "15 at 2:48 bunkerdivebunkerdive 1,78211 gold badge2222 silver badges2525 bronze badges 2 Add a comment | 6In my jobs, the Intermediate and Output directories were collection to:Intermediate Dir : $(Configuration)Output Dir : $(SolutionDir)bin$(Configuration)Under C/C++-->Output Files, I had the following:ASM List Location : $(IntDir)Object File Name : $(IntDir)Program Database Documents Name : $(OutDir)$(TargetName).pdbUnder Linker-->Manifest File, I had:Manifest Data : $(IntDir)$(TargetName)$(TargetExt).intermediate.manifestThe cure wregarding remove the trailing from my C/C++-->Output Files section (because it"s already part of those variables):ASM List Location : $(IntDir)Object Documents Name : $(IntDir)Program Database Documents Name : $(OutDir)$(TargetName).pdbGenerally, the double-up of making use of $(IntDir) or $(OutDir) with a trailing doesn"t seem to cause trouble, even though it"s bad practice. I can not remember currently whether I did it by accident or if the convariation process did it, yet for whatever before reason, it seems to have actually been messing up MT.exe.See more: Fix: Error 18 Spotify Windows 10, Fixed: Spotify Error Code 18 Windows 10I hope this is useful to anyone else who encounters this problem. Your settings may well be various, yet think about that it may be pertained to imcorrectly developed filenames.