Haven't tried it yet; I just got my PC up and running etc. nice and stable-will try 24d in a bit. Tried it on 11 updates KUC said I needed and it installed them, so, I it's working correctly now-go figure! Thanks Burf' UPDATE: did a clean install, ran 24d to install all 359 updates=no autoreboot and all of them at once. It didn't process just 50 at a time, but, it did install all of them.
The updates on WU are only "security updates" and/or "updates", they are only meant to fix security holes...most here are "hotfixes", they fix small bugs and you usually dont receive these bug fixes until the next service pack comes around We dont want to waif for the next SP If Microsoft distributed all the "hotfixes" via WU they would scare away people, so if they find a bug they create a hotfix and a kb webpage so if you encounter the bug and you google it you will get the webpage and be able to request the hotfix to resolve your problem
I really hope that MS will change their strategy on their hotfixes and releases them on Windows Updates. For any admins out there who do either Citrix or RDS these hotfixes are CRITICAL and way more important than the security ones. I'd rather install hotfixes every week than to spent countless hours searching for an issue who is probably already resolved by a hotfix anyway. Thanks to Solor, Komm, Burfadel, RickNitendo64 and the rest of this community for the tremendous work you guys are doing. You really make my job easier and I can finally concentrate on more important issues.
Im not... i dont have time really and i cant be bothered much with beta, Win7 was fun when i could get beta build every 2 weeks, now its not so much, when i would need personally bug for each build... i just dont have time and when i have 2-3 hours free and i see list that i would need to go over almost 60 hotfixes i just dont want to waste that time... ill go true them soon, i promise but im working today
@burfadel refer post #4234; I updated it to show the results using 24d in a full fresh install-all updates installed to a live system. @PointZero I find using komm's utility confusing because he flags updates as required where Burf's Superseded Uninstaller calls some of them as either superseeded or LDR placeholder; KB2635500 for example: Burf will uninstall it as superseeded. Both utilities are current with roughly the same dates. Please don't get me wrong, komm's utility is also a godsend and I use it, but, cautiously; after all it is beta. Plus, I'm still learning how to use it. @komm How do I modify Copy_Files_2_add.cmd to work? Code: @echo off set Repo_Path=W:\W7\Update_repo set Update_Path=F:\WU Echo Number of Packages to ADD found: 5 Echo Copying package 1 to 5 of 5 packages to ADD xcopy %Repo_Path%\Windows6.1-KB974150-x64.msu %Update_Path%\ /y xcopy %Repo_Path%\Windows6.1-KB974674-x64.msu %Update_Path%\ /y xcopy %Repo_Path%\Windows6.1-KB2506143-x64.msu %Update_Path%\ /y xcopy %Repo_Path%\Windows6.1-KB2582203-v2-x64.msu %Update_Path%\ /y xcopy %Repo_Path%\Windows6.1-KB2635500-x64.msu %Update_Path%\ /y I only install using the cabs, never the msu-extract them first. Also, KB2506143, KB2582203-v2 are already installed in my system-why are they flagged to add- and, as mentioned, KB2635500 is supposed to be superseeded. @SoLoR We in the forums can always help doing the grunt work-just ask, and for me anyways, a little direction/instruction....always learning
I think burf's script is based on the current state of SoLoR's repo. 2635500 was changed to an LDR placeholder last week and both myself & akf posted msgs afterwards thinking that might be an error. KUC (komm) doesn't base an update's status on the repo's current state- it (he) bases it on the current state overall, regardless if the repo has been updated or not. That's why there may be a difference. KUC does have a lot of options and they should be reviewed to make sure they're what you want. As an example: 2519946 from the repo is a VM driver so, by default, KUC will flag other missing VM drivers, like 2525835, as being needed. Since I don't want 2525835, I uncheck the VMdriver option on the 2nd screen before scanning. Another thing, if it flags an update as being needed when you already have it installed, look at the branch of the update (GDR or LDR) that it's saying you need. You may have the LDR portion installed, but it may be saying you need the GDR or vice versa.
That's how its meant to work the 50 at a time (per install update session) is only with the autoreboot feature
Now there ya' go, you've got the instructions in English-my native tongue, now I have to learn how to read! Perrrrfect, thanks Burf'
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.