Questions on automatic checking for updates

At the very end of the KLCP installation setup, it has choices for whether to automatically check for updates, how often, and whether to check for "minor updates". I have two questions:

1) After I choose the update settings during installation, how do I change the update check settings? When I looked in the Codec Tweak Tool, all I could find was the "KLCP update check" button, which does a manual check for updates and doesn't let me change how often it automatically checks on its own.

2) What is the definition of a "minor update"? I had told it to check every week but not give me minor updates, and even after almost three weeks it did not notify me that version 11.1.0 had been released. Does that mean non-minor updates would only notify when version 12.0.0 comes out? They seem to release complete installers for every X.Y.0 release and update installers for X.Y.Z releases, so I would have thought the "minor update" notification would include both complete and update installers, while "only major" notifications would be for complete installers.

It is currently only possible to change the update frequency in the installer or when the automatic update check notifies about a new version.

Normal updates are those for which a complete installer is available. Minor updates are the ones for which only the update pack is available.

Windows Control Panel > System & Security > Administrative Tools > Schedule Tasks > Task Schedular Library
There you can see the update check task. You can manually adjust the frequency there. You can also see when it has last run.

The notification screen automatically closes after a while, so it is possible that you have missed it. I am also not sure if it retries if the computer was turned off.

Okay, thanks for the info -- I'll have to troubleshoot what is going on with my computer.

Being able to review/change the check-for-updates settings would be a good feature to add to the Codec Tweak Tool -- I would just change the "KLCP update check" button to show the settings while checking for updates at the same time.

Is there a program I need to give permissions for in Windows Firewall in order for the automatic update check to work? I don't see anything in the K-Lite Codec Pack directory that is a stand-alone update checker.

codectweaktool.exe is used for update checking.

Interesting - I don't see it listed in Task Scheduler. Is it triggered by running MPC-HC?

The name of the task is "klcp_update". If you don't see it, then it means the task wasn't created.

If you install the 11.1.3 update, then you can adjust the update frequency with the CTT.

I'm running 11.1.3 and my update frequency is "never". Every time I change it (even running CTT as administrator) the change doesn't stick -- when I look at the setting again, it is back to "never". Also, I noticed that there is only a button for "close" on that setting instead of the usual options of "apply", "apply & close", and "close", which makes me wonder if the update forgot that dialog box needs to be able to save settings now instead of just manually checking for an update.

Okay, what's also odd is that the check-box for "minor updates" DOES stick when I change it. But the frequency still doesn't.

It applies automatically if you change the setting. It currently always shows "never" if you re-open. Just ignore that, the task itself is correct. It will be fixed to show the actual frequency.

Well... I installed the 11.1.4 update and now it does remember the update frequency setting, but regardless, there's still no update checker listed in the Task Scheduler.

Strange. Which version of Windows do you use?

Windows 7 Ultimate x64. And I'm the administrator account on the computer.

Is there a name I should look for in the Task Scheduler? I've rechecked the list from top to bottom several times but if there's a specific name to look for then I'd be absolutely certain it isn't there.

Its name is "klcp_update".

Well... I just tried it on a 2nd computer, and there's no klcp_update there either.

Found the problem. Apparently it requires different date formatting for different locales. Will be fixed in next version.

Awesome.

Yep, it works now.