SpySweeper startup oddity

[Gustavus]

Spy Sweeper 4.5.9 (build 709) is reporting a strange thing each time I boot. It opens the Startup Shield Alert saying it has found a new program that will start when windows starts, but shows it as (No Title). I have clicked for it to remove this but it can't. If I click on More Details, it shows Product Name not provided, Company Name not provided and Copyright Information not provided. In other words it is seeing something that is to start at bootup, but unlike all other cases, it doesn't see any information about what is starting. I have checked in the startup folder (nothing new or unusual) cleaned the registry with Registry Medic -- all to no avail. I would like to get rid of whatever is causing this to happen, but don't know what it could be.

Any ideas?

Thanks for the help

 

[BadThad]

Run a scan in safe mode. Also, don't just rely on Spy Sweeper alone (although it's a great program.=).

 

[Gustavus]

BadThad,
Thanks for the reply. I had run a normal scan, although I didn't think it was spyware, without finding anything -- other than the usual assortment of cookies. A safe scan was also unsuccessful. I have found and fixed the problem and will report it here just in case someone else encounters the same thing. If you go to Shields and then Startup Programs in Spy Sweeper, you can click on Edit Startup Items and get a listing of all of the startup items Spy Sweeper has identified. One of those was the No Title item which I unchecked to prevent it starting. Spy Sweeper no longer shows the alert for the No Title item wanting to start on bootup.

I think what must have happened is that some piece of software that used to startup on bootup was removed and Spy Sweeper failed to remove the entry from its startup list, although it no longer had a name, company or copyright information to associate with it.

Problem solved so far as I am concerned. I don't know which piece of software amy have caused this, but the most recent install/uninstall was the PGP encryption suite. Could have been the culprit.

 

[BadThad]

Great, good news and thanks for sharing your fix!