Windows 7 Hotfix repository

Updates from MS update you have to integrate both LDR and GDR branches or it may prompt you to reinstall hotfix, so its a good idea to do both MUM files

BTW give the script a try, I'm sure you can edit it better than what I have

 

for applying the GDR updates you don't need to point to the individual update.mum, just /PackagePath:folder-of-CABs and apply all of them in one shot (?)

 

Yes but you still have to extract it to check, so since its already extracted and ready why not just use it

 

Thanks for your reply, ricktendo64. How do we know which hotfix is LDR "placeholder"? Is KB2417038-v2 a LDR "placeholder"?

 

LDR placeholders are updates that install the same files as the later update, even if they belong to a completely different KB article and issue.

Some updates may have files which are replaced by newer versions in later updates, but still aren't LDR placeholders (despite the fact they still force the LDR update of the later update to be installed). This is because the first update may update additional files not covered by the later update.

 

You need to login to view this posts content.

 

KB2522807
KB2519454-v2
KB2520513

is missing

 

They are in IIS folder

 

Looks like there'll be quite a few updates with this 'patch Tuesday'...

 

Only 19 for me, that's including Office hotfixes.

 

15 here (no Office)

 

w00t!!!

In the end did you manage to get a working script that would integrate ldr branch?

 

You need to login to view this posts content.

 

You know what would be nice burfadel, if you can make it do the KB9 updates first. When integrating I have to separate mine and do two sessions so updates that start with KB2X to components not yet installed that start with KB9 dont fail

BTW in response to your PM if you think that pkgmgr is faster no need to switch

 

The problem with the kbxxxxxx filenames is that you do have a 6 digit KB article number, starting with 9, and the newer 7 digit article numbers starting with 2. If you sort by filename, the kb2xxxxxx updates will go first, in ascending order, then the kb9xxxxx (because kb9xxxxx is read as being 'higher' than kb2xxxxxx despite having 1 less digit).

The way around this, to some extent, is changing:

Code:

dir /b /on

to

Code:

dir /b /o-n

with the above change, the kb9xxxxx updates go first. The problem then though is that when you start on the kb2xxxxxx updates, it will start from (at the moment) kb25xxxxx and proceed to kb20xxxxx, which may end up having the same result.

I don't know a simple workaround for this, one which won't require changing it from a universal Vista/Server 2008/7/2008 R2 service pack independent installer to a Windows 7 SP1 installer...

 

I did think of that, I guess I could also add *kb3* and *kb4*, since we are up to kb25x at the moment... it would remove the OS specificness (overkill I know)

 

You need to login to view this posts content.