WinPatrol V33.6.2015.16
https://www.winpatrol.com/winpatrol/
What’s new in V33.6.2015.16 (posted July 22nd)
Enhanced start-up logic to include more start-up programs.
Better detection of 64 bit startup and active tasks.
Better detection of 64 bit program status.
Fixes for repeat alerts.
Improved installation/upgrade.
Support for Windows 10 Edge cookies (No Spartan Cookies).
Fixes potential error when disabling/enabling startup tasks that would corrupt data on the screen.
Active Tasks page now displays all running instances of the same executable.
Ability to terminate all active tasks for the same program.
Fixed bug that would result in unwanted UAC prompts when running WinPatrol Explorer
CraigB
9886
system
9888
WARNING :
The original 33.6.2015.16 release had a bug in the installer, that could corrupt the registry.
In the current 33.6.2015.16 release made available today this has been fixed.
http://www.wilderssecurity.com/threads/winpatrol-v33-6-2015-16-released.378146/#post-2509232
http://www.landzdown.com/winpatrol-help-information/winpatrol-v33-6-2015-16-is-available/msg178034/#msg178034
But users who had already updated, can better restore their system(s) with a System Image or System Restore to a state prior to the WinPatrol update.
Greetz, Red.
DavidR
9890
I bloody hate that, keeping the same version number after a bug fix the user hasn’t got a clue what state his system/registry is in. How are they to know just what version they have. Doing a manual safe program update check from the WP+ UI gives “You have the latest version of WinPatrol.” How do they know that with the same ‘b’ build number.
As bad as avast keeping the same build number when moving from RC3 to release version with no change to the build number.
I just used a system image last night to roll back to the last avast version (10.3.2223) as I was getting system lock-ups and of course, that resulted in me re-installing the winpatrol+ update (spit).
I uninstalled winpatrol, reinstalled and got this version. See screenshot.
DavidR
9893
Bob is reporting that on manually checking there is a 33.6.2015.17 release available now. The WinPatrol Download area is now listing the latest build, 33.6.2015.17 for download.
Like one of the others in the Lanzdown topic, Corrine I don’t have the entries listed in the WinPatrol View History yesterday and the entries were not listed. So looks like I dodged the bullet.
I now have version 33.6.2015.17 installed.
And is everything starting up as it should :
Greetz, Red.
Shortly after I updated to WinPatrol V33.6.2015.16, I noticed that after Windows restart that a few tray items were missing. After a couple of days, I disabled Avast self defense and did a system restore successfully. All removed items were restored, except that WinPatrol had rolled back to the previous version. It was the only program that I had updated after the restore point. Not finding anything in my searches about a problem with WinPatrol V33.6.2015.16, I reinstalled. Immediately, I noticed that startup items were missing.
The ones I really missed were WinPrivacy Tray App and Synaptics Enhancements, which I restored by using WinPatrol’s Add at the bottom of the Startup tab. None of the removed items were showing in Options/View history, so there was no other recourse. I believe that I will do another system restore after removing WinPatrol V33.6.2015.16 and install the latest version.
SNIP> “Shortly after I updated to WinPatrol V33.6.2015.16, I noticed that after Windows restart that a few tray items were missing”
Noticed that as well.
Not normal for WinPatrol ??? ???
Synaptics function, HP Simple Pass and couple others I’ve noticed
system
9898
Tell me about WP, it was a mess >:( It bugged down my sistem so baddly that I have to go back to an image I had last week. Unfortunately I had to reinstall a bunch of programs I had installed this week. So I was out touch the whole day yesterday.
Bill is gone, Bret is in charge… Hope this is an isolated incident.
Never nice when this happens but, it can happen to everyone. 
My system Win 8.1 required a reboot for Winpatrol to show up in the system tray after the update.
After the reboot, WinPrivacy needed to be restarted manually.
