Thats correct, the uninstaller is based on the SoLoR update list, with the date corresponding to the SoLoR repository date.
@ricksteele Why is KUC beta: I am the only tester of the program and -as anybody who does something- I make mistakes. One of the worst errors could be to advice the user to uninstall a needed update and make the system unusable. So maybe the utility will never leave the beta state. As a programmer, I know that every program has errors, some of them will never occur, some after a long time. I have a program that runs fine for about 10 years without any issuers, after that it ran in an endless loop. How to use copy_files_2_add.cmd: What it does: It copies the needed files from an update repository to an installation folder. Form this folder, you could run SoLoR’s “update.cmd” command to install all the updates you need. Therefore, you do not have to pick them one by one. How to modify: Let’s say you collect all windows updates in the folder c:\windows_updates and want to install the missing updates on your system. 1.make a folder c:\wu 2.change W:\w7\update_repo to c:\windows_updates 3.change F:\wu to C:\wu 4.run copy_files_2_add.cmd 5.copy SoLoR’s update.cmd into the c:\wu folder 6.run SoLoR’s update.cmd If you only save the cabs in your C:\windows_updates folder you must change all “.msu” to “.cab” in the batch. In addition you have to modify SoLoR’s update.cmd or just install the cabs as you did before. (The next version of KUC will separate the needed updates in a "normal" and a "LDR" subfolder)
also there are some new hotfixes: 2675469 replaces 2654347 (.net) 2672277 iis 2675049 .Net 4.0 2607393 visual studio 2010 2608539 visual studio 2010 vcredist --------------------- Thanks for all the positive responses to my program.
KUC UpdateChecker-Beta-v.0.6.015.024.zip I only said that because it is the common nomenclature programmers use to identify their work as unfinished in the sense that it is not what they feel is final-excluding timely/required updating as circumstances arise: ie: Burf' labels his update installer as beta when he wants more testing before finnalizing it with all features etc. included; and the title of the download is UpdateChecker-Beta Thanks for the RSS feeds-they work great.
Rick, could you please check out the new dotNetFx40_Full_x86_x64_Slim.7z package SoLoR put up (I think he applied your new MSTs didn't he)? When I use it, I can't succeed at making a silent installer out of it. I use your little silent installer maker package for it, but when I drag and drop the .7z file onto the .bat file, the result is a file of 111kb in size. When I switch to the older dotNETFx4 package it works just fine (same updates, etc.). I double-checked all the internal file names and checked the config.txt files and everything matched. This is for Client-only installer, btw. Thanks EDIT: never mind Rick, it appears I got some files mixed up inadvertently.
@Trinket - I have no problem making silent net installer using Solor's latest slimmer for client & rick's latest net maker.
Never mind pegasus80, I got some files mixed up I think, it's working now That's what I get for doing 7 things at the same time
Since everybody seems to wait for a new update list I published my (unfinished) update-list. To make it quick: no release notes this time. Just a quick-shot. [I hat that.] All new updates needed for Win7 are in my "updates for the W7 only repo" I come back to the help you offered. Maybe somebody can create a list of updates that are at SoLoR and that are superseded now. Something like "added" and "removed" Just feel free to work, should not be so much hard work using my list. Sorry I have no time for that now.
I wait for it for the uninstaller, as its easy base point for the uninstall lists. If I do it separate, people may not have the latest updates I do agree though that to assist SoLoR a complete list of new updates (including a pack with just the new updates for x86 and x64) and a list of superseded updates would be greatly advantageous, then all Solor would have to do is upload the extracted pack and remove the old files... (its the sorting and requesting that takes the most time and effort). These large update releases are now monthly from Microsoft, or at leas thats how it has been the last several months.