Vsserv.exe hogging +80% of CPU. This appears to be a common problem. It was my understanding that this problem had been corrected from BD2009, but apparently it has not been.
Computer with problem: operating system is XP (professional), updated automatically through MS so it is current through SP3 and everything else they put out in terms of security updates, etc. Last MS update on April 15, 2011 with MS's rather large update on that date. The computer is not used for games: it is a work computer and runs MS Office 2007 with internet access through browser IExplorer 7.
This computer ran BD2009 AV until its license was close to expiring so I updated it to BD2011 Internet AV (the 3-machine license). BD 2009 AV had the same problem on XP and the patch that was suggested for BD2009 was successfully implemented during 2010. This patch involved turning off automatic BD signature update and one or two other things: I don't recall at the moment. Regardless, the patch worked for BD2009 on this computer.
(As an aside: BD2011 was successfully implemented on my Vista machine with no problems and I am typing this post in from the Vista machine.)
The installation of BD2011 Internet AV on the XP machine was done exactly per BD instructions on April 16 (yesterday). All antivirus software (i.e. BD 2009) was removed via Uninstall prior to downloading BD2011. Then the BD installer was downloaded via internet and BD2011 Internet AV was installed via the internet (i.e. the most current version). During installation, the installer wizard automatically performed a system-scan and found zero conflicts.
Immediately upon rebooting the XP machine with BD2011, it performed slowly and the "low system memory" alert came up. This machine is now virtually useless due to extreeeeeeeeemly slow operation. This is exactly the same problem that this machine experienced running BD2009 before the BD2009 patch was implemented.
I need one of two things to happen quickly: either solve this problem or refund my money. This problem was supposed to have been solved by now. It hasn't been.
Thanks in advance.