locked
How do I suppress all these "HR propagated" messages under the debugger? RRS feed

  • Question

  • Using VS2010 while debugging our app, we now see a slew of messages like the following which are not written by our app. Can anyone tell me where they are from and how to suppress them?

    *** HR originated: -2147024774

    *** Source File: d:\iso_whid\x86fre\base\isolation\com\copyout.cpp, line 1302

     

    *** HR propagated: -2147024774

    *** Source File: d:\iso_whid\x86fre\base\isolation\com\enumidentityattribute.cpp, line 144

     

    *** HR originated: -2147024774

    *** Source File: d:\iso_whid\x86fre\base\isolation\com\copyout.cpp, line 1302

     

    *** HR propagated: -2147024774

    *** Source File: d:\iso_whid\x86fre\base\isolation\com\enumidentityattribute.cpp, line 144

     

    *** HR originated: -2147024774

    *** Source File: d:\iso_whid\x86fre\base\isolation\com\copyout.cpp, line 1302

     

    *** HR propagated: -2147024774

    *** Source File: d:\iso_whid\x86fre\base\isolation\com\enumidentityattribute.cpp, line 144

     

    *** HR originated: -2147024774

    *** Source File: d:\iso_whid\x86fre\base\isolation\com\copyout.cpp, line 1302

     

    *** HR propagated: -2147024774

    *** Source File: d:\iso_whid\x86fre\base\isolation\com\enumidentityattribute.cpp, line 144

     

    *** HR originated: -2147024774

    *** Source File: d:\iso_whid\x86fre\base\isolation\com\copyout.cpp, line 1302

    Monday, April 19, 2010 7:21 PM

All replies

  • Hello,

    Thanks for reporting this issue.

    This is a known issue which has been reported at https://connect.microsoft.com/VisualStudio/feedback/details/535084/vs2010-debug-output-should-be-cleaned-up?wa=wsignin1.0#details

    Product team confirmed that this is a bug and it will be fixed in SP1 if it has high vote.

    Thanks.


    Hongye Sun [MSFT]
    MSDN Subscriber Support in Forum
    If you have any feedback on our support, please contact msdnmg @ microsoft.com

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    See what's happening in MSDN forum? Follow us at Twitter.
    Tuesday, April 20, 2010 8:46 AM
  • That connect issue is marked "Closed as fixed" but the issue is NOT fixed.  I have up-voted it but it should be marked as Active.
    Tuesday, April 20, 2010 12:13 PM
  • This output is occuring inside the .NET runtime, and only appears when attached with a native debugger (usually because you are doing interop debugging).  If you do not need to be doing interop debugging, disabling mixed mode debugging and enabling only managed debugging will prevent this output from appearing.
    Best Regards, Andrew Hall. Visual Studio Debugger.
    Wednesday, April 21, 2010 12:38 AM
  • Thank you for the explanation Andrew.

    Our statistical app is a mixed mode (C++, C++/CLI, C#) app and we need to use this mode. I'll end up explaining these messages to statistical developers repeatedly so from my perspective these messages really need to be eliminated. Please add another couple dozen votes on behalf of our team :-)

    John

    Wednesday, April 21, 2010 2:33 AM
  • Hi Andrew

    we have the same error. @Andrew: please add my vote :-)

    Fritz

    Wednesday, April 21, 2010 12:01 PM
  • I am only using DebugView (i.e. a debug monitor and no debugger) and I get these message.

    Please add my vote. It messes up all of my debug messages during testing.

    Thanks

     


    dave
    Monday, May 10, 2010 11:54 PM
  • Andrew,

      Our application shows the same error even when running in release mode outside the debugger and using DebugView.  Our application is mixed mode.  Plase add a vote for me.

      Is this just debug out to be cleaned up, or is there something wrong?

    Paul

    Tuesday, May 11, 2010 9:30 PM
  • I too find this really annoying.  The worst thing about it is that the same processes prints out loads of empty lines, so even if I filter out "HR propagated" I get pages of empty lines printed in DebugView!!! So.... annoying....
    Thursday, June 10, 2010 10:33 AM
  • This is extremely annoying, please fix!!

    • Proposed as answer by Jeffrey__ Thursday, November 4, 2010 6:40 PM
    Thursday, August 5, 2010 3:55 PM
  • One more vote! Should not have allowed the Windows Update!!!!!!!!!!!!!!!!!!!!!!!!!!!

    Bad day. Don't need new garbage spew!!!

     


    Thomas F. Divine http://www.pcausa.com
    Thursday, October 28, 2010 1:55 AM
  • Enabling only managed debugging is not an option when debugging drivers using WinDbg.

     


    Thomas F. Divine http://www.pcausa.com
    Thursday, November 4, 2010 6:59 PM
  • Add my vote!

    I met this problem when upgrading our applicaiton from .Net 3.5 sp1 to .Net 4. Please fix!

     

     

    Wednesday, November 17, 2010 5:04 AM
  • Add my vote, too!

     

    I'm running into this error when debugging a mixed app.

    By the way: Is it possible that pure C/C++ apps may get an exception they cannot handle with try...catch when this debugger entries are shown?

    If so add 1000s of votes please.

     

    Tuesday, November 30, 2010 2:48 PM
  • Please add our vote. This makes it very difficult to see our own debug messages.

     

    -Corey

    Tuesday, February 1, 2011 8:49 AM
  • Please count my vote as well. This is really annoying.
    Tuesday, February 15, 2011 6:12 PM
  • After upgrading to Windows 7 SP1 both my 32-bit and 64-bit installs display this message in the kernel debugger.

    This is not a Visual Studio issue really, however this is the only thread I have found about it.

     

    It would be greatly appreciated if this was fixed. It is not very helpful when trying to write a driver. It is also detrimental to system performance when the debugger is attached. Kernel debugger messages have a noticeable overhead attached to them.

    Thursday, March 3, 2011 9:43 AM
  • Add my vote too. Its really annoying!

    ____________________

    Plates

    Saturday, March 5, 2011 8:15 AM
  • I see that SP1 was released. By any chance did this fix make it in? Thanks.
    Wednesday, March 16, 2011 2:27 PM
  • I don't know if this helps, but I'm seeing this on Windows 7 using visual studio 2005 and .Net 2.0.  I'm just glad to hear it's not Human Resources trying to get my attention.


    Note, I don't have a d:/ drive, let alone some iso folder sitting on it, so I'm very confused by the message.  I guess I need to get out some more of those old sys internals tools and start digging, it shouldn't be that hard to figure out which binary is emitting this stuff should it?

    hmm:

    tasklist | strings | findstr "HR originated"

    with a bit of extra effort, guess I need to get busy and install cygwin for strings. 

    A better method might be putting a breakpoint inside the dll containing OutputDebugString and catching these calls in the act, but that would require installing a debug version of the OS...

    Friday, March 25, 2011 5:43 PM
  • Add a vote for me please
    Monday, April 4, 2011 5:18 PM
  • This is very annoying indeed, please fix it soon!

    -2147024774 = 0x8007007A

    8007007A ERROR_INSUFFICIENT_BUFFER
    The data area passed to a system call is too small

     

     

    Wednesday, April 6, 2011 6:55 AM
  • And another vote.  Please, please stop this!
    Wednesday, June 22, 2011 10:33 AM
  • Mr MSFT, fix it, or give _acceptable_ workaround ASAP. Please add my vote.

    Monday, June 27, 2011 6:27 AM
  • I bump the vote to fix it as well
    Tuesday, July 5, 2011 3:39 PM
  • Really annoying.  Please fix.  Add my vote.
    Tuesday, August 16, 2011 11:57 PM
  • Incredibly irritating.  Why hasn't this been fixed yet?
    Wednesday, August 17, 2011 5:11 PM
  • Yes this has been very irritating +1 for my vote. Please fix or provide resolution
    KAV
    Wednesday, September 7, 2011 8:12 PM
  • Please add my vote as well. It is very annoying.
    Tuesday, October 4, 2011 2:49 PM
  • One year and a half, more than 55 votes and the problem still persist. No workaround, no solution. Way to go.
    Friday, October 21, 2011 2:06 PM
  • +1 add my vote, this output is very inconvenient!
    Wednesday, November 2, 2011 7:59 PM
  • +1. This has to be fixed

    Upgrading from 3.5 to 4.0 has caused this issue to me, it was so convenient to use the DebugView to trace the errors and sequence of action, this text has really made it messy. 

    Resolution is much awaited from Microsoft!!!


    KAV
    Thursday, November 3, 2011 8:42 PM
  • +1 add my vote too.
    Friday, November 4, 2011 10:05 AM
  • Please add my vote as well, this is very annoying...
    Monday, March 19, 2012 1:36 PM
  • I use .NET 3.5 SP1, the issue is not fixed
    Wednesday, June 20, 2012 3:39 PM
  • Not fixed on VS2012 RTM as well
    Wednesday, September 5, 2012 8:42 AM
  • Please fix this!!! I use the latest tools. It is still happening.
    Monday, June 24, 2013 9:25 AM
  • Still happening, and I don't believe it's to do with VS at all, as it's happening for me on a machine that doesn't have VS installed (I'm using DebugView).

    Tuesday, June 3, 2014 1:09 AM