Windows 7 Hotfix repository

Burfadel, given that the repository is a constantly changing collection (which would make it kind of hard to put any absolute statement over it), would it be possible for you to put it into simple terms how your above points apply to it? I know it's kind of an impossible question, but if you integrate all current repository updates with an sp1 iso, do you foresee any problems doing this? I can see you've been trying to explain the LDR vs GDR difference, but honestly I can't really gauge how this would flesh out when making an integrated iso with these updates. Thanks.

 

You can integrate updates as LDR, there is an automated integrator that enables you to do this, but the name of it escapes me at the moment.

The issue with GDR and LDR is basically if you want to install all the updates from the repository to be up-to-date, think of the following situation:

You install an update which has file versions 6.1.7601.17555 for the GDR version, and it also has the LDR version of the same update, 6.1.7601.21555. This update replaces a previous update in the repository that updates the same file. The LDR version of this update includes the changes in the older update, plus any other changes and update alteration. The older update has file versions 6.1.7601.17222 and 6.1.7601.21222. If you install just the newer update, the file version 6.1.7601.17555 is used. If you lated install the older, superseded update, the old update puts its useless files in the winsxs folder, but the file actually utilised is the 6.1.7601.21555 file!

Installing GDR versions does not serve the purpose of staying up to date, it only serves the purpose of fixing the issues relating to the associated kb article. The essence of the repository is to accumulate all the non-superseded updates, and from there you can selectively choose the updates you wish to install, or you can install the whole lot. Installing the whole lot suggests that your intention is to be as up-to-date as possible, and as the above example shows this can only be achieved by using the LDR versions where available.

Don't get me wrong, there's nothing wrong with just installing them all, just that you won't be completely 'up-to-date'... If the LDR argument worries you, keep in mind that in any case there are several LDR versions installed anyway when you install the whole lot.

 

I installed this Update, but the version is 6.1.7601.17530 (GDR?)


About Updates GDR and LDR, how to be sure you install LDR Updates?
Me, I only install the Updates of SoLoR's repository

I have not really understood how that Updates "LDR"
if, for example, in the repository, some Updates are GDR

thanks

 

You need to login to view this posts content.

 

thank you very much for your explanation, so I tested your "installer"

I first removed the Update KB2487292, reboot the PC, then run your "installer" for this Update, reboot
and version is the same (but in "winsxs" I have a file netcfg.exe with version 6.1.7601.21628)

I think I would continue to install the Updates (of repository) "normally"

thanks

 

It doesn't make sense because it's not true.

GDR and LDR are just two branches with different levels of stringency for accepting changes. Bugfixes that land on the LDR branch do not necessarily land on the GDR branch, and the inclusion in the latter generally requires a higher degrees of review, testing and validation (or it could trump that with importance or impact; e.g., out-of-band security fixes); in Microsoft's own lingo, GDR has a higher "bug bar". Each branch is cumulative. A particular GDR version of a file will contain every single GDR fix that came before it, likewise with LDR. The part that isn't cumulative is that a GDR file built on March 1 will not contain a LDR fix that was in a February 1 build (but it will contain a GDR fix in a February 1 build).

And, needless to say, since LDR build numbers are guaranteed to be higher than GDR build numbers, those build numbers between LDR and GDR are not comparable. So build 23456 on LDR, even if it has a higher build number than 17890 on GDR, is not necessarily more up-to-date (that can only be determined by the build date).

Once you're on LDR--e.g., if you have a LDR version of shell32.dll--then all subsequent hotfixes will install the LDR version of that file, even if a GDR version is available. So essentially, by installing a LDR version of a file, you've committed yourself to the LDR branch for that file.

Basically, when you install LDR, you are saying that you want every fix--past and future--regardless of whether it meets the GDR bug bar. And if you stick with GDR, you will still get all cumulative fixes--it's just that it's only those the passed the stringent GDR bug bar.

 

Ah ok, because on the Microsoft website:

By security implications, they mean patch Tuesday releases.

If your intention is to just install a few updates that may affect you from the repository, then installing GDR is fine. However, if your intention is to be up-to-date, then it would stand to reason to install the LDR branch, since its considered the Hotfix branch. It is afterall, the 'Hotfix Repository' and not the 'Broad customer impact or security implications Update Repository'! lol

I've changed the update installer to only install LDR versions of the update if available, considering Bapt's report.

 

Okay, LDR hotfixes have to be installed in order to be up-to-date.

Putting that aside, suppose that I want to create most up-to-date Windows 7 SP1 image via RT 7 Lite. Based on your reasoning, I cannot integrate just the newest (non superseeded) hotfixes. I have to integrate both newest (non superseeded) hotfixes as well as older (superseeded) hotfixes, right? Which order of integrating hotfixes via RT 7 Lite will create most up-to-date image?

a. Integrate newest hotfixes first before older hotfixes, or;
b. Integrate older hotfixes first before newest hotfixes,

Either way, in order to be most up-to-date, then the Windows installation will require more hard disk space, right? Isn't any way to prevent wastage in hard disk space?

 

You need to login to view this posts content.

 

*New hotfix*

KB2447659: The GetGlyphOutline() function incorrectly returns glyphs from the GulimChe font.
Win32k.sys GRD:6.1.7601.17527 LDR:6.1.7601.21624

 

Well, so where can we find KB2447659-v2?

EDIT: never mind, I was looking with "v2" in the name...

 

You need to login to view this posts content.

 

Have you tried toggling 'Passive FTP'?

 

So, does KB2447659-v2 superseed KB2479628?

 

Thats correct, KB2447659 deals with a different issue, but updates the same file (Win32k.sys, and yes its for both x86 and x64) to a newer version.

Although the update in itself doesn't supersede KB2479628, it does supersede the same files as updated by KB2479628. Not trying to confuse anyone by that!

Basically if you install both, only the files from KB2447659-V2 will be used, meaning KB2479628 serves no purpose other than to place extra files and folders into the WinSxS folder, and thats why the old updates are removed from the repository.

If you have already installed KB2479628, its a good idea to uninstall it after installing KB2447659 to save disk space etc, which is why I made the automated uninstaller for superseded updates.

 

Thanks Solor new updates !!!!!

 

I downloaded the list again but found that I had 1 update in my list that was not in your current list, namely, KB2498472. Did you not want to include this one, or?