No option to turn-off vulnerability scanner

[catdaddy]

Thank you for the clarity   As it does indeed seem that 4.0.9022 is the Version/Build that has the issue.

All the Best,

-CD

[selvan]

Hi

I was trying to replicate the problem in my PC but couldn't do so. Below is what I did

1. Chose "Do not set a Scan schedule.." under VUL Scanner schedule settings.

2. Waited for couple of days and couldn't see a prompt from McAfee

Am on VUL Scanner version 4.0.9022 and MSC version 14.0.9042

[Peacekeeper]

Mine took 4 days to happen entirely random. Currently 4 days now so waiting.

All 3 us CD, Ex_brit and I have seen it happen.

[jonnywalker]

Yesterday it did a scan by itself again. I ´ve turned of the two scanning options long time ago. First time it happened was after the update to version 9022. Then it has happened two times more. My version of the Mcafee security center is 14.0.9029 that version came 2016.05.27 to me.  So are there different versions out there at the same time ? I have Mcafee Internet security suite via Acer Affld 662.

[Peacekeeper]

The 9022 is the vulnerability scanner build not the Security Center build. that said I and going some testing for the techs.

In Vul scanner at the top does it mention next scan and a date?

[jonnywalker]

Hi

Neither of the  two options for scanning is marked. Only the third option no scheduled scanning is marked. I wondered why Selvan had security center version 14.0.9042 and I have 14.0.9029 updated to that version at 2016.05.27. And yes I knew the difference between Security center and the vul scanner.

[catdaddy]

Judging by your (Affid) # you are lagging behind a Tad, which is normal. The Latest MSC is 14.0.9042, for anyone whom subscribes directly from McAfee.

[jonnywalker]

Tonight it happened again a scan was made despite that the scheduled scan options where turned off.

[Peacekeeper]

and not a friday that ruins my thoughts re cause.

We need 1 of the mods to be able to be sure it will occur so we can log the issue. Problem is we need to determine the exact time it will occur as running the logging tool for days will fill up the drives

[exbrit]

Unfortuately it hasn't recurred on mine.