Problems with the new F-PROT v6

Thanks for the responses Supportguy.

 

I was out of town all day yesterday. Got back at 11PM. I knew Mike was going to fix the FP yesterday but I was too tired last night to try installing it again. So, I just did so today. I am happy to report that F-Prot no longer alerts on procguard.exe.

THERE IS NO OPTION TO CANCEL THE INITIAL SCAN ON BOOT AFTER INSTALLING. Maybe there is if you are a licensed user. I am using the TRIAL version and that option does not exist, as far as I could see, unless I didn't want a key and didn't want any update of the virus definitions.

Perhaps, you mean that I should have declined a key (why do I need a key for a trial anyway)? If I had declined to get a trial key during the install, then from what the setup window said, I believe that I would have gotten NO virus definition updates and there probably would not have been a scan done but there was NOTHING CLEAR about what would happen if I declined to get a key during the install. Obviously I want the latest definitions. The install window said I needed to get a trial key during install. It did not indicate that I could get this key later after I installed. If that is possible then the installer should say that! It said "get subscription, update and scan my computer". That does NOT tell me that it will scan my computer AUTOMATICALLY ON REBOOT. It indicates, at least to me, that F-Prot won't work if I don't get the subscription key and that I must get the key DURING THE INSTALL since that window is there. It does NOT indicate that a scan will start AUTOMATICALLY after reboot, only that I will get the latest definitions and be able to do a scan.

So, I went ahead and got the trial key during the install. I put in my name and email address. Then I was told to reboot to finish the install. I did so, and there was NO opportunity to cancel the scan after rebooting. I did immediately click STOP on the GUI but by the time the GUI was on my screen so I could click, F-Prot had updated and scanned a number of files - 36 I think it was. If there had been another FP in those files then I would have had a problem like I did with ProcessGuard.

So, it is not accurate for you to state that Frisk gives an option to not do the initial scan during setup unless the setup for a person who is ALREADY A LICENSED F-Prot user is different from the setup for a trial. Plus, I want to emphasize that there is NOTHING in the install process that tells the user that a scan will be done AUTOMATICALLY ON REBOOT. That needs to be fixed along with the confusing stuff about getting a key during install if that isn't necessary and that can be done later.

 

I explained that the first time F-Prot placed procguard.exe in quarantine. The second time it did not put a copy in quarantine. I also checked Backup from the GUI and it was empty. So, how could I have restored the file? I did restore it from Quarantine the first time but there was nothing to restore the second time. Might there still be a few bugs in F-Prot? Maybe it works right the first time but if you restore the file, and it deletes it again (because either "ask me first" doesn't work right or you forgot to set it to ask), maybe there is a bug and F-Prot doesn't put it in Quarantine/backup the second time. I don't know...maybe what happened to me was a one time weird thing that will never happen to anyone else ...I hope that is the case. But I won't be sure unless I get a nasty and test F-Prot.

 

I have the 120dpi problem also. It makes no sense to suggest that someone use 96dpi instead, even if just for awhile, until F-Prot fixes this. People generally use 120dpi because they need it and they can't use 96dpi.

I'm surprised this bug is still there! I think I was the first beta tester to report the 120dpi bug to F-Prot way back when the beta began. Of course, it was a much bigger problem then and was fixed. I guess this small problem with the GUI on 120dpi just slipped by. Fortunately, I generally don't schedule tasks so it doesn't affect me like someone who always schedules.

I have NO F-Prot icon in the systray. ProcessGuard reports that "fprottray.exe" was allowed to start and ProcessExplorer says its running, but I have no icon and no way to interact with F-Prot.

Further, ProcessGuard is a bit messed up. It was fine after I used System Restore the other day so I think F-Prot is interfering with it somehow. It's minor but irritating. I cannot minimize PG to the task bar now. I also cannot right click and copy anything from PG. Another probably minor thing was that Gadwin PrintScreen did not load on reboot after I installed F-Prot. I started it manually and it seems ok but it should have loaded at boot. I have not booted another time...just the reboot after installing F-Prot.

EDIT: I rebooted again and now I have an F-Prot icon in the systray. I also have the Proxomitron icon which was also missing from the systray back and PrintScreen loaded properly. Things look good now.

 

With the impressive level of support the Frisk folks are offering here I bring the proposal to vote for F-Prot to open a forum here at Wilders and cast the first Yay vote right now...

 

Nope, that will not happen. Or in other words "That's not gotta fly" And i would kindly ask that you guys do not open for every F-Prot Question or Problem a new Thread here. Reason is being that this Forum is NOT the Support Forum for our product. With new Threads and Questions you force us to answer, what looks somehow "spammy" when the whole Other Antivirus Section gets filled with fprot topics here. Wilders hosts the Eset Forums. HOWEVER... We will see what we can do regarding this forum "problem"

 

Well lets see.

Scan at first boot after install imo is fine because you can abort all scans manually. FP are not the norm in any case and we stamp them out as soon as they are brought to our attention.

It seems I took someone's word for the feature to abort the scan at first boot after install instead of testing it myself. (Bad Supportguy bad) I then tried a fresh install and could not locate this feature myself. Again, personally I believe this feature is something that needs to be there for 99% of our home use customers.

The FP on ProcessGuard did of course start you off on the wrong foot and if you see any blatant reproducible error with the Quarantine/backup then please let me know. However we aren't aware of any error's with this feature.

The 120DPI bug is a minor graphical bug that we will fix with a automatic update when the fix has been implemented.

I'm glad to hear that everything is working fine overall. I check this forum everyone in awhile and will answer as many questions as I can.

 

Does this mean my question about eicar and F-Prot isn't going to be answered? Should I email support instead?

As for the "forum" problem, I think it would be GREAT if Frisk could set up a forum somewhere. I would REALLY like that and I think others would too although I don't know how much use it would get simply because F-Prot is not a complex, complicated AV (from the end user's point of view) and thus probably would generate a lot of questions when a new version comes out but perhaps not many after the dust settles down...so...

I do understand your point and I won't ask further questions here about problems, etc. with the new F-Prot.

 

Right now under work Most likely online later today.

 

Btw, if you want to cancel the scan at boot the just uncheck the box in the setup that is found here. Make not to read the text at the top. "To update F-PROT Antivirus for windows and run a full scan after restarting the computer..."



Its one of those unforgettable "Gotcha" moments ain't it, dint notice this at first myself.

 

Supportguy:

That screenshot with scan my computer message is really hard to see. It would be nice if there is a separate screen to allow to scan my computer. I, too, don't like the idea of the automatic scan when you first install it. Better yet, just UPDATE message would be enough.

As for the F-PROT forum, please keep us posted IC. Thank you.

 

Yeah....that is a "gotcha" for sure. It wouldn't have bothered me nearly as much if there had been no PG False Positive. I would have been a bit miffed because I don't like automatic scans after installing an AV program but I would have stopped it once the GUI loaded and it would not have been a big thing. I do understand why you feel most home users benefit from and need the automatic scan so I probably would have said nothing about it IF that FP had not happened.

Mike, let us know when you get the forum up...that is fast moving to get a forum so quickly.

 

I have brought this up during the beta stage, and hopefully have a separate enlargable scan window, similar to that of Command AV and Norman 6 beta, so that infected details including the full path can be clearly shown, but it turns out that it is still a small window in the final release.