| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 112379 | 2010-09-03 03:27:00 | Nod32 issue this this morning.... | SolMiester (139) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1134291 | 2010-09-03 03:27:00 | Had about 4 PC's doing odd sh*t this morning...found the culprit 3 Sept 2010 Virus Signature Database Update 5418 may cause an "ekrn.exe" error in ESET software Virus Signature Database Update 5418, released on September 2, 2010 at 6:00 AM US PST may cause an "ekrn.exe" error in ESET software which xan in some cases lead to systems not responding and threat notifications with blank name fields. At 8:00 AM US PST, Virus Signature Database update 5419 was released In most cases, restarting the affected computer and updating your ESET security product will resolve the issues. Detailed information has been provided by ESET here. |
SolMiester (139) | ||
| 1134292 | 2010-09-03 03:28:00 | You're lucky it was only 4 PCs :) I got to the office and over 10 clients were down, have been restarting servers all morning. Good work ESET!!! |
WarNox (8772) | ||
| 1134293 | 2010-09-03 03:31:00 | Awhhhhhh Thats a possible reason this thing wouldn't go on the internet first thing this morning - real strange, no error messages. Went and had breakfast, rebooted, and all was fine with a new update of Nod as well. At least they fixed the problem fast. |
wainuitech (129) | ||
| 1134294 | 2010-09-03 04:25:00 | Virus Signature Database Update 5418 may cause an "ekrn.exe" error in ESET software Virus Signature Database update 5419 was released . Mines still on 5410, doesn't update until Sunday. Lucky for me. |
pctek (84) | ||
| 1134295 | 2010-09-03 08:26:00 | Yup, all our clients had problems if they got to work too early and got the faulty 5418 def. Some missed it as they only turned on their machines after 5419 had been released. It seemed to effect some computers more than others. |
CYaBro (73) | ||
| 1134296 | 2010-09-03 08:31:00 | mine's stuck on 5417 anyone else? |
GameJunkie (72) | ||
| 1134297 | 2010-09-03 10:23:00 | Mine updated to 5419 without any problems. | Zippity (58) | ||
| 1134298 | 2010-09-04 08:29:00 | Ours are all 5421 currently | paulw (1826) | ||
| 1134299 | 2010-09-04 23:25:00 | Good to know it isn't just Comodo that does things like this! (Remember the one that caused the XP start menu to not respond half the time?) |
Agent_24 (57) | ||
| 1134300 | 2010-09-06 00:41:00 | Dont think i had any problems with 50 odd clients and 1 server (touch wood) Did have the odd pc that could browse the network but not get on the net, a reboot fixed them, now running 5425. |
Gobe1 (6290) | ||
| 1 2 | |||||