cli.exe obsession with the Registry

rseiler

I have Cat 5.11 (first-time install of any Cat) and I've noticed with Regmon (http://www.sysinternals.com/Utilities/Regmon.html) that cli.exe accesses this area of the Registry every several seconds:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib

Looking at this DWORD item:
Disable Performance Counters

It doesn't matter if it's there or not (by default it's not), it still looks.

I've also seen someone months ago mention the above in a newsgroup post, but I never saw an explanation or way of stopping it.

It's not causing a problem but is a waste. Yes, not running CCC in the first place would solve this, but that's beside the point.

Related question: If you do have CCC installed, must the cli.exe's be resident? Is it possible not to run the cli.exe startup process and have it run only on demand (i.e. when you actually use CCC)?

Thanks

Spyre

You can end task it and use the restart runtime option in the start menu to start it when you want.

Mayro

it seems that it (cli) doesnt even like the final version of net 2....

reholli

That's what people keep saying, but many of us are using it just fine with .NET 2.0, either with both 1.1 and 2.0 installed, or with just 2.0 installed, as in my case.

rseiler

Yes, I figured out that the task (actually two) doesn't need to be running, so I used MSCONFIG to take it out of startup. That solves the problem by bypassing it, though it would be nice to know why it accesses the Registry when it is running.

BTW, I didn't notice the "restart" option before you mentioned it. I notice that starting from no cli.exe's in memory it puts both cli.exe's back, versus just running it the other way (regular Start menu item, desktop icon, etc) still runs CCC yet puts only one cli.exe back in memory. Perhaps unless the "restart" method is used it's not fully functional, I'm not sure.