WSA + other AV suites/IS/Mega suites

Hi,

WSA is compatible to other third party AV suites/IS/Mega suites.

I'm interested in how it works. I mean the technical ways WSA makes sure no compatibility issues rise with other suites.

Also I wonder how many of the wilders members use WSA with other suites.

Best Wishes,
Amit

 

You know i like to test combo's compatibility; actually , i test Emsi pack (EAM + OAP, EAM set on "detect on read) + NOD32 v6 (HIPS disabled, RT set on "scan on created & executed) + WSA. (overlapping, i know, but i'm curious ^^).

Btw, no issues so far. all works together like a charm.

 

On this main PC In real time I use WSA & Mbam pro along with LnS - Trojan Remover is passive & I scan weekly or so with that. I also have licenses for the full versions of SAS & Emisoft & have run them in real time with WSA & have never had any issues - At the moment they are not installed as I don't feel the need. I did use the full version of Hitman without problems but let the renewal license lapse recently as it never found anything but a few FP's -

I've also recently run WSA along with Norton NIS 2012 & (2013) though NIS no longer named by the year without problems: But I far prefer WSA along with Mbam & personally feel no need for any other protection - If LnS were not so light on resources I wouldn't use a secondary firewall either. My other PC's just have WSA & Mbam pro & remain issue free

 

PrevxHelp commented on this here.

 

Ah missed that. Thx a lot Tony. @pc and @guest thx a lot guys.

 

Like PC_Fiddler, I have run it with a few other products with no adverse effects: ESET and MSE to name two. But now I simply use it with MBAM-Pro and seems more than adequate.

 

Okay I've just installed WSA in this pc. Everything is fine but a bit slower. Is this a type of conflict?

 

Could be yes. Though have you checked that Emsisoft V7 is compatible with other vendors in the same way that V6 was ? I mean now that they have changed engines and all.

 

Check your scan logs for lines. If you've got a lot of them, especially if any of them are running, it means you use weird, cool stuff and Webroot doesn't know about it yet, so contact support for determinations.

 

@SweX
Yes I've asked Emsisoft Support Team if version 7 was compatible with other av suites before installing WSA. They said it was.

The two actually should not conflict afaiu. I mean EAM is supposed to be compatible with other suites and WSA is said to be especially designed to be compatible. I'm not putting either of them with a full blown av suite/is/mega suite which would not accept other av. But I'm putting them with each other. So no conflict in theory, right?

 

@TechFox
I have absolutely no idea what you're saying. What are scan logs for lines? Where do I find them?

 

@Amit
System Tools->Reports->Scan Log (Save as)
For example, in my log:
c:\program files\ccleaner\ccleaner.exe [MD5: BE66B026CF488C87B4D0EA9E616FFA4A] [Flags: 400A1011.2112]
In this case, I would think ccleaner would be a known file.

 

Definately not running any "weird, cool stuff"

I wish I didn't have to contact support, to sort out determinations I know about, just to get my scan time lowered from the current 20 minutes to less than 4 minutes. Such an annoyance!

e.g.

c:\$mbr.1 [MD5: D86096E61CF49BD077B9615C2549B67A] [Flags: 00000000.127]
c:\program files\gfi software\vipre\sbamwsc.exe [MD5: 7944909492E61AB77773C08A6DFA8557] [Flags: 00081010.7145]
c:\program files\gfi software\vipre\vipre.dll [MD5: C610485022BDAF12F3836B6955470B69] [Flags: 00081010.3037]
c:\program files\gfi software\vipre\sbamoutlook.dll [MD5: 3FA7C4DB146E8B07DE5E62DC7C89EDEC] [Flags: 00081010.7144]
c:\program files\gfi software\vipre\sbap.dll [MD5: 09289206C1FDDD64CA96E024D5C4B23E] [Flags: 00081010.7117]
c:\windows\installer\{ad02a465-ae8e-40d3-80e2-de095484a761}\newshortcut21_339c927bb4b547f9804fdf51f01d2d57.exe [MD5: 20FCD12AD239B1AC6DC0EB58B2384FA3] [Flags: 00081011.6152]
c:\program files\vx search\bin\vxsrch.exe [MD5: 95A4E894C6889DDD2CABFF7B7162ED25] [Flags: 00080010.1989]
c:\program files\gfi software\vipre\sbamsvcps.dll [MD5: E92F9A1CAF8369D541DA870B683A33D6] [Flags: 00081010.7134]
c:\program files\gfi software\vipre\sbpimsvc.exe [MD5: 5314272972576D925A54CABAFD1E7FBF] [Flags: 10081010.7127]
c:\program files\gfi software\vipre\sbarva.dll [MD5: 08AF0B15AC1696F1F9B58FAB6560372B] [Flags: 00081010.7148]
c:\program files\gfi software\vipre\sbca.dll [MD5: 1C3C1A4C04409BC0DEDB8D3C65DE60E5] [Flags: 00081010.7139]
c:\windows\installer\{ad02a465-ae8e-40d3-80e2-de095484a761}\newshortcut2_339c927bb4b547f9804fdf51f01d2d57.exe [MD5: 3F248A90484545BF1FD78FF1E99AF600] [Flags: 00081011.6153]
c:\program files\gfi software\vipre\spursdownload.dll [MD5: 9EBA2C513B44A87C1E4A2A4115FA5AB8] [Flags: 00081010.7123]
c:\program files\gfi software\vipre\sbamsvc.exe [MD5: 99FC1599F89A80216E41175B8CA44D89] [Flags: 10081010.7121]
c:\program files\gfi software\vipre\sbte.dll [MD5: E691826F57C814DECD85E143BB8F15C0] [Flags: 00081011.7056]
c:\windows\system32\drivers\safemon.sys [MD5: 97BC7732FE1EBD3DFC0BA43C7932E8D5] [Flags: 00081010.426]
c:\program files\gfi software\vipre\sbhips.dll [MD5: 414F0C81BC69D2BF7216B0A5432DBA7F] [Flags: 00081010.7133]
c:\program files\gfi software\vipre\sbsetupdrivers.exe [MD5: 0521CE195006264D18EDC86A7C4BA333] [Flags: 00081010.7147]
c:\windows\installer\{39a0a1d8-e31d-43da-8251-37f42c7ea795}\newshortcut21_339c927bb4b547f9804fdf51f01d2d57.exe [MD5: 761762624DEED6F6D0639420C4262B18] [Flags: 00081011.6112]
[U] c:\program files\gfi software\vipre\drivers\amd64\wlh\sbhips.sys [MD5: 1490E7C7A22329BE5641D4C2E16B868E] [Flags: 00091010.7130]
[U] c:\program files\gfi software\vipre\drivers\i386\wlh\sbhips.sys [MD5: BE4CCD4A299337CBA1CE41DB9E2C2543] [Flags: 00081010.7142]
[U] c:\program files\gfi software\vipre\plugins\pi_patchmonitor.dll [MD5: 25F1C5BF31FEA0EB1194AD05B6BED9C2] [Flags: 00081010.7124]
[U] c:\program files\gfi software\vipre\plugins\pi_recovery.dll [MD5: BC2984F79E964D1A59C638BB3B649CF0] [Flags: 00081010.7119]
[U] c:\windows\installer\{661e0398-f846-44dc-a622-f34c30fdd312}\newshortcut21_339c927bb4b547f9804fdf51f01d2d57.exe [MD5: 5CCEECFDED8073598A0140BF8E8AD008] [Flags: 00081011.6125]
[U] c:\program files\gfi software\vipre\drivers\i386\wlh\sbtis.sys [MD5: 168F4D58425141A94FBE555F8BCB378C] [Flags: 00081010.7146]
[U] c:\program files\gfi software\vipre\drivers\amd64\wlh\sbtis.sys [MD5: E74431E8DECBC4E88BEF955497B8928B] [Flags: 00091010.7131]
[U] c:\program files\gfi software\vipre\drivers\amd64\wlh\sbwtis.sys [MD5: 051C35F5FF516398FFC806979C709A2F] [Flags: 00091010.7122]
[U] c:\program files\gfi software\vipre\drivers\amd64\wnet\sbtis.sys [MD5: 8F549F109F3D0CF1171C45B2C2A3B138] [Flags: 00091010.7132]
[U] c:\program files\gfi software\vipre\drivers\i386\w2k\sbtis.sys [MD5: A1DA0C619ED8F49DD904100BA2BE04EA] [Flags: 00081010.7120]
[U] c:\program files\gfi software\vipre\drivers\i386\wlh\sbwtis.sys [MD5: 089B10BD0619EFA9CE4812E0B4E685EE] [Flags: 00081010.7125]
[U] c:\utilities\tor\tor browser\app\tor.exe [MD5: 235CEB06FB4C6B460DD3A1CE80E01DDE] [Flags: 10080810.2704]
[U] c:\windows\installer\{661e0398-f846-44dc-a622-f34c30fdd312}\newshortcut2_339c927bb4b547f9804fdf51f01d2d57.exe [MD5: 9F07D5AA03C010EDCD117BFB54E41E70] [Flags: 00081011.6126]
[U] c:\program files\opera next\opera.exe [MD5: 5C54D20BD7BEFCC3BE01F101298EEC7D] [Flags: 515C1110.139]
[U] c:\program files\opera next\pluginwrapper\opera_plugin_wrapper.exe [MD5: BE10AB40F3252785979C7760EAFBCB83] [Flags: 511C1010.140]
[U] c:\program files\securityxploded\operapassworddecryptor\operapassworddecryptor.exe [MD5: 31BC03B2696425AEDAF2DC2DA2F3A509] [Flags: 40080010.141]
[U] c:\program files\gfi software\vipre\sbtis.dll [MD5: 9BA9F1AFE93C1EA09F96FDB497F6C653] [Flags: 00081010.7126]
[U] c:\windows\installer\{41edead1-2f20-49b0-9e83-ae65047589d4}\newshortcut2_339c927bb4b547f9804fdf51f01d2d57.exe [MD5: 125361521151EB2253DCE6A424864983] [Flags: 00081011.6117]
[U] c:\program files\opera next\mapi\operamapi.dll [MD5: 9293A2C1A3EF8D1E107795BBB9997F7E] [Flags: 40080010.142]
[U] c:\windows\installer\{41edead1-2f20-49b0-9e83-ae65047589d4}\newshortcut21_339c927bb4b547f9804fdf51f01d2d57.exe [MD5: 38C8EA523EBB5DA5B028E14A19200209] [Flags: 00081011.6116]
[U] c:\program files\gfi software\vipre\sbamcommandlinescanner.exe [MD5: 2FA632819FA36825E7124CCB278DC898] [Flags: 00081010.7143]
[U] c:\program files\gfi software\vipre\sbamscanshellext.dll [MD5: 001872A724DFB8F8BF49BCA8426C058E] [Flags: 00081010.7135]
[U] c:\program files\gfi software\vipre\sbamui.exe [MD5: 4700BBF8B8869CCDAE9FC2A8ED12E3E8] [Flags: 000A1011.7057]
[U] c:\program files\gfi software\vipre\sbamcreaterestore.exe [MD5: 3113239A6B351913DE3BFE670179A5F5] [Flags: 00081010.7136]
[U] c:\program files\gfi software\vipre\sbfe.dll [MD5: C1506FBB5F07431238D2F9EFBC2FF6B0] [Flags: 00081010.7116]
[U] c:\program files\gfi software\vipre\sfe.exe [MD5: 4422201D404ABF7465CEDDF9E12DCD71] [Flags: 00081010.7118]
[U] c:\program files\gfi software\vipre\sbamtray.exe [MD5: 2677FD8468E489B14135F795F1A0780A] [Flags: 00081010.7115]
[U] c:\windows\system32\drivers\vdd\apvdd.dll [MD5: BB29807D7CBE84C052F8E60BDD78AE79] [Flags: 00081010.7140]
[U] c:\program files\gfi software\vipre\gfiarksh.dll [MD5: 967FC9D11343766707E8A3D238597018] [Flags: 00081010.7141]
[U] c:\program files\gfi software\vipre\x32\sbbd.exe [MD5: 963DDEAB8E9ECFC908D62AEA91C60312] [Flags: 00081010.7129]
[U] c:\program files\gfi software\vipre\x64\sbbd.exe [MD5: D95CD9B1BB27B748864DC4914B1ACF05] [Flags: 00091010.7138]
[U] c:\program files\gfi software\vipre\sbrc.exe [MD5: E9C0B6518F4F4145267C9F0E0D9ED9CF] [Flags: 00081010.7128]
[U] c:\program files\gfi software\vipre\drivers\amd64\sbapifs.sys [MD5: 8F19D62B04081C0BFF1E8D6F26220A28] [Flags: 00091010.2652]
[U] c:\program files\gfi software\vipre\drivers\i386\sbaphd.sys [MD5: 862EEC4DFFF55AB124C9F4C758BECC39] [Flags: 00081011.2621]
[U] c:\program files\gfi software\vipre\drivers\i386\sbapifs.sys [MD5: 87574F4C899E8AEDDDC1EDF71D3E045E] [Flags: 00081011.2620]
[U] c:\program files\gfi software\vipre\drivers\i386\sbapifsl.sys [MD5: 5E0DF62A272B4E668A094CEC32C89068] [Flags: 00081010.2646]
[U] c:\program files\gfi software\vipre\incompatibleprograms.dll [MD5: 47121B2AB142D8F079B174E190DE28EE] [Flags: 00081010.7137][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U][/U]

 

@Thankful
Thx my friend. It shows many files with md5 and flags. But how would I know if I'm running any cool weird stuffs unknown to WSA? I'm not that experienced or techie to understand what the log says or indicates and how to use the log to find out unknown cool weird stuffs.

 

Using Emsi pack + NOD32 + WSA :

1- some delay when WSA scan the process for the first time (visible by the popup), after it is ok
2- 0.25 sec delay in context menu appearance

after nothing special.

For EAM v7 , i can confirm it is still compatible with other products (i am a closed-beta tester) and the main requests from the developers to us is to test compatibility.

 

@guest
Thank you for the confirmation my friend. My browsing is also slower now. I think it's the web threat shield in wsa double scanning for threat while I'm browsing and EAM along with OA also scanning for web threats. Opening files and folders are taking slightly more time.

 

With all the security programs that you run in realtime I wouldn't complain about scan times 4 minutes is pretty good Just teasing you!

TH

 

Yeah sure, what I meant was that WSA is absolutely compatible with other products, but the other products may not be compatible to the same extent as WSA.

 

@SweX
Yeah well you're right. I've removed wsa from this pc and put it on another one. Now both EISP and WSA can have their freedom and work to their full potential.

 

That's good

 

Yeah both pcs run as expected - much lighter.