Error during check!: Win32.Autorun.cfto

No, it is not fixed. It is really amusing to see the same problem reported in 2005 and appearing now, with initially a completely bullshit answer from Spybot that the trouble resides in a non updated version of Windows, and then we see that the same problem appears in all version of Windows and in all versions of Spybot. I am not a fan of political correctness. This is called professional incomtence. It looks like no one at Spybot having enough knowledge to at least recognize the nature of the problem has ever been informed of the issue, instead of which "Sandra", whatever her or his real name is, just gave out usual phone support salestalk.

I am disgusted.
 
No, it is not fixed. It is really amusing to see the same problem reported in 2005 and appearing now, with initially a completely bullshit answer from Spybot that the trouble resides in a non updated version of Windows, and then we see that the same problem appears in all version of Windows and in all versions of Spybot. I am not a fan of political correctness. This is called professional incomtence. It looks like no one at Spybot having enough knowledge to at least recognize the nature of the problem has ever been informed of the issue, instead of which "Sandra", whatever her or his real name is, just gave out usual phone support salestalk.

I am disgusted.

Yeah, actually that's my real name, and I'm a real person - shocker -
This issue has been reported as a false positive and it has been fixed.
 
Hello,

That is a different problem.
Did you open Spybot with a right click and choose "run as administrator/take ownership"?

Best regards
Sandra
Team Spybot


No, Sandra.
I opened Spybot as always, with a double click on its icon in my desktop.
Thank you anyhow.
Gigim

As I already said, this has nothing to do with this problem.
And unless you run Spybot as admin like described above you won't have the sufficient rights to fix this item.
 
Seems to be fixed on V 1.62(error during check)

Thanks a lot sandra,after updating today I get no more error!!!!
Only question is since 1.62 is dead shold we continue to update
this version or leave it as it is so the error message does not
come back??
You are doing a great job and Kind Regards
Rod
 
Last edited:
you went w 2.1?
i think 1x had a patch
so im not sure if dead yet

No I still use 1.62 and I updated it today and now it works
fine-was wondering if I should still update it? I dont want
that error message to come back,you see?
Rod
Wisconsin as well! Go Pack!
 
Back
Top