Brian Robbins

@wiktork, did the change made by @noahfalk end up fixing this?

Thanks @wiktork. Since we believe this is fixed in the current release, I'm going to close this issue. If you find that the issue is not resolved, just let me...

If you look earlier in the log, you'll see the following: ``` Parsing ETW Provider Spec: *Microsoft-System-Net-Http Parsing ETW Provider Spec: *Microsoft-System-Net.Security Enabling Provider:*Microsoft-System-Net-Http Level:Verbose Keywords:0xffffffffffffffff Stacks:0 Values: Guid:bdd9a83e-1929-5482-0d73-2fe5e1c0e16d Enabling...

> @brianrob Do we maybe want to rename the file in the package to have proper casing? Do you see any risk in doing that? I think this would be...

Can you share some details on the issue that you're looking to fix here? I am not super familiar with the details of the different ETW provider mechanisms, and so...

Thank you for the explanation. To make sure I'm understanding, are you saying that you're running into wpp events that aren't properly handled by TraceEvent and so they show up...

I need to think about this a bit more - I want to say I tried to fix this a while back and was convinced by @vancem that I shouldn't....

Co-pilot Post-Mortem: - The code was easy for copilot to get right. - I appreciated that the PR description described the solution and called out that this was done elsewhere...

> [@brianrob](https://github.com/brianrob) - do you think we should treat this guid encoding convention as a public convention of the runtime? If I recall correctly, it's not guaranteed that the GUID...

@ppozeti is this something that you're still interested in working on?