Cannot execute CVTRES.exe

Could not write to output file 'xxx' - 'Could not execute CVTRES.EXE.', I have a problem. I install VS2010, but the problem remains. I also applied devnev -resetsettings, but in vain. How to solve this problem.

Thank you in advance

+4
source share
5 answers

I only encountered this problem after installing VS2010 on a VMware client image, where I need to debug messages. The error prevented me from creating any projects in C #, while C ++ projects worked fine.

The source of the problem was corrupted cvtres.exe.config . I just managed to check this file:

 C:\Windows\Microsoft.NET\Framework\v4.0.30319\cvtres.exe.config 

and found that it contains only a sequence of null bytes. After restoring the contents of the file from a well-known good system, everything was just starting to work fine. Here is what I now have in the file:

 <?xml version ="1.0"?> <configuration> <startup useLegacyV2RuntimeActivationPolicy="true"> <requiredRuntime safemode="true" imageVersion="v4.0.30319" version="v4.0.30319"/> <supportedRuntime version="v4.0" sku="client" /> </startup> </configuration> 

This answer is probably too late for you, but I am writing it just in case it helps someone else. Final remarks about my system configuration: Win7 64-bit, VS2010 (10.0.40219.1 SP1Rel), .NET Framework 4 (4.0.30319 SP1Rel).

+5
source

Again, just in case, this is useful for someone else ...

I ran into the same problem in Visual Studio 2013. A solution containing project A (a class library with simple code) and project B (another class library containing a bunch of resource files) A โ€‹โ€‹refers to B. exact error: Metadata failure while creating assembly -- Could not execute CVTRES.EXE for project B.

It turns out that A was for .NET 4.5, and project B was for .NET 2.0. Changing B to 4.5 also solved the problem. Visual Studio was probably looking for CVTRES.EXE in a non-existing 2.0 folder or something like that.

Update: Indeed, Visual Studio was looking for a file in the folder C:\Windows\Microsoft.NET\Framework\v2.0.50727 , and it was not there. Reinstalling the .NET Framework 3.5 (2.0 is no longer available for download) did not help. I copied the files from a collegiate machine, and everything worked out fine. I donโ€™t understand why this happened to me, and not to others in my department, we all have the same computer setup (Windows 7 Pro x64, VS 2013 Pro).

+2
source

CVTRES.exe usually complains when the .resx file resource is not associated. Perhaps additional ui language files, etc. Are a problem. Try compiling to exclude these files and see what happens.

0
source

I solved this problem

copied cvtres.exe from framework/v2.0.50727 to framework/v4.0.30319

I donโ€™t know why, but it works

0
source

In case someone encounters problems with cvtres.exe - in my case it was Anti-Virus that blocks the launch of the file.

0
source

All Articles