I, like others, had a problem with
CI-Commander1215.exe today.
After much investigation, I found that
I had to add it to the exclusion list for the Avast! antivirus
software. I have been running Commander and Avast! for years and
never had to do this before.
What made this particularly difficult
was that CI-V Commander would not show up in the Windows 10
Professional 64 bit task manager after starting it.
But what did happen was the Avast!
Service (32 bit) CPU utilization jumped from 0% to about 25% and
stayed there. In fact, I accidentally caused the utilization to
increase until 99% of the CPU was utilized by Avast! Service (32
bit). This was because I generated multiple starts of Commander
instances by trying to start again even though they never showed up
in the task manager. Needless to say the computer became
non-responsive.
They only way I found to exit this
condition was to exit all programs, hard to do when 99% CPU used, but
easy with only one start of Commander generated. I then had to do a
restart of the OS. However, even this was annoying as I would have a
spinning restart screen display sometimes for a very long period. I
used the power on button after five minutes of this to turn power off
to the computer and then turned power on.
I then discovered that if I turned all
shields off in Avast!, I could start Commander1215 and it would
execute. Note that turning shields off after Commander1215 was
started would not correct the hang condition described above.
At this point I added Commander1215 and
Commander to the Avast! exclusion list and it is no longer issue.
Commander1212 ran fine with Avast!
running even though it was not in the exclusion list.
I terminated my investigation at this
point.
I am reporting my observations for
whatever use they might be.
As always, I appreciate DXLabs and
thank Dave for it.
73,
Bill
NJ1H
