The Windows 7 UnOfficial Update and HotFix Collections Members, Here you may post you own hotfixes and updates to be put in packs and posted in our sticky thread. Brandrune and secr9tos ( myself ) will then pack your updates in 5/10/15's and place into RAR files. This is to reduce the space in the threads. WARNING: UPDATES AND HOTFIXES HAVE BEEN LEAKED AND MAY NOT BE SAFE TO USE. USE ONLY AT YOUR OWN RISK. :WARNING NOTICE #1: EACH UPDATE/HOTFIX POSTED HERE WILL BE SCANNED AND PACKED SO NOT UPDATE/HOTFIX WILL NOT CONTAIN VIRUSES. NOTICE #2: ALL SUBMITTED UPDATES THAT DON'T USE THE SUGGESTED FORM ( OR SIMILAR ) WILL BE DELETED!
There is only 133 unique windows hotfixes and then about ~10 more "aditions" of some sort (like virutalpc, system update readyness tool etc). And thats about it... so of those 203 "MEGA SUPER PACK" there is lot of garbage and gets superseeded at one point or another. Yesterday when zukona posted that late packs from november/december it took me 6h to map them out and figure out what superseeds what.
This wont work, because date creation sometimes gets changed when you copy/upload/download whatever. For this to work we should make some parsing script, that would check digital signature date and then install then in reverse order of digital signatures. But even in this case if updates have same components WU allows them to be installed for some reason (for example KB976398 and KB976399, both have same version of group policy and they are 2 or 3 more of cases like this, but WU allows them all to be installed). I otherwise do this manualy, install all updates of full "prepatched" windows in vmware and then when there are new updates, i open them, check what components they have and then check in "table" of old updates if some old update includes that components and get superseeded that way. But until there is only one component its easy problem begins when, 2-3 superseeds some old one, or other way around and then you also need to watch if some patch is LDR only or GDR and LDR, because sometimes in same patch that have both GDR and LDR versions they are not same files, LDR includes sometimes includes more fixes, so you sometimes need to install some old LDR patch (that is superseeded otherwise), just to bump that component in to LDR branch. Bottom line is, its a mess if you want to have installed "only" unique updates.
Thanks Serp202 for posting the updates! I've just started downloading them, but its almost 1am Tuesday here so I think I'll leave that till tomorrow! I'll post here what I have found with them.
lol who you think you are? "work" you mean take 5 packs from zukona, mix them together and upload them somewhere? yes that is hard... how much does it take? download time + 2min + upload time? unless YOU are zukona there is basickly _zero_ work from you, but i dont think he would try to hide his identety behind different nick... you are smartass for someone with 9 posts and most of them is posting LINKS to updates or offending people. Just got damn post source of this updates is zukona anyway and YOU personly didnt do much.
just keep focused on the topic guys.. Oh and don't forget: WE NEED VOLUNTEERS TO TEST THESE UPDATES!!!
This has nothing to do with the topic.. please only post useful things like updates etc.. and not "spam" nobody needs to quarrel here...
Update pack analysis: I installed a fresh clean copy of Windows, which I had intended doing anyway, and did the following: With the large hotfix pack posted by Serp202, I broke it up into 3 groups to make it more manageable. I broke them up based on The 'date modified' dates, which shows the original creation date of the file. Breaking up a large number of updates can be beneficial as when there are hundreds of updates, each update seems to get slower when there are a hundred installed before it. Two groups would have been fine too. After each group was installed, I compared the updates in the folder with the updates in the 'View installed updates' part of the programs and features control panel. I double checked each one not on the list by running it manually (to be sure), and moved the non applicable into another folder. I then rebooted and repeated the process for the other two folders. I then copied the files that did install into another folder, and copied the updates I had that I thought were ok over the top of them, BUT skipping the ones that exist. The copied files are the difference between what I had in my normal update folder and the updates that installed. The copied files are automatically highlighted by explorer (ensure you haven't highlighted a file in the folder already), I then cut and pasted the highlighted files into yet another folder. I ran each one of them, and all were non applicable. Also there are updates Windows6.1-KB973525-x64.msu and Windows6.1-KB973525-v1.1-x64.msu. The v1.1 is actually older, the GDR and LDR build number (respectively) are x.16415 & x.20518 for Windows6.1-KB973525-v1.1-64 and x.20529 & x.16424 for the Windows6.1-KB973525-x64. I checked these before installing. I've listed what I just discussed below: With the batch script I installed the updated newest first. The following updates were installed: Code: Windows6.1-KB123334-x64.msu Windows6.1-KB123456-v2-x64.msu Windows6.1-KB674101-x64.msu Windows6.1-KB674103-x64.msu Windows6.1-KB675605-v2-x64.msu Windows6.1-KB675606-x64.msu Windows6.1-KB917607-x64.msu Windows6.1-KB925681-x64.msu Windows6.1-KB941158-x64.msu Windows6.1-KB943790-x64.msu Windows6.1-KB954664-x64.msu Windows6.1-KB958488-v6001-x64.msu Windows6.1-KB958488-x64.msu Windows6.1-KB958559-x64.msu Windows6.1-KB958685-v2-x64.msu Windows6.1-KB969168-x64.msu Windows6.1-KB970413-v2-x64.msu Windows6.1-KB970486-x64.msu Windows6.1-KB970924-x64.msu Windows6.1-KB971468-x64.msu Windows6.1-KB971601-x64.msu Windows6.1-KB971988-x64.msu Windows6.1-KB972251-x64.msu Windows6.1-KB972270-x64.msu Windows6.1-KB972551-x64.msu Windows6.1-KB972583-x64.msu Windows6.1-KB972831-v4-x64.msu Windows6.1-KB972848-x64.msu Windows6.1-KB973062-x64.msu Windows6.1-KB973525-x64.msu Windows6.1-KB973746-x64.msu Windows6.1-KB973751-x64.msu Windows6.1-KB973975-x64.msu Windows6.1-KB974039-v2-x64.msu Windows6.1-KB974090-x64.msu Windows6.1-KB974168-x64.msu Windows6.1-KB974204-v2-x64.msu Windows6.1-KB974327-x64.msu Windows6.1-KB974332-v1.1-x64.msu Windows6.1-KB974405-x64.msu Windows6.1-KB974431-x64.msu Windows6.1-KB974562-x64.msu Windows6.1-KB974571-x64.msu Windows6.1-KB974624-x64.msu Windows6.1-KB974638-v2-x64.msu Windows6.1-KB974639-x64.msu Windows6.1-KB974940-v4-x64.msu Windows6.1-KB974944-x64.msu Windows6.1-KB975076-x64.msu Windows6.1-KB975214-x64.msu Windows6.1-KB975243-x64.msu Windows6.1-KB975354-v2-x64.msu Windows6.1-KB975363-x64.msu Windows6.1-KB975364-x64.msu Windows6.1-KB975415-v2-x64.msu Windows6.1-KB975467-x64.msu Windows6.1-KB975469-x64.msu Windows6.1-KB975496-x64.msu Windows6.1-KB975535-v2-x64.msu Windows6.1-KB975538-x64.msu Windows6.1-KB975541-x64.msu Windows6.1-KB975560-x64.msu Windows6.1-KB975599-x64.msu Windows6.1-KB975680-x64.msu Windows6.1-KB975688-x64.msu Windows6.1-KB975777-x64.msu Windows6.1-KB975778-x64.msu Windows6.1-KB975806-x64.msu Windows6.1-KB975851-v2-x64.msu Windows6.1-KB975858-x64.msu Windows6.1-KB976038-x64.msu Windows6.1-KB976090-x64.msu Windows6.1-KB976098-x64.msu Windows6.1-KB976099-x64.msu Windows6.1-KB976127-v5-x64.msu Windows6.1-KB976210-v2-x64.msu Windows6.1-KB976240-x64.msu Windows6.1-KB976296-x64.msu Windows6.1-KB976398-x64.msu Windows6.1-KB976399-x64.msu Windows6.1-KB976417-x64.msu Windows6.1-KB976419-v3-x64.msu Windows6.1-KB976422-x64.msu Windows6.1-KB976443-x64.msu Windows6.1-KB976494-x64.msu Windows6.1-KB976525-x64.msu Windows6.1-KB976538-x64.msu Windows6.1-KB976566-x64.msu Windows6.1-KB976571-v2-x64.msu Windows6.1-KB976586-x64.msu Windows6.1-KB976658-x64.msu Windows6.1-KB976662-x64.msu Windows6.1-KB976746-x64.msu Windows6.1-KB976755-x64.msu Windows6.1-KB976759-x64.msu Windows6.1-KB976775-x64.msu Windows6.1-KB976778-x64.msu Windows6.1-KB976781-x64.msu Windows6.1-KB976782-v2-x64.msu Windows6.1-KB976910-x64.msu Windows6.1-KB976983-x64.msu Windows6.1-KB977015-x64.msu Windows6.1-KB977020-x64.msu Windows6.1-KB977036-x64.msu Windows6.1-KB977074-x64.msu Windows6.1-KB977132-x64.msu Windows6.1-KB977158-x64.msu Windows6.1-KB977165-x64.msu Windows6.1-KB977178-x64.msu Windows6.1-KB977180-v2-x64.msu Windows6.1-KB977186-x64.msu Windows6.1-KB977222-x64.msu Windows6.1-KB977314-x64.msu Windows6.1-KB977342-v2-x64.msu Windows6.1-KB977348-v3-x64.msu Windows6.1-KB977357-x64.msu Windows6.1-KB977375-x64.msu Windows6.1-KB977380-x64.msu Windows6.1-KB977392-x64.msu Windows6.1-KB977397-x64.msu Windows6.1-KB977419-x64.msu Windows6.1-KB977542-x64.msu Windows6.1-KB977576-x64.msu Windows6.1-KB977579-x64.msu Windows6.1-KB977609-x64.msu Windows6.1-KB977617-x64.msu Windows6.1-KB977620-x64.msu Windows6.1-KB977627-x64.msu Windows6.1-KB977648-v2-x64.msu Windows6.1-KB977863-x64.msu Windows6.1-KB977866-x64.msu Windows6.1-KB977911-v2-x64.msu Windows6.1-KB977944-x64.msu Windows6.1-KB977977-x64.msu Windows6.1-KB978042-x64.msu Windows6.1-KB978054-v4-x64.msu Windows6.1-KB978055-v2-x64.msu Windows6.1-KB978125-x64.msu Windows6.1-KB978155-x64.msu Windows6.1-KB978157-x64.msu Windows6.1-KB978207-x64.msu Windows6.1-KB978249-x64.msu Windows6.1-KB978254-x64.msu Windows6.1-KB978258-x64.msu Windows6.1-KB978387-x64.msu Windows6.1-KB978433-x64.msu Windows6.1-KB978462-x64.msu Windows6.1-KB978476-x64.msu Windows6.1-KB978506-x64.msu Windows6.1-KB978535-x64.msu Windows6.1-KB978601-x64.msu Windows6.1-KB978637-x64.msu Windows6.1-KB978869-x64.msu 153 updates installed The following updates are updates in the pack that weren't applicable to my system (some of these may not be superceded, but valid only for Server 2008 R2 for example): Code: Windows6.1-KB968771-x64.msu Windows6.1-KB972636-x64.msu Windows6.1-KB973529-x64.msu Windows6.1-KB973874-x64.msu Windows6.1-KB974065-x64.msu Windows6.1-KB974138-x64.msu Windows6.1-KB974176-x64.msu Windows6.1-KB974179-x64.msu Windows6.1-KB974259-v2-x64.msu Windows6.1-KB974324-x64.msu Windows6.1-KB974455-x64.msu Windows6.1-KB974473-x64.msu Windows6.1-KB974476-v2-x64.msu Windows6.1-KB974537-x64.msu Windows6.1-KB974560-v2-x64.msu Windows6.1-KB974598-x64.msu Windows6.1-KB974636-x64.msu Windows6.1-KB974672-x64.msu Windows6.1-KB974817-x64.msu Windows6.1-KB974909-v2-x64.msu Windows6.1-KB974912-x64.msu Windows6.1-KB975053-x64.msu Windows6.1-KB975142-x64.msu Windows6.1-KB975499-x64.msu Windows6.1-KB975500-x64.msu Windows6.1-KB975530-v4-x64.msu Windows6.1-KB975617-x64.msu Windows6.1-KB975620-x64.msu Windows6.1-KB975741-x64.msu Windows6.1-KB975762-v2-x64.msu Windows6.1-KB975763-x64.msu Windows6.1-KB975921-x64.msu Windows6.1-KB975954-x64.msu Windows6.1-KB975992-x64.msu Windows6.1-KB976092-x64.msu Windows6.1-KB976093-x64.msu Windows6.1-KB976096-v2-x64.msu Windows6.1-KB976187-x64.msu Windows6.1-KB976323-x64.msu Windows6.1-KB976325-v2-x64.msu Windows6.1-KB976418-x64.msu Windows6.1-KB976427-x64.msu Windows6.1-KB976462-v2-x64.msu Windows6.1-KB976483-x64.msu Windows6.1-KB976484-x64.msu Windows6.1-KB976528-x64.msu Windows6.1-KB976627-x64.msu Windows6.1-KB976655-x64.msu Windows6.1-KB976749-x64.msu Windows6.1-KB976764-x64.msu Windows6.1-KB976883-x64.msu Windows6.1-KB976887-x64.msu Windows6.1-KB976898-v2-x64.msu Windows6.1-KB976972-x64.msu Windows6.1-KB977067-v2-x64.msu Windows6.1-KB977068-x64.msu Windows6.1-KB977071-x64.msu Windows6.1-KB977140-x64.msu Windows6.1-KB977307-x64.msu Windows6.1-KB977346-x64.msu Windows6.1-KB977381-x64.msu Windows6.1-KB977415-x64.msu Windows6.1-KB977420-x64.msu Windows6.1-KB977570-v2-x64.msu Windows6.1-KB977577-x64.msu Windows6.1-KB977578-v2-x64.msu Windows6.1-KB977580-v4-x64.msu Windows6.1-KB977608-x64.msu Windows6.1-KB977615-x64.msu Windows6.1-KB977632-x64.msu Windows6.1-KB977692-x64.msu Windows6.1-KB977748-x64.msu Windows6.1-KB977832-x64.msu Windows6.1-KB977894-x64.msu Windows6.1-KB977927-x64.msu Windows6.1-KB978034-x64.msu Windows6.1-KB978048-x64.msu Windows6.1-KB978116-x64.msu Windows6.1-KB978118-x64.msu Windows6.1-KB978265-x64.msu Windows6.1-KB978347-x64.msu Windows6.1-KB978838-x64.msu Windows6.1-KB979006-v2-x64.msu 83 not applicable The following list is a list of updates that were in my folder, which I thought were ok, which are superceded (not applicable now but used to be). These updates are currently in the update packs (as far as I know): Code: Windows6.1-KB973529-x64.msu Windows6.1-KB974065-x64.msu Windows6.1-KB974537-x64.msu Windows6.1-KB974560-v2-x64.msu Windows6.1-KB975620-x64.msu Windows6.1-KB975921-x64.msu Windows6.1-KB976092-x64.msu Windows6.1-KB976187-x64.msu Windows6.1-KB976325-x64.msu Windows6.1-KB976528-x64.msu Windows6.1-KB977140-x64.msu Windows6.1-KB977346-x64.msu Windows6.1-KB977420-x64.msu Windows6.1-KB977608-x64.msu Windows6.1-KB977927-x64.msu Windows6.1-KB978116-x64.msu 16 outdated previous updates