PA 14.00.18 load time
-
i can confirm that when i launched 2013, eset service went to 50% cpu (one core 100%) and it took around 10s for PA to start…. i just tried it out.
-
are you sure it happened all the time?
It seems to take long time once, then it stores its crc and never checks it again.but yeah, if you run it first time, it seems like everything gets blocked and nod32 takes up 60%-70% of cpu.
-
Since I have plenty of various pa.exe’s on my computer, i could easily reproduce this with Nod32… it is very very slow. I have no idea how AVs really work and what they do, but it seemed as if was checking something online.
In any case, I have reported this to Nod32 team. I hope they fix it. While it doesnt happen after the first time (at least it is not super slow), it looks pretty bad the first time you run it. People will think it is due to PowerArchiver even though we have nothing to do with it.
-
ok, soe ESET responded that this will be “fixed” tomorrow…
-
Excellent…nice to know I was not suffering another senior moment.
-
i think i will need to send them all versions in the future, unless this changes… let me know if you notice anything else with AVs. Once it decides to scan the file, it is really annoying :-).
I forgot to turn it on and went to test some compression and it was really really slow… so it turned out it went to scan few files out of selected list :-)
-
Think I’m going to have to lewave PA excluded permanently. Just has a > 20 second first load with the latest.20 beta.
It’s no biggie as I trust PA and only download it from the official site. I could always scan it manually.
-
Think I’m going to have to lewave PA excluded permanently. Just has a > 20 second first load with the latest.20 beta.
It’s no biggie as I trust PA and only download it from the official site. I could always scan it manually.
i uninstalled it from my computer, it was making everything slow… i will email them again, because it seems that i will have to for each new release.
-
Hi
Sorry to jump in on my first post, I have similar problems with very slow startup (20-30 secs) of PowerAchiver, after that first start it’s fine. It occurs on both of my PC’s using XP and Win7 64bit which both have ESET installed.
Since reading this post I have emailed ESET support (been annoying at times).Peter
-
Hi again
Good support from ESET (replied quick)
added the exclusion for PA and it works!.
which I added C:\Program Files\PowerArchiver*.*From ESET Support:
please make sure that you have the latest version of ESET software installed: http://kb.eset.com/esetkb/index?page=content&id=SOLN2788
NOTE: The latest version of ESET software is version 6
If you need to UPGRADE to the latest version, which is FREE with a current license, please refer to:
[To exclude a program or file please complete the following:
For Windows XP (Vista and 7 is very similar).
1. Click on “Start”.
2. Click on “All Programs”.
3. Click on “ESET”.
4. Click on “ESET NOD32 Antivirus” or “ESET Smart Security”.
5. Click on the 2nd “ESET NOD32 Antivirus” or “ESET Smart Security”, this will open up the ESET Control Center.
6. Click on “Setup”.
7. Click on “Enter advanced setup…”
8. Expand “Computer”.
9. Expand “Antivirus and Antispyware”.
10. Click on “Exclusions”.
11. Click on “Add” and then navigate to the folder or file that you would like to exclude.Please Note: You need to enter the exclusions like the following filename*.*
It is vital to have the wildcards at the end. e.g. c:\test*.*Peter](http://kb.eset.com/esetkb/index?page=content&id=SOLN2788)
-
Welcome to the forum Peter…:)
Many thanks for taking the time to post the useful feedback from ESET.
-
Yes, thanks Peter!
-
Hope this solves some issues relating to slow startup (first time start)
for some as it fixed my problem. It was so annoying at times clicking to open
a file and it would just hang. By that time you already clicked on it 2 to 3 times which then ran multiple instances of PA.Peter
-
Hope this solves some issues relating to slow startup (first time start)
for some as it fixed my problem. It was so annoying at times clicking to open
a file and it would just hang. By that time you already clicked on it 2 to 3 times which then ran multiple instances of PA.Peter
we will keep emailing them to add new version to their whitelist so you dont have to… it is very annoying, most people wont know to do 11. steps required.
-
I have to say no p[erformance issues with ESET other than this one. Computer just as fast, if not moreso than Kaspersky - left Kaspersky as their mods arrogant and power mad in the extreme as well as being often wrong.
-
I have to say no p[erformance issues with ESET other than this one. Computer just as fast, if not moreso than Kaspersky - left Kaspersky as their mods arrogant and power mad in the extreme as well as being often wrong.[/QUOTE]
i am so happy I dont use any :-).For me NOD32 was pretty intrusive (compared to nothing)… I have had BD 2013 for testing, as we sell it, and it wasnt as intrusive, but as I am my own master on my own computer, i dont use any AVs in general (i dont download exe’s from internet, except major applications).
I guess it is not easy for them to fight off all the evil :-)
-
OT: I wish I had the cajones to run without AV. I am very naughty on the internet and do not get much of a peep from my AVs. I am much more worried about rogue web sites that infect PCs. Infected exe’s are sooo yesterday LOL.
Both KAV and ESET do not slow down the machine at all, but KAV would not accept exceptions without nagging about them. No probs with ESET. I do not like the AVs whose interfaces have gaudy colours and do not allow detailed configuration - i.e. they are designed for noobs.
-
we got access to their whitelist ftp, so we will have to upload each new release there and it will be auto-magically whitelisted by ESET.
So let us know if you continue noticing anything :-)
-
I am still having to list it in the exclusions. I have PA 14.00.20 and had not run it at all since booting earlier. I removed the exclusion from ESET and had to wait approx 15-20 secs for the window to appear. Has this latest version been (supposedly) whitelisted yet?
-
I am still having to list it in the exclusions. I have PA 14.00.20 and had not run it at all since booting earlier. I removed the exclusion from ESET and had to wait approx 15-20 secs for the window to appear. Has this latest version been (supposedly) whitelisted yet?
it probably takes them a little bit, like a day, we uploaded 2013 b4 and 2012 official today.
