There are additional parameters in TPL ETW events that cause the debugger to overflow

Question

Update: this is not prefix related

I have an earlier version of the prefix installed. I updated it by running a new installer. After updating in VS.NET 2015 Update 3, I see these messages in the Debug output window when loading the Prefix module. These messages do not appear if Prefix modules are not loaded.

Event 10 was called with 5 argument(s) , but it is defined with 6 paramenter(s).
Event 7 was called with 5 argument(s) , but it is defined with 6 paramenter(s).

Is this a problem with a prefix or other component mismatch? Any idea how to fix this? I get hundreds of messages when debugging.

Updated on May 3, 2017 . I was able to determine where these messages came from. They come from the internal class .NET Framework System.Threading.Tasks.TPLETWProvider These two events:

Event 7: The TaskScheduled event method has an additional 6th parameter int appDomain, which is not used.

Event 10: TaskWaitBegin , which also has an additional unused int appDomain parameter.

When each of these methods ultimately calls EventSource.WriteToAllListeners, the method parameters are checked for the number of data elements passed. When there is a mismatch, a message appears in the output window in Visual Studio.

Related Sources for the .NET Framework 4.7. In my local version, I am running .NET 4.6.1 (mscorlib, Version = 4.0.0.0, Culture = neutral, PublicKeyToken = b77a5c561934e089)

I am really surprised that more people do not face this problem.