wscntfy.exe

[Gary Graham]

I am using GhostWall, so I have no use for the default windows firewall. I have it disabled. Now the security center wants to complain about this.
The first time the warning popped up, AD asked if I wanted to allow wscntfy.exe
I told AD to always block it. Now when I boot the system, sometimes it is initially blocked, and sometimes it does not. If it is blocked initially, then I will not see it for that session. If it was not, then the process is free to run untill I kill it. If I do that, it is not allowed for the rest of the session.

Why is it this is allowed to run sometimes, and not sometimes? It is being loaded before AD has control?

Let me know if you want me to try anything else.

Gary

[Disciple]

-{ Quote: "... Why is it this is allowed to run sometimes, and not sometimes? It is being loaded before AD has control?" }-
My personal experience with a day planner program that loads an alarm exe module is very similar to what you have just reported. I questioned Jason about this and his answer was just what you speculate, that GSS is sometimes being loaded after what we have set as blocked. Jason did say that by the release version GSS would be loading earlier in the Windows startup process. So until then we need to keep mindful of what we don't want to load and make sure when we boot/reboot to kill those that do start.

I don't think there is much else to test/try that will put more light on the situation.