We have solved the »mystery«
Let us explain how we have found out the root of the problem. First of all we would like to mention that we have tried to slipstream Sophos Lancrypt Client version 18.104.22.168.msi with patch 22.214.171.124 into a single msi file, because we wanted to deploy it over the Group policy as a single msi file.
The reference for doing such a kind of “one-msi-package” is this link: http://www.404techsupport.com/2009/06/26/how-to-apply-patches-msp-to-group-polic y-deployed-software-msi/
Ok, we have created “slipstreamed-single-msi-file” which contained 126.96.36.199 and 188.8.131.52 version (all-in-one msi package). The manual installation of this msi file seemed to went fine, but somehow after the reboot »this slipstreamed version« caused Virusscan »to unlike« Lancrypt causing several performance issues.
Maybe because of the slipstreaming there were some digital signatures lost because we have combined to msi files into one? Well the strange thing is that NOD did not react on this kind of situation, but Virusscan did, soo we had quite a luck to find out that this was causing the performance issue and virusscan restarting.
Soo we did a separate installation of client and patch:
-First, we have uninstalled the slipstreamed LanCryprt and rebooted the pc.
-Then we have installed lancryprt 184.108.40.206.
-Then we have separately ran the installation of the patch and rebooted the pc.
It seems to us that problem has disappeared.