10-10-2008 07:44 AM
11-03-2008 12:25 PM
Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run "taskkill /im PTChangeFilterService.exe /f", 0, True
end I load the file on start of windows!!!
by good work
ps: accepted more best solutions
11-08-2008 06:00 AM
As it keeps crashing on my laptop (an EliteBook 6930p), I've just disabled the service.
If you want to do this too, go to Start > Control Panel > Administrative Tools > Services. Scroll down the list until you find "HP ProtectTools Service" and double click it. On the next dialog, there should be a drop-down list reading "Automatic"; change this to "Disabled" and the service should never restart. If it's running at the time, you'll want to click Stop, as well.
12-24-2008 08:34 AM
01-07-2009 05:36 AM
I left it running overnight, came in this morning and ptchangefilterservice.exe was using 113MB of ram...as it sat there doing nothing.
Reboot-already at 107 MB as I type this.
I have no problems killing the service as long as the functionality or Protectools remains for my clients.
I can't sell these until this is resolved.
CampusHP Tech Manager.
03-11-2009 01:27 PM
The exception is "System.NullReferenceException"
The source is "PTHostServices"
The stack trace is:
" at HpProtectTools.PTChangeFilter.CChangeFilter.a(Bool
The exception data is:
It looks like a classic .NET coding error, a class is trying to reference or call methods on one of its own objects that are apparently already GC'd from the class's finalizer.
Please fix this HP! Should be a simple bug to locate.
03-13-2009 02:03 AM
try to install new version of HP Protect tools from here:
This problem is fixed in the information about this version.
11-11-2011 12:53 PM
PTchangefilterservice.exe is part of HP protect tools. If it's hogging RAM, you probably have an old version. Personally, unless you use parts of Protect tools intentionally, like the credential manager, or use a fingerprint reader for logging in, I'd just uninstall it. (I don't work for HP, this advice is strictly my own). If you really want to keep it, check and see if there's a newer version you could upgrade to. The version that came on my 6735b laptop was a memory hog and also put a lot of unnecessary traffic of a type I never determined onto my wireless network, but subsequent versions fixed these bugs.