Ccleaner hobbled AnalogX NetStat Live

CCleaner for Windows CCleaner Windows Bug Reporting
1

New machine, fresh OS (XP Pro), installed all of my applications, so time for diag's and tuneups...

AnalogX's NetStat Live (a net bandwidth and cpu monitor) had been sitting quietly in the lower corner tabulating usage statistics on everything it can monitor including CPU usage (although, since I am running a Core 2 Duo, I have no idea whether it was just displaying one CPU or an average of both cores).

I ran Ccleaner and as expected it found many issues in the registry. After unchecking the broken shortcuts that I was going to fix manually I clicked on fix all problems (and stupidly did not let it back up the registry -- never again!!!) and let it do its thing. Upon my next reboot NetStat Live came up but is no longer displaying the CPU usage of the machine. This also happened a couple of months ago when I was doing some maintenance on my housemate's dual-core AMD box but was not worth investigating since he does not use the meter (I do when I am SA'ing). Any wisdom on what key or other repair procedure may have caused this would be most appreciated so that I can get it running again fully functional...

TIA for any help

2

welcome to the forums.

all i can suggest is maybe a system restore point?

start>programs>accessories>(system tools)>system restore.

hope this helps :D

3

Way too late for system restore point recovery -- tend to blow all but last away on a regular basis using Accessories --> System Tools --> Disk Cleanup before de-frag'ing...

4

Not sure what could have been the problem but you could just reinstall the program and run an issues scan and see what comes up.

5

I have de-installed NetStat Live down to the manual registry edit level (blowing away anything AnalogX) and then reinstalled from scratch and am still not showing anything in the CPU meter part of the app -- it has to be a key somewhere else that got flagged by Ccleaner that has an impact on what NSL can get to - nothing pops out at me on a sysinternals procexplorer analysis -- just weird.....