av problem

[Henry]

i recently got a virus infection
it killed my AVG
now i am using pc tools
but when i try to install a flight1 and install the wrapper
i get a virus notice
and it kills the exe
then i check after with malwarebytes and there is one in the registry
now i know this is not in fact a virus
has anyone else had this problem?
H

[tracyq144]

Yaey, the Lord says "Thou shalt not view the porn in words, nor shall thy view the porn on any device, be it the public television, nor the iPhone, nor the computer, though the computer may be used for viewing the Youtube, but the Youtube shall not be used for the viewing of the porn, lest the viewing lead to infections.

Just saying. :wavey:

[Cactuskid]

I recently had a similar problem... I was having a lot of problems with Norton AV, so I uninstalled it, and before I could install a new AV program, my computer got so badly infected that I finally had to dump the OS and re-install Windows. The malware infection would not let me log-on as administrator, and I could not open any .exe files. It also wiped out my folder options in the control panel so I couldn't get to my fsx.cfg and neither could FSX, so it wouldn't load. I was also unable to load a new AV program. :isadizzy:

I hope your problem is not as bad as mine was... Re-installing the OS and FSX with all the add-ons that I have was a lot of work!

[harleyman]

H


You have to allow that ..Do Not block..

Its probably a huerer engine its blocking...

Just tell it to allow and have it added to your Global Action List

[Henry]

H


You have to allow that ..Do Not block..

Its probably a huerer engine its blocking...

Just tell it to allow and have it added to your Global Action List
confused its only flight 1 installs
if i allow "and i know they are not infected"
i still get my back up av kill
H

[harleyman]

confused its only flight 1 installs
if i allow "and i know they are not infected"
i still get my back up av kill
H



Ummmm Its the flight 1 installer that it does not recognize...I had the same problem.....

What does I still get my backup AV kill ....mean ?

[FAC257]

Same here. A few Flight1 and a few Carenado installers had issues.

FAC

[Henry]

Ummmm Its the flight 1 installer that it does not recognize...I had the same problem.....

What does I still get my backup AV kill ....mean ?
it means i have 2 av's
if the first dont get it the 2nd will
at least thats my theory
H

[NoNewMessages]

You should have only one AV product running, otherwise you can get some nasty conflicts.

Any AV product should allow you to ignore oe exempt a product, file, folders, etc, otherwise I would not use it. No one has found a virus in any of the Flight1 products that I am aware off, but the AV scanners may flag them. That's why it's important to be able to override the AV.

[IanP]

Opposing anti-virus applications will usually report each others' scans as attempts to infect the system, so your solution may well be that you just need to clear out both AV applications totally, then install one particular choice.

[Henry]

actually i have 1 av and 1 malware
product running
i know they are the problem and not flight1
its just frustrating
H

[Wing_Z]

I use Microsoft's Windows malware product.
It never catches anything, so I never have issues like this :d

[Henry]

I use Microsoft's Windows malware product.
It never catches anything, so I never have issues like this :d
LOL
actually i turned of av for installing F1 wrapper
and it works run a scan afterwards and no VIRIsess:applause:
H

[IanP]

I had a number of problems with AVG when I was using it, to the point at which I threw it away and went to Avast. That seems a lot happier on all the PCs I've put it on and so far - touch fake wood desk surface - I've not caught anything malicious.

I can see one issue in trying to put in an exclusion to make the AV scanner ignore the F1 wrapper, though, which is that the wrapper executable is named differently for each installer.

[Henry]

I can see one issue in trying to put in an exclusion to make the AV scanner ignore the F1 wrapper, though, which is that the wrapper executable is named differently for each installer.
yup and i have a few
H