Error log Event id 63 attributed to SpyBot

[dblake]

Going thru my event log I see Error: event id 63, source: SideBySide that appears to be pointing to Spybot. It had the following text:

Activation context generation failed for "c:\program files (x86)\spybot - search & destroy\DelZip179.dll".Error in manifest or policy file "c:\program files (x86)\spybot - search & destroy\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.

I'm running Win7Pro-64bit, i7-920cpu, Gigabyte mobo.

As far as I know Spybot seems to run ok, I'm not using tea timer.

Wondering if anyone has info on how to fix this. Or is it a bug?

[spybotsandra]

Hello,

Did you open Spybot with a right click and choose "run as admin"?
http://www.safer-networking.org/en/faq/42.html

Best regards
Sandra
Team Spybot

[dblake]

ok, is that something that should be done every time or can it be set permanently somehow?

i hadn't noticed any problems running it by left clicking except for the error in the log.

[spybotsandra]

Hello,

This has to be done every time.

Best regards
Sandra
Team Spybot

[drragostea]

Nice specs dblake.
-
If this still applies, I recalled Zenobia once said that you could right click the Spybot-Search&Destroy icon>Compatibility tab and there will be an option that will say "Run as Admin". I am not sure if this still works, but the last I have encountered it was with a user that ran Windows Vista.

[dblake]

thanks for the tip, ill try that.

previously id gone to security tab & given my logon all permissions for the file but run as admin looks better.

dont think thats the problem tho.

closer reading of error msg looks like the op system doesnt't like a line of code in the dll itself.

since the prgm appears to be running ok ill just ignore it. was just trying to clean up the red errors in the event log.

[dblake]

fwiw, a little more info.

right click dll & try to 'register' produces error msg about 'module not loading'.

i booted to win7-32bit & checked event log & no errors so this might be a 64 bit op system issue?