weekly scan (Blackspear) runs two instances

[Kenji786]

I am using the weekly scan with Blackspear's settings for some time now. However it always starts two scanjobs, doing the same thing, at the same time.

Since both scans require the harddisk this slows the pc down and scanning takes forever. I checked the scheduler, and only one entry is listed. Why are two instances running?

the only other items scheduled are regular automatic update and system startup check (twice:after logon and after update).

my version is 2.70.37

[Bubba]

Hello Kenji,

Just in case....would you mind looking in Windows Task Scheduler and see if there is an entry associated with Nod32 Please.

Bubba

[Kenji786]

I checked, there is only one entry there which does not belong to NOD32.

I am not sure, but i think the scans don't start exactly at the same time. I think one starts at 9.00 and the other like 9.15 or 9.30.

[Bubba]

Would you mind doing this for me Please:
Click Start > Run> and copy the below bold command into the window:

regedit.exe /e C:\scheduler.txt "HKEY_LOCAL_MACHINE\SOFTWARE\Eset\Nod\CurrentVersion\Scheduler"

Click OK to execute that command. If done correctly this will create the file C:\scheduler.txt
Find that file and upload the text file as an attachment to this thread Please.

Regards,
Bubba

[Blackspear]

{QUOTE-> I am using the weekly scan with Blackspear's settings for some time now. However it always starts two scanjobs, doing the same thing, at the same time. <-QUOTE}Do you have the setting that has NOD32 wait for 400 hours before doing another scan if missed? This prevents what I call "stacking" which is what you are seeing.

Cheers ;D

[Kenji786]

This is the content of scheduler.txt. It doesnt mean too much to me, but i see only one weekly scan.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Eset\Nod\CurrentVersion\Scheduler]
"Timestamp"=dword:0da2ee28

[HKEY_LOCAL_MACHINE\SOFTWARE\Eset\Nod\CurrentVersion\Scheduler\1]
"Params"=hex:
"Name"="Log maintenance"
"ActionCode"=dword:00000001
"ModuleID"=dword:6c504343
"TriggerType"=dword:00000002
"TriggerSettings"=dword:00016da0
"StartFailSettings"=dword:00000000
"Enabled"=dword:00000001
"LastExec"=dword:4753a1e7

[HKEY_LOCAL_MACHINE\SOFTWARE\Eset\Nod\CurrentVersion\Scheduler\100]
"Params"=hex:
"Name"="Regular automatic update"
"ActionCode"=dword:00000000
"ModuleID"=dword:31647055
"TriggerType"=dword:00000001
"TriggerSettings"=dword:00000001
"StartFailSettings"=dword:ffffffff
"Enabled"=dword:00000001
"LastExec"=dword:4755c3df

[HKEY_LOCAL_MACHINE\SOFTWARE\Eset\Nod\CurrentVersion\Scheduler\101]
"Params"=hex:
"Name"="Automatic update after dial-up connection"
"ActionCode"=dword:00000000
"ModuleID"=dword:31647055
"TriggerType"=dword:00000004
"TriggerSettings"=dword:00020001
"StartFailSettings"=dword:ffffffff
"Enabled"=dword:00000000
"LastExec"=dword:ffffffff

[HKEY_LOCAL_MACHINE\SOFTWARE\Eset\Nod\CurrentVersion\Scheduler\102]
"Params"=hex:
"Name"="Automatic update after user logon"
"ActionCode"=dword:00000000
"ModuleID"=dword:31647055
"TriggerType"=dword:00000004
"TriggerSettings"=dword:00050001
"StartFailSettings"=dword:ffffffff
"Enabled"=dword:00000000
"LastExec"=dword:ffffffff

[HKEY_LOCAL_MACHINE\SOFTWARE\Eset\Nod\CurrentVersion\Scheduler\182037065]
"Params"=hex:3c,3f,78,6d,6c,20,76,65,72,73,69,6f,6e,3d,22,31,2e,30,22,3f,3e,0a,\
3c,4e,4f,44,33,32,5f,43,4f,4d,4d,3e,0a,20,3c,53,43,48,45,44,55,4c,45,44,5f,\
54,41,53,4b,20,50,4c,55,47,49,4e,3d,22,36,43,35,30,34,33,34,33,22,20,41,43,\
54,49,4f,4e,3d,22,30,22,20,44,45,53,43,52,49,50,54,49,4f,4e,3d,22,6e,6f,64,\
33,32,2e,65,78,65,22,3e,0a,20,20,3c,44,41,54,41,3e,0a,20,20,20,3c,4e,4f,44,\
45,20,4e,41,4d,45,3d,22,46,49,4c,45,4e,41,4d,45,22,20,56,41,4c,55,45,3d,22,\
43,3a,5c,50,72,6f,67,72,61,6d,20,46,69,6c,65,73,5c,45,53,45,54,5c,6e,6f,64,\
33,32,2e,65,78,65,22,20,54,59,50,45,3d,22,53,54,52,49,4e,47,22,20,2f,3e,0a,\
20,20,20,3c,4e,4f,44,45,20,4e,41,4d,45,3d,22,44,49,52,45,43,54,4f,52,59,22,\
20,56,41,4c,55,45,3d,22,43,3a,5c,50,72,6f,67,72,61,6d,20,46,69,6c,65,73,5c,\
45,53,45,54,22,20,54,59,50,45,3d,22,53,54,52,49,4e,47,22,20,2f,3e,0a,20,20,\
20,3c,4e,4f,44,45,20,4e,41,4d,45,3d,22,43,4d,44,4c,49,4e,45,22,20,56,41,4c,\
55,45,3d,22,2f,6c,6f,63,61,6c,20,2f,61,64,77,61,72,65,20,2f,61,68,20,2f,61,\
6c,6c,20,2f,61,6e,74,69,73,74,65,61,6c,74,68,2b,20,2f,61,72,63,68,2b,20,2f,\
63,6c,65,61,6e,20,2f,63,6c,65,61,6e,6d,6f,64,65,20,2f,64,65,6c,65,74,65,20,\
2f,68,65,75,72,2b,20,2f,6c,6f,67,2b,20,2f,6d,61,69,6c,62,6f,78,2b,20,2f,6e,\
74,66,73,2b,20,2f,70,61,63,6b,2b,20,2f,71,75,61,72,61,6e,74,69,6e,65,20,2f,\
73,63,61,6e,62,6f,6f,74,2b,20,2f,73,63,61,6e,6d,62,72,2b,20,2f,73,63,61,6e,\
6d,65,6d,2b,20,2f,73,63,72,6f,6c,6c,2b,20,2f,73,66,78,2b,20,2f,75,6e,73,61,\
66,65,20,2f,75,6e,77,61,6e,74,65,64,20,2f,77,72,61,70,2b,22,20,54,59,50,45,\
3d,22,53,54,52,49,4e,47,22,20,2f,3e,0a,20,20,3c,2f,44,41,54,41,3e,0a,20,3c,\
2f,53,43,48,45,44,55,4c,45,44,5f,54,41,53,4b,3e,0a,3c,2f,4e,4f,44,33,32,5f,\
43,4f,4d,4d,3e,0a,00
"Name"="Weekly Scan"
"ActionCode"=dword:00000000
"ModuleID"=dword:6c504343
"TriggerType"=dword:00000003
"TriggerSettings"=dword:01039918
"StartFailSettings"=dword:00000000
"Enabled"=dword:00000001
"LastExec"=dword:47543d2b

[HKEY_LOCAL_MACHINE\SOFTWARE\Eset\Nod\CurrentVersion\Scheduler\3]
"Params"=hex:3c,3f,78,6d,6c,20,76,65,72,73,69,6f,6e,3d,22,31,2e,30,22,3f,3e,0a,\
3c,4e,4f,44,33,32,5f,43,4f,4d,4d,3e,0a,20,3c,53,43,48,45,44,55,4c,45,44,5f,\
54,41,53,4b,20,50,4c,55,47,49,4e,3d,22,36,43,35,30,34,33,34,33,22,20,41,43,\
54,49,4f,4e,3d,22,32,22,20,44,45,53,43,52,49,50,54,49,4f,4e,3d,22,46,69,6c,\
65,73,20,72,75,6e,20,61,66,74,65,72,20,75,73,65,72,20,6c,6f,67,6f,6e,20,22,\
3e,0a,20,20,3c,44,41,54,41,3e,0a,20,20,20,3c,4e,4f,44,45,20,4e,41,4d,45,3d,\
22,74,68,72,65,61,64,5f,70,72,69,6f,72,69,74,79,22,20,56,41,4c,55,45,3d,22,\
46,46,46,46,46,46,46,45,22,20,54,59,50,45,3d,22,44,57,4f,52,44,22,20,2f,3e,\
0a,20,20,20,3c,4e,4f,44,45,20,4e,41,4d,45,3d,22,73,63,61,6e,5f,6c,65,76,65,\
6c,22,20,56,41,4c,55,45,3d,22,38,30,30,30,30,30,44,43,22,20,54,59,50,45,3d,\
22,44,57,4f,52,44,22,20,2f,3e,0a,20,20,3c,2f,44,41,54,41,3e,0a,20,3c,2f,53,\
43,48,45,44,55,4c,45,44,5f,54,41,53,4b,3e,0a,3c,2f,4e,4f,44,33,32,5f,43,4f,\
4d,4d,3e,0a,00
"Name"="System startup file check"
"ActionCode"=dword:00000002
"ModuleID"=dword:6c504343
"TriggerType"=dword:00000004
"TriggerSettings"=dword:00050018
"StartFailSettings"=dword:00000000
"Enabled"=dword:00000001
"LastExec"=dword:4753a1a7

[HKEY_LOCAL_MACHINE\SOFTWARE\Eset\Nod\CurrentVersion\Scheduler\4]
"Params"=hex:3c,3f,78,6d,6c,20,76,65,72,73,69,6f,6e,3d,22,31,2e,30,22,3f,3e,0a,\
3c,4e,4f,44,33,32,5f,43,4f,4d,4d,3e,0a,20,3c,53,43,48,45,44,55,4c,45,44,5f,\
54,41,53,4b,20,50,4c,55,47,49,4e,3d,22,36,43,35,30,34,33,34,33,22,20,41,43,\
54,49,4f,4e,3d,22,32,22,20,44,45,53,43,52,49,50,54,49,4f,4e,3d,22,52,75,6e,\
20,73,79,73,74,65,6d,20,63,68,65,63,6b,20,61,66,74,65,72,20,75,70,64,61,74,\
65,22,3e,0a,20,20,3c,44,41,54,41,3e,0a,20,20,20,3c,4e,4f,44,45,20,4e,41,4d,\
45,3d,22,74,68,72,65,61,64,5f,70,72,69,6f,72,69,74,79,22,20,56,41,4c,55,45,\
3d,22,46,46,46,46,46,46,46,45,22,20,54,59,50,45,3d,22,44,57,4f,52,44,22,20,\
2f,3e,0a,20,20,20,3c,4e,4f,44,45,20,4e,41,4d,45,3d,22,73,63,61,6e,5f,6c,65,\
76,65,6c,22,20,56,41,4c,55,45,3d,22,38,30,30,30,30,30,31,45,22,20,54,59,50,\
45,3d,22,44,57,4f,52,44,22,20,2f,3e,0a,20,20,3c,2f,44,41,54,41,3e,0a,20,3c,\
2f,53,43,48,45,44,55,4c,45,44,5f,54,41,53,4b,3e,0a,3c,2f,4e,4f,44,33,32,5f,\
43,4f,4d,4d,3e,0a,00
"Name"="System startup file check"
"ActionCode"=dword:00000002
"ModuleID"=dword:6c504343
"TriggerType"=dword:00000004
"TriggerSettings"=dword:00030018
"StartFailSettings"=dword:00000000
"Enabled"=dword:00000001
"LastExec"=dword:475439ea




{QUOTE-> Would you mind doing this for me Please:
Click Start > Run> and copy the below bold command into the window:

regedit.exe /e C:\scheduler.txt "HKEY_LOCAL_MACHINE\SOFTWARE\Eset\Nod\CurrentVersion\Scheduler"

Click OK to execute that command. If done correctly this will create the file C:\scheduler.txt
Find that file and upload the text file as an attachment to this thread Please.

Regards,
Bubba <-QUOTE}

[Kenji786]

I have it set to: if it fails, run as soon as possble. I think I changed this from your recommended settings to try and see if that would fix this. I reckoned it would now run asap, so by next week only one instance should run.

{QUOTE-> Do you have the setting that has NOD32 wait for 400 hours before doing another scan if missed? This prevents what I call "stacking" which is what you are seeing.

Cheers ;D <-QUOTE}

[Blackspear]

{QUOTE-> I have it set to: if it fails, run as soon as possble. I think I changed this from your recommended settings to try and see if that would fix this. I reckoned it would now run asap, so by next week only one instance should run. <-QUOTE}Try setting it back to 400hrs as per the Tutorial, I think it will resolve what you are seeing.

Cheers ;D

[Kenji786]

Thanks. Just did, and will see upon next scan.

{QUOTE-> Try setting it back to 400hrs as per the Tutorial, I think it will resolve what you are seeing.

Cheers ;D <-QUOTE}