<p>When i include Visual leak detector and build the source code than it is unable to register the dll on XP and on Windows 7, regsvr32.exe crashes.</p>
<p>Environment : VS2008 , OS is XP </p>
<p>error PRJ0050: Failed to register output. Please ensure you have the appropriate permissions to modify the registry.</p>
<p>Environment : VS2008 , OS is Windows 7</p>
<p>error PRJ0050: Failed to register output. Please ensure you have the appropriate permissions to modify the registry and after that regsvr32 crashes to regsiter the dll.</p>
<p>Thanks in advance.</p>
Comments: I've been experiencing very similar, if not the same problem. Year ago, someone reported it to StackOverflow as [COM registration fails with error code 0xC0000005](http://stackoverflow.com/questions/20044040/com-registration-fails-with-error-code-0xc0000005). I have a COM project which is instrumented with VLD. There is Custom Build step running regsvr32. Every time I build Debug variant of the project running MSBuild in command line or build from VS2012 IDE, regsvr32 exits with: -1073741819 (0xc0000005) code which denotes access violation. The failure is logged in Event Viewer as error due to OLEAUT32.DLL failure. So, I debugged regsvr32 and I found access violation occurs in oleaut32.dll!_MemFree, similarly to the report on StackOverflow. Interestingly, two of my colleagues are unable to reproduce this problem building the very same project in Debug mode using the same VS2012 Update 3 with VLD 2.3. I, however, am experiencing it on two development platforms I use: * Windows 7 + VS2012 Update 3 + VLD 2.3 * Windows 8.1 + VS2012 Update 3 + VLD 2.4RC In release build, without VLD, regsvr32 works without any problems.
<p>Environment : VS2008 , OS is XP </p>
<p>error PRJ0050: Failed to register output. Please ensure you have the appropriate permissions to modify the registry.</p>
<p>Environment : VS2008 , OS is Windows 7</p>
<p>error PRJ0050: Failed to register output. Please ensure you have the appropriate permissions to modify the registry and after that regsvr32 crashes to regsiter the dll.</p>
<p>Thanks in advance.</p>
Comments: I've been experiencing very similar, if not the same problem. Year ago, someone reported it to StackOverflow as [COM registration fails with error code 0xC0000005](http://stackoverflow.com/questions/20044040/com-registration-fails-with-error-code-0xc0000005). I have a COM project which is instrumented with VLD. There is Custom Build step running regsvr32. Every time I build Debug variant of the project running MSBuild in command line or build from VS2012 IDE, regsvr32 exits with: -1073741819 (0xc0000005) code which denotes access violation. The failure is logged in Event Viewer as error due to OLEAUT32.DLL failure. So, I debugged regsvr32 and I found access violation occurs in oleaut32.dll!_MemFree, similarly to the report on StackOverflow. Interestingly, two of my colleagues are unable to reproduce this problem building the very same project in Debug mode using the same VS2012 Update 3 with VLD 2.3. I, however, am experiencing it on two development platforms I use: * Windows 7 + VS2012 Update 3 + VLD 2.3 * Windows 8.1 + VS2012 Update 3 + VLD 2.4RC In release build, without VLD, regsvr32 works without any problems.