Online Armor services couldn't be disabled, for obvious reasons to do the Windows clean boot , so I decided to temporary uninstall Online Armor. And, suprisingly, the Windows8. So it looks like OA is interfering with this update in some way - hence why reporting this here in order to see if you can reproduce this and get this fixed. I take it that you already had the required update KB installed in order for this particular update to install?
Unfortunately, since I uninstalled and reinstalled AO again in order to have this update working , the OA history has been purged. Another user had the same issue with this exact update. Temporary uninstalling OA fixed this as well. I am the "other user" that miekiemoes refers to - uninstalling Online Armor allowed me to install the KB update. And like miekiemoes I also had the KB update installed already. I encountered the same issue. With Win 8. Only after uninstall of Emsisoft Online Armor and at the same time the Anti Malware , the important Windows update was sucessful.
I've also had this problem on a W8. There was indeed a change during this KB update to there afaik. I can't check my history logs here unfortunately, since I temporary uninstalled and reinstalled OA, but imho, I believe that's the cause. One has to be careful to remember to re-enable things afterwards! Having this problem is a nuisance though. The initial failures happened when I was trying to apply a whole set of fixes and when Windows Update unrolled the I think only one that really had failed, it took off twelve other fixes which had also needed a restart.
I chose to be cautious and apply those one by one so had an extra 12 restarts to do before I finally found that KB had been the culprit. I'd like to know if Emsisoft have made any progress in fixing this problem. Some of the subsystems required to verify the digital signature of the update aren't loaded when the change is made, so we can't make sure that the change is made by a legitimate update or not and end up denying it.
We are working on it. It's getting annoying, mainly because it needs a pair of reboots beforehand, plus the one for the fix itself, plus a couple. For those who don't yet know, OA has now released Version 2. The last official was 31 which gives some sense of the amount of beta testing carried out.
Others using KAV may be able to help if any questions show up. The free version is as I understand it still at version 31 for now. For the past many weeks I have been one of the beta testers over at OA which has been an interesting experience. Any learnings that I got there I will be glad to provide here with the usual no promises of accuracy caveat. So that my version is the same as users here I have installed the trial 85 since I couldn't find an easy way to get v 85 to show up on my pc coming off a beta version.
TO: Mike Nash from the trial how do users put their exiting license codes in? Here is a list of 6 steps I have followed so far: 1 Uninstalled all old OA versions, including the folders and all old settings 2 Ran registry clean up, CCleaner and a defrag then rebooted as if OA had never existed on my PC.
I will record my next steps on settings and report back. Last edited: Feb 19, Escalader , Feb 19, Also I allow local host. I donot need to allow Intranet or Satellite Provider. I don't know if anybody is finding these posts here useful or not. There are other OA threads running here as well I am prepared to post how to restrict users updating exe's using UDP 53 and the matching TCP's to one and only one ip, but why bother if everybody either knows already or don't have the interest?
I'm NOT complaining just don't want to waste time. Let me know what is of interest. Escalader , Feb 20, Joined: Oct 28, Posts: Hi, Escalader If it wasn't for your posting of all this useful info, I might not have bought OA in the first place. It helped me set up OA when I first used it.
Trying to fix a computer that's having hardware issues can be very stressful. The problem, although it appeared to be a hardware problem after further checking eluded that type of solution. I tried something else. I have found that in some cases that if something bad gets into the boot sector of a Windows drive that the best thing to get it out is a Linux-type installation. I think that whatever it was might have been very bad.. Even the first install of Linux failed to clean everything up.
So I killed the partition again and started a new install of that Linux system. Afterwards I started a fresh Windows XP install in that same partition and rebuilt everything. I was not so confident that I had solved the problem. First I installed Avast expecting the same problem with Online Armor.
Ran that for a day, and then curiosity got the better of me. I disabled all of the active protections of Avast and installed online Armor. No problems with the installation or initial update of OA. The final test See if Malwarebytes would be allowed to complete it's updating process.
It did, much to my surprise. Problem solved, although what might have been the cause precisely, I suppose remains a mystery. But with everything working properly, I can't find much to complain about. You are quite welcome, we appreciate the follow-up to let me know everything is working well for you. If you have any other questions or issues arise in the future please do not hesitate to create a new topic describing your issue in detail. A friendly forum helper will be glad to assist you.
Thank you very much! You need to be a member in order to leave a comment. Sign up for a new account in our community. It's easy! Already have an account? Sign in here. This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings , otherwise we'll assume you're okay to continue.
For the above reason, we have decided to not spend any more development time on Emsisoft Online Armor , but instead focus on improving the award-winning protection of Emsisoft Anti-Malware and Emsisoft Internet Security, which we are certain have a great future ahead.
As of today, we have stopped selling Emsisoft Online Armor. New license activations will only be possible until the end of May The official end of technical support will be March 31, Though, we will still provide updates for critical issues that may be discovered until then. At the moment we can say with certainty that we will not add Windows 10 compatibility, since that requires several major changes to the codebase.
We are happy to exchange any actively used license keys of Emsisoft Online Armor to Emsisoft Internet Security for free. Please contact our support team for an individual swap offer.
0コメント