I have been pulling my hair out trying to figure out why some of my programs are taking an extra long time to open. Like for example “XMPlay” media player.
Well as it turns out it was “Code Emulation” under File system shield settings, Sensitivity, Heuristics Sensitivity (Normal).
After I remove the check mark from “Code Emulation” all my progrmas now open up almost instant.
So what is “Code Emulation” for? And why does it slow down the opening of programs so much?
And is it safe to disable it?
Or can you fix it so it does not slow down the opening of programs so much?
When “Code Emulation” is running it causes XMPlay to take about 7 seconds to open. With “Code Emulation” disabled XMplay open in less then a second! Almost instantly.
If the box "use code emulation" is checked and avast! detects some suspicious code in a file, it will attempt to run the code in a virtual environment to determine how it behaves. If potential malicious behavior is detected, it will be reported as a virus. Running the code in this virtual environment means that if the code is malicious it will not be able to cause damage to your computer.
So avast is checking that the file that you are executing is safe, which will mean that it takes a little longer to start.
code emulation comes into action when suspicious software/files is detected… otherwise it never interferes… at least I never saw that happen so far. Not sure what sort of stuff you run on your system.
Well, system hog. The code emulator kicks in whenever it sees a suspicious file. And yes, it usually takes a few seconds to emulate the file.
On the other hand, unless you’re actually executing the file, the File System Shield’s transient cache should be effective and should prevent the same file from being rescanned multiple times…
But it happens everytime I run these programs and “transient cache” seems to have no affect at all.At least with the 3 programs I am talking about here.
Everytime I open XMPlay or open iTunes Store and use scrollbar or add a music file to xrecode II. All slow way down when(Code Emulation)is on.
Its just a shame that this happens because I know these programs are very clean and it feels like I am running a very old computer becasue of(Code Emulation).
I was always a big fan of Avast but I have to admit this is getting very frustrating.
I am sure some other programs also open more slowly because of(Code Emulation) but the 3 above are the most obvious ones the come to mind.
Can you some how optimize(Code Emulation) to allow programs to open faster?
Am I asking for big trouble if I disable(Code Emulation)?
I’m just chiming in to confirm that Code Emulation currently ignores previous scan results with either Transient and/or Persistent caching turned on. So those two caching methods do not effect any executables, corrent? Program documentation gives no clue about that.
This is really my whole issue with “Code Emulation”.
All my programs are being scanned every single time I open them
I don’t mind if they are scanned the first time I run them but since progrmas I use are clean they should not have to get scanned everytime I run them.
I’m currently experiencing the same frustrations with programs like OpenOffice,nero,nitro pdf, and IE9. It has gotten so frustrating that my entire program files folder has been added to file shield exclusions. Both cashes are enabled. Watching the little orange ball spin isn’t very entertaining.
I’ll try a nice neat and tidy re-install tonight using all default settings and see if it gets any better.
In the mean time, could someone please give a simple one word answer to each of the following questions:
What is the default setting for the file emulation in the file shield? checked/unchecked
If file emulation is checked, should the cashes prevent repeat scanning of unchanged program files upon running? Yes/no.
A nice tidy removal and fresh installation solved my problems and answered the 2 questions:
Emulation is on by default in the file shield, and yes, caching does work with emulation on. Every is running quite snappily now with the default settings.
I use a fax softwrae called “EssentialFax” and when having Code Emulation on “EssentialFax” takes about 12 seconds to open vs 2 seconds when Code Emulation is off! http://www.essentialfax.com/
However Build 6.0.1125.0 has seemed to fix the iTunes issue with the slow scrollbar and xrecode II also seems faster now although XMPlay still takes longer to load after closing the player and then opening it again after about 10 minutes or so. However if I close XMPlay and the open it again with in a few minutes then it opens very fast! So I don’t think “transient caching” or “Persistent caching” is not working too well with XMPlay.
Infact I am happy to say “almost” all software now starts up like normal except “EssentialFax” with Build 6.0.1125.0.
But for now I will add “EssentialFax” and “XMPlay” to the Exclusions Tab.
I really hope to see (Code Emulation) optimized even more in future builds of Avast so I do noty have to add any programs to the Exclusions Tab
“transient caching” And “Persistent caching” does not seem to have much effect om my computer.
Could someone test “EssentialFax” and “XMPlay” for me please and let me know your results?
I am hoping Vik can fix this in the next build of Avast
Would it be possible to fix “transient caching” And “Persistent caching” so programs like XMPlay never have to be rescanned again at all?
Since like I said it is clean! So it not have to be scanned after the first time.
But for some reason with the current build of Avast XMPlay keeps getting rescanned even with “transient caching” And “Persistent caching” on. Same for EssentialFax!
Longer answer, it shouldn’t be needed as once scanned it would be in the transient cache for the duration, until you either get a new VPS or reboot. Only files which are guaranteed not to contain any virus infection e.g. operating system files, files signed by trusted publishers will be placed in the Persistent cache.
avast - Scan Transient and Persistent caching to speed scanning.
Use transient caching - if transient caching is used, a file that has been scanned, and in which no infection was detected, will not be scanned again the next time it is accessed. However, this is only valid until the next virus definitions update, as the file may contain an infection that was not previously detected but which may be detected based on the new virus definitions. Also, information that the file is clean will only be stored in the computer's operating (temporary) memory. This means that when the system is restarted the information will be lost, therefore the file will also be scanned again the next time it is accessed after a system restart. This box is checked by default; if you want files to be scanned every time they are accessed. this box should be unchecked.
Use persistent caching - if persistent caching is used, the information about the scanned file is stored in the permanent memory. This means it is not lost after a system restart and it is also not affected by virus definition updates. Consequently, persistent caching is suitable only for files which are guaranteed not to contain any virus infection e.g. operating system files, files signed by trusted publishers, or other files covered by the avast! whitelist. This box is checked by default; if you want all files to be scanned regardless of their trust status, this box should be unchecked.
So personally I don’t believe there is anything to fix. But you have to ensure that your setting a) populate the various caches and b) use them.
and I added the XMPlay folder.