Windows 7 Hotfix repository

@burfadel Use your script to install SoLoR's pack on x86 Windows 7 SP1 and you will see that it only extract the updates but doesn't install them.

 

I had a look over the script and can't see any reason why it should work on x64 and not on x86...

 

Just try it and you will see.

 

You need to login to view this posts content.

 

Weeeellll, not really; all of a sudden v.24c, or anything after v.23, just extracts all the cabs to %Temp% and quits. Win7Ultimate x64. I upgraded to socket 2011 and now only v.23 will do it all; same OS, same install-nothing changed at that end. Absolutely no clue why.

 

What about v24d?

 

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.

 

hi,
is there any news about solor updates?

 

I think hes cheating on us with another (Windows 8)

 

You need to login to view this posts content.

 

Maybe it's easier to satisfy Windows Update than it is to satisfy us

 

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.

 

thanx for your hard work solor,
you coud also ask help from the forum members?

 

You need to login to view this posts content.

 

@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'