Also it is quite strange that PackageBoot scans all the files in the F-Secure folder even though they are not running.
Unless the package has been customized, I'm not aware of any reason that PackageBoot would be scanning any folders other than those explicitly listed in the package rule.
The exception could be that if F-Secure has a dependency on the JRE, and we killed off the JRE, the F-Secure process may have taken that personally.
Otherwise, I'd suggest inquiring with F-Secure as to what that message is driven by and why it would claim something was scanning, when it's not.
I have one Java application running all the time and your Java Update package did not notice it.
This is correct. The JRE update package only scans for the JRE files that are likely to be impacted directly by the update.
The package does not scan for any Java-based applications that are dependent upon the JRE.
If you have such applications that would be adversely affected by terminating/updating the JRE, you should customize the JRE update package to also terminate those processes.