Nod32 Error Occurred While Updating Program Modules
Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Update problem Started by Boris , May 21 2013 09:22 AM eset an error occurred while downloading update files update Reply to this topic 12 replies to this topic #1 Boris Boris virus signature database update ended with an error Group: Members Posts: 28 Kudos: 0 Joined: 13-May 13 Posted 21 May 2013 - 09:22 AM Hi all, I would like to commend the look of the new forum! ESET team going in the right direction. Now about my problem. Sometimes Nod32 had to download a large file, aprox 29mb but when hi finished I get this error 21.5.2013 11:09:49 Update module Error downloading file from update server NT AUTHORITY\SYSTEM This happens in every 2 weeks. Best Regards. 0 Back to top Quote MultiQuote #2 shocked shocked Group: Most Valued Members Posts: 292 Kudos: 44 Joined: 17-May 13 Posted 21 May 2013 - 09:42 AM download the offline installerand perform a repair installation here 0 Windows 10 32-bit / 3 GB ram / ESS 9.0.349.0 Back to top Quote MultiQuote #3 Boris Boris Group: Members Posts: 28 Kudos: 0 Joined: 13-May 13 Posted 21 May 2013 - 10:11 AM Ok, Now, when I try to repair I get this 0 Back to top Quote MultiQuote #4 Danny Batenburg Danny Batenburg Group: Members Posts: 2 Kudos: 1 Joined: 16-April 13 Posted 21 May 2013 - 10:34 AM You could consider doing a completely new installation using the removal tool first? After that, try to re-install using the MSI. Also, make sure that you have proper acces to the MSI file. Edited by Danny Batenburg, 21 May 2013 - 10:42 AM. 1 Back to top Quote MultiQuote #5 Marcos Marcos Group: ESET Moderators Posts: 6,671 Kudos: 1590 Joined: 08-February 13 Posted 21 May 2013 - 10:42 AM This kind of error normally occurs if the backup msi file is deleted from the \Windows\Installer folder. I'd suggest removing ESET completely using the Uninstall tool as per the instructions here and installing EAV v6 from scratch. 0 ... www.virusradar.com . www.goexplore.net . www.welivesecurity.com ... Back to top Quote MultiQuote #6 Boris Boris Group: Members
update. How fast is your internet? Test your internet connection If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 15 Thread: NOD32 Won’t update. Thread https://forum.eset.com/topic/189-update-problem/ Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 24-06-2012,12:30 PM #1 ktee View Profile View Forum Posts Private Message Senior Member Join Date Jun 2006 Location Wellington Posts 158 NOD32 Won’t update. Had Vista reinstalled. NOD32 Antivirus 5 seemed to be working http://pressf1.pcworld.co.nz/showthread.php?125380-NOD32-Won%92t-update but the Virus signature database can’t seem to run fully. It appears from the Vista reinstall date that Under Scheduler, Log maintenance, regular automatic and system scan have worked, but “Update Virus signature database” says “Update has not been run yet”. It has tried to run automatically going round and round and it’s now changed from orange to red. Under Home .”Maximum protection is not ensured” “Virus Signature is out of date” After googling I realised that Windows Defender could be the problem as it would have been reactived by default on the Vista reinstall. So turned it off. But on NOD when I select update and manually try to start “Update Virus signature database” nothing happens. Also just tried options “Smart scan” and “Frequently used” and both say failed to run scan. Anyone any idea?? I’ve left on Windows Firewall as I read that NOD32 Antivirus 5 doesn't have a firewall, but Eset Smart Security does, and I believe I have the former. 24-06-2012,03:20 PM #2 pctek View Profile View
of the following reasons: Interruption or loss of Internet connection Data corruption on local drive Damaged ESET installation Corrupted update server files (Mirror http://www.esetscandinavia.com/support/error-downloading-update-file/ server environment) Incompatible update files (using beta ESET product to download http://donnedwards.openaccess.co.za/2011/10/esets-not-so-smart-security-failure.html from live update server) To resolve this error, perform the following steps: Verify that your Internet connection is active by visiting ESET's home page. Clear update cache by performing the following steps: Open the main program window by clicking the ESET icon next to the system clock or error occurred by clicking Start - All Programs - ESET - ESET Smart Security or ESET NOD32 Antivirus. Press F5 to open the Advanced Setup window. From the Advanced Setup tree, click Update. Then, clear the update cache by clicking Clear.... Click OK and restart your computer. Open the main program window and click Update - Update virus signature database. If you error occurred while still receive the "Virus signature database update failed" message, continue to step 3. If not, you are finished. Delete the %AllUsersProfile%\Application data\ESET\ESET NOD32 Antivirus\Updfiles folder and Charon folders. ESET Smart Security: Click Start - My Computer and navigate to C:\Program Files\ESET\ESET Smart Security. ESET NOD32 Antivirus: Click Start - My Computer and navigate to C:\Program Files\ESET\ESET NOD32 Antivirus. Delete all em0**_32.dat files. Restart your computer. Open the main program window by clicking the ESET icon next to the system clock or by clicking Start - All Programs - ESET - ESET Smart Security or ESET NOD32 Antivirus. Click Update from the main menu and click Update virus signature database. If you still receive the "error downloading update file" message, continue to step 9. If not, you are finished. If the steps above do not resolve the "error downloading update file" message, please Uninstall, restart the computer (IMPORTANT!) and reinstall your ESET security product. Quick links: Purchase | Renew | Download | Activate | Online Scanner | Twitter | Blog Products (Home users) | Products (Business users) |
incompetence." -- Napoleon Bonaparte Friday, October 14, 2011 ESET's Not-So-Smart Security Failure - Fixed Resolved: I remain a NOD32 fan, particularly after the amazing response from Shaun Norris and his team. They have fixed the problem locally, and making sure the ESET engineers improve their download process in future releases.Original Post 10/14/11: I have been a NOD32 fan for a long time, but recently I have been questioning my loyalty, particularly in the light of their very dodgy virus definition update policies. It seems they are perfectly happy to allow a PC to run with definition files that are 448 days old. Or 105 days. Or whatever. What kind of security is that!?Take a look at the screen shot at the top of the page (click on the image) to see how the software is lying to me. I installed the software two weeks ago on this Windows 7 32 bit PC, and at the time the virus definitions were updated backwards from version 6364 (20110809) to 5307 (20100723) and then later to 6516 (20111004). OK, so it had a glitch. It came right. Wrong!This morning I returned to the machine, after leaving it running by itself for 10 days. The virus definitions are back to 5307. No amount of cajoling can persuade the machine to download the correct version and not mislead me:Other versions of the software have experienced similar problems. This PC was using version 4.2.71.2 and it had an issue with the definitions, so I removed the software and installed version 50.93,0. The same thing happened on a brand new Windows 7 machine I was setting up from scratch. Other PCs running Windows 98 and version 2.7 are reverting back to July 2011.So my question is this: how can the software allow the definitions to roll backwards? How can the servers still have definition files that are 448 days old? Are they insa