Windows 7 Hotfix repository

I also found at least 1 update that was superseded one month ago.
951422-v2
Windows-TerminalServices-RemoteConnectionManager.Resources has version 6.1.7600.21085 and not 6.1.7601.21855 and is only installed for RTM
so 2667402 and 2647409 supersede 951422-v2

for everybody to check here a list of superseded updates I found in the repo
951422
975410
2496744
2514307
2524478
2563210
2566059
2589015
2600907
2617157
2619497
2621491
2636613
2637518
2639043
2641192
2641222
2646168
2647516
2664375
2665875
2669522
2672484
2673977
2675785

 

Looks like I forgot to generalize on my first sysprep, i tried again and it worked. I also followed your directions on removing WPA info and resetting rearms count and it worked perfectly. Thanks a lot for the info.

 

Small suggestion to KUC Windows Update Checker.
Flat folder structure is not the best way for keeping updates...
It would be better to look for update in subdirectories, so Copy_Files_2_add.cmd could be chaenged like this:
Replace:

Code:

xcopy "%Repo_Path%\hotfix.msu"   "%Work_Folder%\Normal" /y >nul

To:

Code:

Call :CopyUpdate "hotfix.msu"   "%Work_Folder%\Normal"

Add to script end:

Code:

GOTO :eof
:CopyUpdate
for /f "Tokens=*" %%i in ('dir /b /s "%1"') do xcopy "%%i" %2 /y >nul
GOTO :eof

 

Uncompressed repo on McRip's Cesidian server is up-to-date with this latest.

 

I was just thinking about the superseded update remover...

Do people actually use the LDR placeholder function? (in that they install the LDR placeholders to force the LDR branch instead of forcing the LDR branch directly)?

Just that the SoLoR repository has LDR placeholders in mind, but the Cesidian server repository doesn't. In the future its possible both will reflect each other directly? (maybe)? Anyways, since the Cesidian server is updated more frequently I might start using that as the base, but in which case I need to remove the LDR placeholder function from the script.

If anyone uses the LDR placeholders, let me know! (and if you want to, the reason for using it)!

Thanks!

I know I did promise an updated installer script last weekend, but I ran out of time. I wanted to update the system for WU satisfaction, and the satisfaction list - working out what is required as Komm knows, isn't an exact science! which is why my list is different... in any case, the only functional change will be the satisfaction list, and the satisfaction check, so in itself will not be massively different so don't let it hold you off using the current one. The main thing people will notice with the script update is a couple of KB's shaved off its size.

 

I do use it.

And there are LDR placeholders on the server.

 

KB2556532 and KB2644615 are superseeded, have an older version, replaced by another update

 

?, what is superseeded by what

 

@burfadel
No, I don't use LDR placeholders; use either komm's or your's to install, forcing LDR as the program sees fit.

 

these 2 are superseeded according to SoLoR. When I was asking why these 2 updates are showing in WU for me even when I have all SoLoR updates installed, he said that they can be hidden, because they are superseeded. Twas like a month ago, not sure

 

???????????

 

files of these updates are older than what I already

 

Would you please describe which update or updates supersede the called above?

 

Dunno, but one update is more then half a year old and the second one is from january. When I integrated SoLoRs March 19th KB000000 back then, 3 more updates (KB2556532, KB2644615 and KB2639308) were shown in WU for me. At the same time, some other guy wrote that he had a few updates shown in WU too and that one of them is KB2644615. So I replied to him that I had a similar problem, only with slightly different updates shown. Minutes later, SoLoR replied (at 22nd of March) that any update shown in WU after the March 19th repo update could be safely hidden, because its superseeded.

 

KB2556532 is superseded by KB2532445-v2, KB2645594 and KB2666390 (OS Kernel)

KB2644615 is superseded by KB2582203-v2 (ntdll)

of SoLoR's repo

 

bapt is correct. But the newest that supersedes KB2556532 is KB2679255-v2 (SoLoR needs to add it).

 

OK, thanks for clarification to all of you. I'll take a look at it.

 

Repo should be correct now. If somebody wants to check and find some errors, please let me know about it.

 

KB2556532 and KB2644615 are both superseded however if they are not present they will appear on windows update so they should installed/integrated as well.

 

Amires, I dont have this problem. I did not hide anything from WU and those two updates are not installed on my systems, WU is not showing it at all. Pretty weird.