This has only started since the last program update on Jan 21

Wait a moment, are you saying that you have not scheduled the boot-time scanner at all? That it somehow scheduled itself automatically during the update??

That would be extremely strange, I’d say…
I’ve never heard of anyone experiencing similar behavior.

Thanks,
Vlk