A strange solution to warnings about uninitialized variables

This is my third note on this subject, and I hope no-one objects.

My questions (and those of other members) were why perl sometimes claims
some variables have not been initialized, even when direct investigation
proves that the variables in fact have valid real values.  Several people
suggested helpful ideas, but none of them worked.

But then my PC tech installed a program to find and locate spyware on my
PCs.  The problem with Perl's strange warnings went away instantly, and
have never returned.  Nothing else changed:  same input files, same
program, and same version of Perl.

Does this make sense to anyone?  Would anyone have predicted this
behavior?

Thanks,
Walt