Start up Scan - never done or just not logged

Hi i am using nod32 3.0.667 and windows vista ultimate x64 sp1. in scheduler there is a task "scan files on startup". but under "last started" there is no entry. so is this just a bug in the logfile or doesnt nod 32 run the startup scan? first would be ok, second would be a problem.

maybe someone else has this recognized?

thx 4 help. leschy

 

Automatic startup task should be run after the user logon. Perhaps you meant the other startup scan task - this will be fixed in a newer version that is being tested and will be released shortly.

 

oh yes, i meant the startup scan task. the startup of nod32 itself works perfectly.

thx for your information, that means also, that the startup scan task is not running, right?

any date, when the new version will be released?

 

There are 2 startup scan tasks scheduled by default. The scan after the user logon should work fine.

 

please have a look at my attachement, both startup scans dont work. eve if i run these manually, there is no entry in "last started at". i think in previous version the startup scan worked. any idea?

 

ok here a screenshot of version 3.0.650. in this version, the automatic startup scan works fine, in version 3.0.667 it doensnt. i hope this will be fixed in the next upcoming version, its a little bit annoying for me.

 

Re: Start-up files scanning

i believe version 3.0.669 didn't fix the problem. in my scheduler is a task "automatic startup file check" which should be launched with user logon. but there is no entry in "last run" although I completely rebooted my pc. I even unchecked the box "once per 24 hours at maximum", so nod should perform this task EVERY user logon. It does NOT. It's annoying.

System: Vista Ultimate x64 SP1

Does anyone have the same situation? Does anyone have a hint how to solve this problem?

greets, leschy

 

Version 3.0.669 installed. Task "Automatic startup file check" after "successful update..." works perfectly. The other "Automatic startup file check" sould be launched "after user logon". This does NOT work for me. I started the pc 5 times and logged on 5 times, no entry in "last run". I edited the "launch time" from "after user logon" to "Every time computer starts" and wow - now it works. could anyone confirm this? And please could anyone from Nod give a statement. Maybe it is so, because its Vista x64?

 

Re: Start-up files scanning

XP SP3 --- .669 successfully Corrected (for me) the "Last Scan Date" issue with "After Successful Virus Update "event trigger" -

LAST RUN DATE After Successful Virus Sig Update was stuck on June 18 and now shows

 

Re: Start-up files scanning

Update after successful virus update works for me, too. I see u have the trigger "every time the computer starts". That works for me, too. But change the trigger to "user logon". This Option does not work for me.

 

Re: Start-up files scanning

I changed my 1st AutoStart File Check line to User Logon and the time changed Correctly when I re-booted as follows (is this the setup you meant that still fails for you?): (hope all know to single Clk the image once, then again to enlarge as needed))

 

Re: Start-up files scanning

That's exactly what I meant. Thanks for your help. For me "User logon" does not work and I do not know why. Maybe it is Vista, maybe not.

 

Re: Start-up files scanning

I did a final test and the result is: trigger "user logon" does not work, same task with trigger "when computer starts" does work.

It would be nice if someone from ESET could tell me

1. Maybe why is this so?

2. do I have any disadvantages using "when computer starts" instead of "user logon"?

Thx Leschy

 

Re: Start-up files scanning

I don't have any problems on Vista x64 SP1. I've modified the task so that it's not run only once a day, logged off and logged on - the current time was logged in the task details.

Could you make sure that UAC was disabled and you were logged with admin rights when you edited the task?

 

Re: Start-up files scanning

Well, that are two good points. I will test it and report, when I'm done.

 

OK i did the following:

1. Disable UAC, log on with Administrator account (my normal account has administrator rights, too), edit task, log off / on with Administrator account, it worked.

2. Log on with my normal account, which has administrator rights, uac is still disabled, it worked.

3. Enable UAC, log on with Administrator account, it worked

4. Enable UAC, log on with normal account, which has administrator rights, it did NOT work.

I thought, maybe my user profile is corrupted. So i created a complete new one with administrator rights. Same game again, it did NOT work.

That means to me: This task works only if either uac is completely disabled or uac is enabled AND I log on with Administrator account. Keep in mind, that all accounts have administrator rights, but only the original Administrator account works together with UAC and performing this task.

Could anyone confirm this?

Important question to Eset: Do I have any (security) disadvantages using the trigger "every time computer starts" instead of "user logon"??

Thx, Leschy

 

@Eset Moderators: Is it possible to get an answer to this question?

Regards,
Leschy

 

There is virtually no disadvantage providing that you restart the computer on a daily basis and do not keep it always on. Even in such case, a startup scan would be run several times a day after an update.

Anyway, the startup scan after user logon works even with UAC enabled, it's just not logged.