LandzDown Forum

I am not sure when it happened for the first time that my WinPatrol Icon (blue) vanished from the systray and the "WinPatrol.exe *32" process from the Windows Task Manager. It now happens regularly after about 52 minutes system uptime. If I then logout and login again, WP starts working again (I don't know whether for another 52 minutes or shorter).

It could be that WinPatrol PLUS v 30.5.2014.0:30.5.2014.0 was the last stable and fully functioning version on my system. (Could I locate the exact point in time of the first WP malfunction in the WinPatrol Report Log?) I cannot think of a remarkable event other than the change of WP version that could have caused the defect.

I am astonished that WP cannot defend itself better and I would like to know how this can happen and what I could do to cure the situation.

I should not hide the fact that although WP is started as HKLM_RUN it vanishes only in one of my Standard User Accounts. It stays alive in the Admin and a second Standard User Account.

Of course I should try to repair the defective account, all the more so as this is not the only defect of this account. However, I would like to learn from the situation first and see whether WP can be cured.


----------------------------------------------------------------------------------------------------------------
Intel Core i3 540, 8 GB RAM, 2 SATA-HDD with 640 GB each, Win7 64-Bit, MSE, WinPatrol PLUS, Fx 40.0.3 with NoScript, Tb 38.2.0 (POP3)

As I said before, the "WinPatrol.exe *32" process vanishes from the Windows Task Manager at the same time.

I do not intend to blame anything or anybody. I am only concerned that a software that is designed to defend itself against being closed, does shut down regularly and I wonder what lies behind that time interval of 52 minutes.

Of course I have tried several times to uninstall and reinstall WinPatrol - with the same result.

I thought I had posted that I would report back on the outcome of my contacting WinPatrol Support on this matter. But I cannot find this posting any more. Anyway, here are the results of that consultation:

As to the reason for my problem I was told that there is a “clean-up” process that runs around 1 hour after start-up that could result in the issue I was seeing. Upgrading to the latest version  should fix the problem.

I was told that WinPatrol 33.6.2015.18 was available which is more stable than the version I was running. So I uninstalled my version and installed the proposed one. That solved the problem.

In the context of this E-Mail consultation with WinPatrol Support I asked two additional questions. The answers may be of some interest here:

• The makers of WinPatrol prefer to have WinPatrol PLUS in HKCU run instead of HKLM run because it is installed on a user by user basis.
• They stopped using the -expressboot parameter because they found some problems in the way that code was written that was leading to repeat alerts. The savings at start-up were negligible so they decided to simply remove it from the product.