Solution to log tumor problems caused by clrprofile

W3wp.exe process will generate a log file in C: \ Windows \ temp \ pipe. log endless growth

This log file will grow endlessly. This slows down the system. Usually, the C disk contains only 0 bytes.
How can I stop this process from logging.
Some of the information was found to be caused by clrprofile.exe. But I do not remember that I have run this program. Or the program runs on the machine, but I don't know where it is.
I don't know why. It's almost suffering. Amount

The above questions are posted on the msdn operating system Forum module and nobody cares about me.

This problem cannot be solved. I searched for a post for the past 03 years and found it as follows.

I got the same problem, however I have overcame it. By any chance have you ever run CLR Profiler/Allocation Profiler? Do you remember it failing?
As per CLR Profiler Document (which is little ambiguous) following locations has "Environment" variable which needs to be removed in the case when Profiler results in an error:

• HKLM \ SYSTEM \ CurrentControlSet \ Services \ IISADMIN (ASP. NET)
• HKLM \ SYSTEM \ CurrentControlSet \ Services \ W3SVC (ASP. NET)

The deletion of these two key values still exists.

Then search for clrprofile in the registry.

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT \ CLSID \ {8c29bc4e-1f57-461a-9b51-rjc32e6f1f}]
@ = "Microsoft CLR Profiler Test"

[HKEY_CLASSES_ROOT \ CLSID \ {8c29bc4e-1f57-461a-9b51-rjc32e6f1f} \ InprocServer32]
@ = "E: \ Program Files \ CLRProfiler \ Binaries \ x86 \ profilerOBJ. dll"
"ThreadingModel" = "Both"

[HKEY_CLASSES_ROOT \ CLSID \ {8c29bc4e-1f57-461a-9b51-rjc32e6f1f} \ NotInsertable]

[HKEY_CLASSES_ROOT \ CLSID \ {8c29bc4e-1f57-461a-9b51-rjc32e6f1f} \ ProgID]
@ = "Objects Profiler. {8C29BC4E-1F57-461a-9B51-1200C32E6F1F}. 1"

[HKEY_CLASSES_ROOT \ CLSID \ {8C29BC4E-1F57-461A-9B51-1200C32E6F1F} \ VersionIndependentProgID]
@ = "Objects Profiler. {8C29BC4E-1F57-461a-9B51-1200C32E6F1F }"

When you see this key. I feel like I have found the correct place to export and then delete it. Then start the application pool to run the website. The pipe. log file is not created.