![]() |
|
#1
|
||||
|
||||
|
On January 16th, 19:31:52 NOD updated to def file 2799. An hour later NOD updated again...to def file 2799...
How can this be? |
|
#2
|
|||
|
|||
|
Perhaps the first update was not applied correctly and that is why NOD32 downloaded/installed it again ...
|
|
#3
|
||||
|
||||
|
Quote:
The same thing happens here... |
|
#4
|
||||
|
||||
|
Quote:
Did your first update not go as planned as well (like HiTech_Boy suggests)? |
|
#5
|
||||
|
||||
|
Quote:
NOD32 did show a succesfull update balloon the first time. |
|
#6
|
||||
|
||||
|
Quote:
Not that I know! My update are made automatically so I only see the ballon indicating that an update have been made with the info of the update. I have seen at around one hour of intervalle two balloon indicating to me that my NOD32 have been updated and both time the definition number were 2799 ![]() |
|
#7
|
|||
|
|||
|
Quote:
I can only suggest you reinstall NOD32 2.7 should this happen again |
|
#8
|
||||
|
||||
|
Quote:
Let's hope that's not necessary. And it seems other people have the same problem as well. |
|
#9
|
||||
|
||||
|
Quote:
Why should we reinstall NOD32 2.7 for an update problem that might not be from our part? |
|
#10
|
|||
|
|||
|
Quote:
"might not be" , I don't know for sure what caused this problem so reinstalling generally fixes most issues |
|
#11
|
||||
|
||||
|
My NOD 2.7 just checked for automatic updates again (is set to hourly check-ups) and this time it didn't update (which should be okay since 2799 is the latest def file).
@Atomas31: How did your auto update go? The same as mine? |
|
#12
|
||||
|
||||
|
Quote:
Hi Stijnson, The problem didn't get back for update 2800 and 2801... Things seems back to normal again ;-) |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|