Loading Profile...
Recent activity
Subscribe to this feed
Steve asked a question in Sunbelt Software on April 28, 2009 06:12:
No definition file updates?Is there a particular reason that we haven't seen a definition file update since 5111, issued 24 Apr 09?-
Steve replied on February 23, 2009 07:42 to the problem "Update 5003 - SBAMsvc.exe clocks 100% CPU utilisation" in Sunbelt Software:
Jacob, thanks for the information. I'm going to experiment with what you suggest, but with the changes I've seen so far, I don't expect to have any more problems.
Many thanks. -
Steve marked one of Jacob's replies in Sunbelt Software as useful. Jacob replied to the problem "Update 5003 - SBAMsvc.exe clocks 100% CPU utilisation".
-
A comment on the problem "Update 5003 - SBAMsvc.exe clocks 100% CPU utilisation" in Sunbelt Software:
Hi Jacob,
Thanks for the advice. I've no other form of active monitoring running so I've disabled File & Folder checking as you suggest. This has certainly improved the issue in that I can now open and edit Excel files without having to remember to turn off AP. The time taken to open a spreadsheet is not as quick as pre the 5003 update but I can live with it. I'm interested to understand why this issue has occurred, is it because of extra workload being placed on the CPU by the updated software?
Thanks for the help so far. – Steve, on February 22, 2009 16:13 -
Steve reported a problem in Sunbelt Software on February 22, 2009 10:48:
Update 5003 - SBAMsvc.exe clocks 100% CPU utilisationSince updating to def 5003 I'm unable to run Excel (2007) spreadsheets without disabling Active Protection (AP). If I forget to disable AP, SBAMsvc.exe clocks 100% CPU utilisation and my PC effectively freezes until I am able to manually kill this process. Am aware update 5003 introduced more than just definition updates and have not yet found any other area where I suffer this problem. Running VIPRE, SBPF, Windows XP (fully patched) and didn't suffer this problem until update 5003. Ticket raised with the support desk (no reply as yet ... it is the weekend) but is anyone else experiencing the same problem?
P.S Just had a similar problem opening a new Word doc.
