read winlogon.exe

[tomoz]

Bitman,

I freely admit that I am not enough techy to understand the inner workings of PG or the registry. I am quite happy to leave things on default in general though I try to follow the advice to learn more.
The point you misunderstood though is that winlogon.exe is by default protected from reading. Your quote re read access must refer to other programs, but if you look at http://www.diamondcs.com.au/pgdb/ind...s=winlogon.exe you will see that it does not normally refer to this file.

[bitman]

Let me make this simple; Don't block anything that an application you trust is attempting to do. If you do it is only likely to create a problem for you.

The key sections of the two ProcessGuard FAQ entries I posted are:

Only advanced users who understand what they're doing should block Read access.
Otherwise if you know and trust the application then give it the privileges it desires.

The most fundamental statement I can make is that using a security application you don't understand is as dangerous as not having one at all.