To answer our question, I would say yes, this is a baddie and needs to go.
But, further analysis is needed to determine exactly which baddie it is... there are a number of different baddies that use winsock32.exe. The path where it runs from and Reg keys differ among the various baddies and we'd need to pin them down.
Perhaps a WinPFind2 Log......?
I am heading out the door, but Judy will be able to help you and I really don't want to step on her toes
Best Luck
PP






Reply With Quote