My opinion is that the Startup cleanup should be opt-in, rather than opt-out.


I went back to 2014 because PT X messed up my Startup programs when I left it at the default settings.

I'm sorry but I don't understand what you mean by "Startup cleanup"?


What startup programs were messed up, also what do you exactly mean by them getting "messed up"?

I meant Startup Optimizer, sorry.


When I initially installed X the day of release, I lost my audio control panel (Oxygen HD) at startup.


After doing a system restore, everything was, as expected, back to normal.


I re-installed X today, and it appears that everything is working fine. Maybe the first installation was corrupt?


Regardless, I believe all the options should be opt-in.


Anyway, I tried 'check for updates' using V. 1477, but it does not make a connection to the server.

The problem you are referring with Startup Optimizer was fixed in the last build (1480):

Bug Fix: The Startup Optimizer can fail to properly run certain software under specific conditions. If you have tried the PowerTools X and after using it, some software which usually start with your computer no longer start automatically, this bug is probably the reason. This bug fix ensures the software are run again properly during the next system startup.

However, if the issue was affecting your system, there is no need to do a System Restore, simply disabling the Startup Optimizer is enough.


Also, the Check For Update issue was fixed with build 1480: basically, with all previous versions (including PowerTools 2014 and 2013) the program used caching: if the server was contacted within 24 hours, the old data was used instead making a new connection. The idea behind this was to save our server from a flood of Check For Update calls. However, it also would result a delay up to 24 hours for users to see a new version release and occasional questions asking us why the Check For Updates doesn't work. That's why the caching was removed: starting with the latest version, every time you use the Check For Updates feature, it asks our server for new versions.

I manually downloaded and installed 1480, but the updater continues to fail to make a connection to the Macecraft server.

What do you mean by the updated continues to fail to make a connection? Does it show an error message? What does it say?

Apparently, your updates are not hosted on your server at 209.188.85.213?


I probably have wherever you host your updates blocked in my firewall.


Perhaps you could send me a PM with the update server IP so that I might make an exclusionary firewall rule?


Thanks

4 days later

OK, no problem.


I suppose I will have to manually check for and download updates.

The updates are hosted at our server macecraft.com, whose IP address is 209.188.85.213. If your firewall blocks it, you should unblock it.

Interesting...


I ran the CFMC, removed some minor things, and I noticed my AV (Kaspersky total Security) popup that it had added the Startup Optimizer to the Trusted Applications Group.


Strange, I thought, because I had disabled the Startup Optimizer.


I checked the Startup Optimizer option, and sure enough, it was set to Enabled.


Frankly, I find this troubling. If I disable an option, it should stay disabled.

jv16 wrote
The updates are hosted at our server macecraft.com, whose IP address is 209.188.85.213. If your firewall blocks it, you should unblock it.

209.188.85.213 is this page also, therefore it is not blocked.


However, the update never connects nor completes.

What I have found:


If I allow my PC to make a connection to 178.255.83.1, which resolves as ocsp.comodoca.com (Comodo Security Group?), then Power Tools X will open a https connection to Macecraft at 209.188.85.213.


If I block 178.255.83.1, no connection to Macecraft will be made by the Power Tools X updater.

Arctucas wrote
Interesting...


I ran the CFMC, removed some minor things, and I noticed my AV (Kaspersky total Security) popup that it had added the Startup Optimizer to the Trusted Applications Group.


Strange, I thought, because I had disabled the Startup Optimizer.


I checked the Startup Optimizer option, and sure enough, it was set to Enabled.


Frankly, I find this troubling. If I disable an option, it should stay disabled.

What happens is you have the Startup Optimizer option checked in the Clean and Fix My Computer, so whenever you run it, the Startup Optimizer gets enabled again.


As this can be confusing, I have now changed the way the feature works: If you have disabled the Startup Optimizer, the Startup Optimizer checkbox in CFMC will be unchecked by default. If you have not disabled the Startup Optimizer, the checkbox will be checked by default. This update will be included to the next released build, scheduled to be released later in this week.


In the mean time, to disable Startup Optimizer, do this:

1) Open the Starup Optimizer, select Disabled and click OK.

2) Next time you run the Clean and Fix My Computer, uncheck the Startup Optimizer checkbox before starting the tool

Arctucas wrote
What I have found:


If I allow my PC to make a connection to 178.255.83.1, which resolves as ocsp.comodoca.com (Comodo Security Group?), then Power Tools X will open a https connection to Macecraft at 209.188.85.213.


If I block 178.255.83.1, no connection to Macecraft will be made by the Power Tools X updater.

Most likely, your Comodo will check all outbound connections with their server first. If Comodo fails to verify with their server that connection with Macecraft is OK, they block it.

jv16 wrote
Arctucas wroteWhat I have found:


If I allow my PC to make a connection to 178.255.83.1, which resolves as ocsp.comodoca.com (Comodo Security Group?), then Power Tools X will open a https connection to Macecraft at 209.188.85.213.


If I block 178.255.83.1, no connection to Macecraft will be made by the Power Tools X updater.

Most likely, your Comodo will check all outbound connections with their server first. If Comodo fails to verify with their server that connection with Macecraft is OK, they block it.

I do not use any Comodo products.


The connection to Comodo, as far as I can tell, is initiated by the Power Tools X Updater.

Arctucas wrote
jv16 wrote
Arctucas wroteWhat I have found:


If I allow my PC to make a connection to 178.255.83.1, which resolves as ocsp.comodoca.com (Comodo Security Group?), then Power Tools X will open a https connection to Macecraft at 209.188.85.213.


If I block 178.255.83.1, no connection to Macecraft will be made by the Power Tools X updater.

Most likely, your Comodo will check all outbound connections with their server first. If Comodo fails to verify with their server that connection with Macecraft is OK, they block it.

I do not use any Comodo products.


The connection to Comodo, as far as I can tell, is initiated by the Power Tools X Updater.

Ah, in that case, it must be Windows checking from Comodo that the SSL certificate we use in Macecraft.com is valid. We use an SSL certificate for the secure connection (https instead of http) and the certificate is signed by Comodo.


So, PowerTools X attempts to connect to https://macecraft.com to check for updates with a Windows API call and while doing so, Windows also initiates a connection to Comodo to check that the https connection is secure.

<SNIP>


Ah, in that case, it must be Windows checking from Comodo that the SSL certificate we use in Macecraft.com is valid. We use an SSL certificate for the secure connection (https instead of http) and the certificate is signed by Comodo.


So, PowerTools X attempts to connect to https://macecraft.com to check for updates with a Windows API call and while doing so, Windows also initiates a connection to Comodo to check that the https connection is secure.


I had guessed that was be the case.


Thank you for confirming.


I now have the firewall rule in place, and the Power Tools X updater is working as expected.


Thanks again, and keep up the good work on Power Tools.

Might I suggest that the Startup Optimizer not be permitted to automatically re-enable itself every time the CFMC is run?


Thanks.

Arctucas wrote
Might I suggest that the Startup Optimizer not be permitted to automatically re-enable itself every time the CFMC is run?


Thanks.

You are indeed correct and this issue has already been discussed in my earlier message starting with "What happens is you have the Startup Optimizer option checked ..." and the problem has been fixed, but the fixed version of the program hasn't been released yet. The fixed version is scheduled to go out next week.