possible virtual memory problem with a2service.exe in Other Emsisoft products Posted May 19, 2016 · Report reply If a new install fixes the problem, surely someone should be curious about why? The updated product is meant to be the same as a fresh install. If it's not, surely someone at Emsi should be curious about what is wrong with the install. So, if you'll tell me which bits of the registry, any files outwith C:\Program Files\Emsisoft Internet Security and anything else that I should backup first, and then copy again after such an install, so that you guys can look at these things to see what has been changed, I suppose I could try it. I do understand the point that was made earlier, that any trusted application could have altered registry keys etc that might matter. But I don't understand why, if that's the case, "self-protection" doesn't prevent that from happening. I have another product whose author was driven mad by (naive) users constantly complaining that a component had unregistered itself. Although he knows that the problem was users running registry cleaners and deleting eveything the cleaner suggested, and explained this to such users, that did not stop the support requests. Eventually he changed the product so that, in essence, it reinstalls the licence registry keys every time it starts. It seems to me that your product could, immediately after an install, store encrypted copies of critical registry data (if indeed this is the problem) and - if not replace them, if the same entries are no longer present later on - at least log/alert saying that required registry entries have been damaged.