First, nice to hear form you again. As your usual manner you describe facts understandable and readable. 2506143, 999158, 999159 and 2666914 are still updates in the pre-release state (could be a reason for the strange version numbering). As i post earlier, it was not easy to implement a version check for those in KUC. All of those have to be uninstalled before you install their new version. If you do not, not all files in the system32 folder are updated with the newest version. So it was also necessary to check the version of the installed files in system32. If a user has an old version in his repo and run remove_old and then update the system would not be changed and he runs in a loop. So it was also necessary to implement a checking of the downloaded version of those files, luckily the file sizes defer. In addition 2506143 and 2666914 are only installable, if an English LP exists during installation. Note: during means, you can install those updates in non-English installations of home or prof., if you temporary add the English LP.
Burf, should we consider the VC Runtimes 2012 and/or the 2012 'additional' runtimes as for experimental use, or can we install these on any system no holds barred?
The Visual C++ 2012 runtimes are fine on any system they are only utilised by programs that are compiled for use with them. This obviously is very few programs currently, except for some experimental programs out there, but once it is released and different versions start floating around it will become more important. The additional runtime components are just the non-core C++ runtime files. The 2005, 2008, and 2010 redists actually have these files included in the main installer. The old runtime files are there just for compatibility with some programs still floating around that require those files. So yes, its safe to use no hold barred on any system
In the komm's repo, I don't find link for 271256 and 2714394 It's not yet updated? Thanks EDIT: it's OK