Gnutella Forums - LimeWire 8.0 broke McAfee VirusScan!

Gnutella Forums (https://www.gnutellaforums.com/)

- General Windows Support (https://www.gnutellaforums.com/general-windows-support/)

- - LimeWire 8.0 broke McAfee VirusScan! (https://www.gnutellaforums.com/general-windows-support/6404-limewire-8-0-broke-mcafee-virusscan.html)

Quote:

Originally posted by Unregistered
You'd think that if v1.8 really broke McAfee, there'd be a lot more folks screaming about it!

Hi, it is indeed LiMewire's fault. I also have the same problem. I use Windows NT 4.0 and right after installing Limewire V2.0.2, Mcafee Visruscan, in particular Vshield stopped working. When the computer starts I get an error on AVSync Manager service, and Vshield no longer loads, the rest of the package works.
I know it is Limewire fault because I made several tests and all the times, Mcafee visrusscan crashed right after installing Limewire. The most annoying part of the problem is that if I try to reinstall Virusscan, the installation crashes with MSIEXEC.EXE, that MS program is modified by Limewire.
The only solution I have found so far is a clean installation of Windows NT and all software and not to use Limewire... I still use Limewire and Norton Antivirus.

Sue The Bastards

I think there is a class action suit in this. The discovery process is a wonderfull thing ... unless you have something to hide.

Decline bundled software during Limewire install

I have three systems running here in my home -
Win 98 SE with Mcafee & Limewire 2.0.2
Win2K with Mcafee & Limewire 2.2.4 PRO
Win2k with Norton & Limewire 2.3 beta

I have experienced none of the problems mentioned in this thread. The only thing I might be doing different is I decline to install the junkware (Gator etc.) during the LIMEWIRE installation. I suspect this other software is the root of the problem. As I understand it Limewire itself is well behaved but the ad-on stuff that is bundled with the Limewire installer is really a bunch of spyware that DOES change your registry and DOES install some new DLLs etc. While I don't know for a fact I suspect this other software probably is a source of revenue for Limewire. As you will note I popped for the $8.50 for my primary system for the ad-free version of Limewire.

I concur with others that Adaware by Lavasoft (free version) will remove most of this crapware... I use it on the three systems of mine... and almost daily find Cydor and Double-Click stuff stuck onto my system by unscrupulous vendors.

Quote:

Originally posted by Unregistered
You'd think that if v1.8 really broke McAfee, there'd be a lot more folks screaming about it!

I have the exact same problem as Aaron. Vshield does not load immediately after installing Limewire! The "developers" comments have not been helpful...NON-SUPPORTIVE.

ok i got 2 trojens recently..limewire u suppose?

i cannot rid of one because it in use by windows..:mad:
plz help...my comps acting weird

well for one adam the old limewire version did not cauz me any problems

Something it installed broke McAfee

Quote:

Originally posted by afisk
I can look into this issue further. It's most likely a conflict between our installer and Mcafee that is totally unrelated to the LimeWire program itself. Our installer uses Microsoft's new "Windows Installer Service" (hence the messages about MSIEXEC.EXE). This is the "latest in installer technology", but it's notoriously buggy and appears to conflict with Mcafee.

Just for the general clarity on these issues for those interested, pretty much every program modifies the registry when you install, as this is the default setting with most installer programs. This makes sense because the registry was invented as a sort of "hidden" place to store application data, so everyone's using it for the intended purpose. LimeWire and LimeShop make really minimal registry changes that would not be causing this conflict (in fact, as a Java program, LimeWire doesn't even have built-in access to the registry -- we'd have to add some fancy native windows code to do this).

So, again, the issue is more likely a more basic conflict between the installer and Mcaffee. I would suspect, for example, that there are other programs that use InstallShield Developer 7 as their installer that would also cause this issue. I'll look into it more, though.

Thanks for all of the info, and our apologies for the frustration.

Adam, the latest windows installer sounds like the right track. Also did not like having to install Sun Java!