Resolved Can anyone using 1511 64-bit try to start them and tell me if they work?

I am using Windows 10 Version 1511 64-bit.
http://members.tripod.com/~randy_hall/download.htm
Please click on 'Primo' above and then unzip it.
chkunin-x64-ANSI and Regshot-x64-ANSI cannot be started at my end.
Can anyone using 1511 64-bit try to start them and then tell me whether they work?
Yesterday I emailed the author telling him the problem. Today he told me that he used 1511 32-bit, and the x86 versions worked properly.

 

Why do you think you need this program??
I don't think anyone would want to open an unknown program in case of Malware/virus or the likes.
I Googled and can't find any info on it.

 

See http://www.portablefreeware.com/forums/viewtopic.php?t=8164
I used it in Windows 7. It was very useful and contained no malware/virus or the likes.

 

I tried both 32-bit and 64-bit, but no luck.

 

Yes, definitely.

 

I've downloaded and opened the program using my SSD with W10 1511 build 10586.29 and all was OK.

 

I restored Windows to a point at 10/12/2015 14:29:46 Windows Update (Major update), then Primo worked properly, but it failed again after a reboot, before which I did nothing to my computer.

 

@Matthew - Please don't take this the wrong way but I note you have an inordinate number of problems, and strange problems at that, with your computer systems. I suspect you bring most upon yourself because you keep trying to fix something that is not broken.

You don't need Primo. All you need to keep Windows 10 secure is to keep W10 fully updated, use a decent and updated anti-malware solution (I use Windows Defender with MBAM, and Windows Firewall on all my systems) and don't be "click-happy" on unsolicited downloads, attachments and links.

If this were a great program, it would be widely publicized, and more importantly, easy to find with Google. It is neither. And that should raise some big red flags. There are broken links on the author's web page - that indicates a lack of professionalism to me. And once you finally do find your way to www.tripod.com, there is nothing there about this program because the program has no affiliation with any company! More red flags!

In addition to the security setup I mention above, I recommend you check out WinPatrol. This will monitor your startup programs and notify you if something new wants to start with Windows. And I note that right now, the PLUS version is 40% off at only $17.97 for a lifetime license. Well worth it, IMO.

 

@ Bill. I think there is misunderstanding. Primo is not security software but a program installation monitor intended for complete and thorough uninstallation.

So far, I have never had a security problem with my computer.

 

Such programs are often considered security type programs. And while the focus of my reply may have been on security, it applies to 3rd party "utility" programs as well. So again, you are trying to fix something that is not broken.

Windows 10 is not XP. What used to be required tweaking with XP may actually be detrimental to W10. W10 is much better at managing everything, including program installations (and uninstalls) than previous versions of Windows. As are most mainstream programs and utilities - which Primo clearly is not.

Your call. But my advice is to NOT install or use that program.

 

Do you use the free or the commercial version of Malwarebytes Anti-Malware?

 

On my two main systems, I use the commercial version of MBAM, MBAM Premium. On my other, systems, I use the free version. The primary difference is the Premium version has real time monitoring. So on my other systems, I just have to remember to periodically start a manual scan.

I have been using Windows Defender (or it's Windows 7 predecessor, Microsoft Security Essentials) on all my systems since Windows 7 came out in 2009 after giving up on AVG and Avira for being too bloated and bogging down my systems. And I have been running supplemental scans with MBAM just to make sure MSE/WD or me (the user is always the weakest link in security) did not let something slip by. And MBAM has never detected anything.