LinkBack URL
About LinkBacksI still think Kaspersky is the root of the problem :-D
This is a discussion on Reverting to a previous dev channel version within the Chrome Troubleshooting section, part of the Google Chrome category: I still think Kaspersky is the root of the problem :-D...
Moderator
Senior Member
We need Sohil to confirm he has disabled sandblocking as an option ...
That solution was posted after his last post ...
Senior Member
Reverting to a previpus version ...
Reverting to a previous dev channel version
Just 'cos it bugged me at the time, and I didn't have the time to check it out, I tried this again with the latest release of Chrome (3.0.183.1) today ...
It does work (knew I hadn't been dreaming) :-D
Last edited by StevePaul; 06-04-2009 at 10:17 PM.
Junior Member
Thank you guys for the help. But there's still an issue. The problem started when I had just UNINSTALLED Symantec and installed Kaspersky!! So, maybe Kaspersky, as devilslackey said, was the root of the problem and I had to disable sandboxing to go around it.
@Steve Paul: Yes, it did work, as in the version name changed, but chrome still showed the error. That's what I meant in that post. Sorry for the vagueness.
Senior Member
No problems ...
Without trying to confuse matters, it could still be something to do with Symantec there could be some bits of Symantec still hiding on your system which is causing the conflict ...
You could try a registry cleaner ...
Moderator
Ah, I love getting more details :-D
Try running the Norton Removal Tool from this site: http://service1.symantec.com/Support...05033108162039
Posting Permissions 
Reply With Quote