After a lot of research, development and beta testing we are finally releasing Process Guard v1.200 to the public. This version is a lot better than previous versions of Process Guard , especially in regards to stability. This version adds a lot of new protection to make your system even more secure, including rootkit installation protection and leaktest blocking.
The free version of Process Guard has also been updated and can be downloaded at Process Guard's homepage.
The following is general list of some of the things changed since v1.150
[NEW FEATURES/ENHANCEMENTS]
-Added "Block Driver/Services" protection along with an allow list for certain programs. This blocks rootkits from being installed.
-Added "Block Global Hook" protection along with an allow list for certain programs. This blocks certain leaktests from working.
-Added Splitter Resize so you can adjust the log and protection list size.
-Added better Right-Click menu on the Systray icon to provide all the options from the main menu.
-Enhanced output of Window Log to be easier to read.
-Optimized the Window and File Log code.
-Everything in Window Log is now shown in File Log
-DAY and MONTH now appear in the Window/File Log.
-"Set File Log Path" now shows the filename and directory of the old log file.
-Made END TASK give an alert when it happens and which application is trying to do it.
-Optimized the drivers initialization to be faster. [DRIVER]
-Optimized undocumented method of getting the name of processes. [Driver]
-Optimized code in process comparison tests. [Driver]
-Helpfile additions and changes.
-Now display "in program" tooltips to explain each protection option to the user.
-Process Guard's stability and compatibility increased immensely.
-Hundreds of small tweaks.
[BUGS FIXED]
-Issues in driver causing Cannot attach errors randomly [DRIVER].
-Random and rare rebooting issues [DRIVER].
-Close Message Handling sometimes keeping a handle open to pguard.dat.
-Close Message Handling timing issues.
-Fixed Window position/size and Listview Column order/size saving code.
-DOS/SHORT path names now get resolved correctly. [DRIVER]
-Driver protection not being enabled correctly on some reboots due to timing condition. [DRIVER]
-Fixed File Log sometimes not being written to.
Spread word of the release and have a good weekend!
-Jason- "
(Probably the best $19 I've ever spent). Pete
Compaq Presario 7110US, 1.3GHz ThunderBird, 1GB RAM, 160GB HD, WinXP Pro w/SP2, TDS-3, WormGuard, Port Explorer v2.0, Process Guard v.3.150, The Cleaner Pro v.4.1 b.4252, TrojanHunter v.4.2 b.908, NOD32, XP ICF, ALL javacool programs, SBS&D, SPYCOP, Opera v.8.0 Build 7561, FireFox v1.0.4, ShadowUser v.2.5, SpyBlocker v8.7, RegDefend v1.300
Many thanks for this as I tried the previous version but had theerror message after installing. I now know this was OK to have but it did worry me. I have been intending to go back and download the full version as I love TDS-s but now the completely new version is out I am going to get this tonight
I was at the site looking at the various screenshots; I know I want to protect all my security processes but see that there area lot of Windows services etc I can use this for but am concerned incase I protect the wrong things Are there more details in the help file as to what is the best way to configure the full program?
I would like to have this setup to the best possible configurations, just a little unsure what is best to do first
Basically, I just threw everything and the kitchen sink - defensive program-wise - into PG's list (all the exe's, that is - see screenshot).
When you first install the program, make sure you let it add all the default processes to protect (it saves you some time and they're all vital processes).
When you come to the "Protection"/"Protection General Options" screen, I've put checkmarks in all of them and everything seems to be working fine - however, any specific questions you have about anything you're seeing in your logs should be posted at:
Wilders.org ProcessGuard forum for clarification. You can also get many useful tips there on different things to add and handling specific apps as far as their permissions go.
Reading the included "Help" file from end-to-end is just about a "must" here, or you're not going to know what's going on or what you're seeing. HTH Pete
Thanks again for this extra information (much needed)
Hopefully if I get the install correct and everything works as yours has then I will be able to take time to read the help files as I definitely do need to understand what is happening and why!
Thanks for the screenshot too; I think I will wait to install tomorrow when my mind is a lot clearer than it is tonight.
I will visit the forum for extra advice; thanks to you fo all of this information, I just hope mine runs as smoothly
Hey, when it's something this good, it's a pleasure to post about it.
I also might mention this - some programs already have their own methods of "hiding" from process killers. I have a couple of these on my computer at the moment - a trial version of TrojanHunter and a fully registered version of The Cleaner.
In both cases, I've either not used (as in The Cleaner's Stealth Mode/TC Mode) or actually disabled (as in re-naming TH's "THSec.dll) them so that PG could do the job, instead. Less confusion, lesser amounts of (possibly conflicting) processes running to accomplish the same thing. Pete
Just tried the link as I was at the Diamond forum reading about PG when this post became active. I am not sure if it's just me but I get page not found.
I know what you mean about having to re-name folders as this was something I only found out about after installing TDS-3. DCS then recommended PG to protect TDS at least. Considering all that is happening today everything needs to be protected.
When on the forum I noted that you need to disble protection when installing Windows updates and any installation. I will have to remember this before heading off to Windows Update or any updates Just thought do you disable PG when updating your AV? What happens if this updates automatically?
The answer to your other question (about updating AV's, etc.) is - it doesn't affect anything to leave PG running when you do those.
Don't know whether you were around a lot or not yesterday, but it was nutso out there - everything I have on here updated at least once - most of them two or even three times yesterday. PG was running through all of it and nothing was impeded (have since scanned with ALL of them).
The instructions to disable PG before M$ updates is sound and SAFE advice (you never know what M$'s going to do, or how they'll do it that might be at cross-purposes to how PG works).
Pay particular attention to this thread: Tips&Tricks thread (that wghole forum would be good to watch, actually, as new things are discovered about what PG can and can't do - and how to make sure you're doing things right). HTH Pete
Compaq Presario 7110US, 1.3GHz ThunderBird, 1GB RAM, 160GB HD, WinXP Pro w/SP2, TDS-3, WormGuard, Port Explorer v2.0, Process Guard v.3.150, The Cleaner Pro v.4.1 b.4252, TrojanHunter v.4.2 b.908, NOD32, XP ICF, ALL javacool programs, SBS&D, SPYCOP, Opera v.8.0 Build 7561, FireFox v1.0.4, ShadowUser v.2.5, SpyBlocker v8.7, RegDefend v1.300
Thanks Pete, this is just my type of thing as I do like to know a lot about a program and how others are suing it to make sure I use it correctly (full notebook ) I have been back and forward to their forum keeping notes.
This morning I was deluged with updates to all the security programs I am running. My AV has had a few updates today due to the latest crisis that is why I wondered about PG's reaction to this.
I will definitely remember Microsoft's are best to keep PG disabled for. I will be back to the link tomorrow as it's night time over here and I am ready to shut down now.
Thanks again - you are certainly are a good advocate for PG