Windows 7 Hotfix repository

Does anyone know what's the deal with KB2688730 and KB2688729 ? According to their KB articles they contains the same files but they got different file size.

 

KB2688729 is for Windows 7 RTM/Server 2008 R2 RTM, and KB2688730 is for Windows 7/2008 R2 SP1. You are correct, the installed files do seem the same. The difference in the file size would be due to different catalog, manifest, and .mum files.

 

New KUC is out
I hope i did not oversaw an update/hotfix

 

Does not recognize/uninstall

Code:

2624677"6.1.1.0""Installed""Hotfix"4/3/2012 8:37 PM"BF_2624677""""Windows6.1-KB2624677-x86.msu""yes""2687753"" ""unknown""Not found in Reference! [KUC-State] is either OK, if it is a new Hotfix or [KUC-State] should be REMOVE, if it is an old one or applies, but does nothing ! """

 

Here's the list of UNKNOWN hotfix I got:

Code:

26246776.1.1.0InstalledHotfix29/02/2012 23:46BF_2624677Windows6.1-KB2624677-x64.msuyes2687753 unknownNot found in Reference! [KUC-State] is either OK, if it is a new Hotfix or [KUC-State] should be REMOVE, if it is an old one or applies, but does nothing ! 

-16.1.7600.16444InstalledLanguage Pack28/12/2011 17:24NTBackup-RestoreUtility-Packageen-US unknownLanguage Pack NOT found in the Reference
-16.1.7600.16444InstalledUpdate28/12/2011 17:24NTBackup-RestoreUtility-Package-MiniLPen-US unknownUpdate NOT found in the Reference

Thanks Komm!

 

Worked flawlessly for me-no unknown or unrecognized anything; found 22 packages to uninstall and 2 to install. This is after running Burf's Installer_V25b to install all 53 of the "new" updates found.

Update: my bad; yes KUC fails to recognize updates already extracted and present in the KUC_Repo, but, required for installation. It insists on downloading the msu. My workaround was to replace the .msu extension with .cab in the copy files cmd. Other than that minor bug it worked just great.

Very nice komm

 

Works perfectly either way-silent or user input; very nice McRip

 

You need to login to view this posts content.

 

Ricktendo, have you also come across that problem of having to sysprep an image twice in order to be able to integrate certain updates to an image? I read RickSteele's account of this but remember you having mentioned you sysprep as well, so I wonder if you have found any work-around or alternative method that would prevent us from having to perform two syspreps to get all the updates to integrate nicely to a particular image.

I just verified that, indeed, after having sysprepped an image twice, I was able to integrate ALL 333 updates I had in my folder, whereas with the image that I sysprepped only once, about 20 or more updates failed to integrate (citing pending update problem).

Thanks

 

You need to login to view this posts content.

 

I have not done any syprepping in a while since my laptop died and I am having to use my old slow toshiba

 

Thanks Rick. A friend just suggested to me that it may not be necessary to sysprep an image twice. Sysprepping twice does work, as RickSteele said and as I just verified myself as well. But my friend suggested to try sysprep OOBE reboot first (so then reboot) and THEN to sysprep OOBE quit. It made perfect sense to me when he said that, because the 'pending reboot' problem should be remedied by... well... a reboot You'd still be in audit mode but it makes sense this would work. I'll try it and report back.

PS: my hat off to power users who can stand to work on a laptop

 

You need to login to view this posts content.

 

I feel for ya'; that definitely sucks.

 

In the latest pack you uploaded, it seems only KB2666938 is superseded (at least for x64, according to the latest KUC).

 

Ok, I'll put them all in but 2666938-v2. Thanks Burf.

I have removed those update installers flagged by Old Update Remover W7 SP1 12-Apr-2012 as superseeded, added the balance of the "new" updates to the uncompressed x86/x64 on McRips server and 7-zipped both. The compressed archives are on the server. Refer to the Update Changelog.txt for the changes made to date.

 

You need to login to view this posts content.

 

The situation is the following:
2624677-v1 has normal and BF version
2624677-v2 has no BF
2624677-v2 is a new update but it is supperseded by 2687753
I have only one version of a kb in my database, so there is 2624677-v2.
But this one has no BF, so you don't get the "new version" message for 2624677-v1-BF

I think this is the first time something like that came up.
I have to fix that in the next version.

I will check NTBackup too.

 

I agree. Sometimes it works, sometimes not.

 

Are all the updates that did not install first time "driver" updates (use KUC to check)?