no regular solution for this, as sheduled scans are a somewhat outdated concept.
Try "net stop fsma", but I am not sure how it will behave when you restart fsma.
In any case the scheduled scan should only "eat" idle cycles (unless you defined to also scan inside archives.
perComp is a Platinum Partner of F-Secure since 1994. Any advice or help given by me in this forum is voluntarily and to my best knowledge based on working with the products since 1997. Direct contact for customers please check our homepage http://www.percomp.de
Scheduled scan is being launched by command line scanner fsav.exe . Stopping that process will eventually interrupt appropriate scheduled scanning instance. To prevent scheduled scannings from starting, appropriate scheduled job should be disabled or deleted. In Home product you may disable it only locally. In corporate product managed by Policy Manager you either modify policies accordingly or - if you've set up a scheduled scan job locally - you have to manipulate the job the locally.
This topic has been closed due to inactivity. If you would like to discuss this topic further, please start a new post.
You can reference this topic in your post by adding this link:
Visit the Community
Check our Forums or How-to & FAQs for advice or answers
View User Guides
Refer to our getting started guides and product manuals
Talk to our Support and get answers to your questions