yes lots of updates! and thanks! btw you can use page2rss.com to get rss feeds from the repo when its updated
Hi! I have just integrate the updates on my windows 7 disc, original windows 7 disk is 2.9gb, but after I integrates all the updates the windows 7 disk end up the size of 4.37gb, how is that possible when all updates are on the 559mb? Tnx for the uppdates.
Hmm... that doesn't really sound right to me. Only after I integrate updates and add 1gb of apps, I'm about at that number.
Oh yeah, didn't think about that OK, that probably does sound more right then. For x86 the updates are around 300+ mb, whereas for x64 they are 500+ meg, and I find it about adds that amount to the original Win source after updating. But possibly more, as your post would indicate.
If I do not install the full (client plus extended) .NET 4 package, none of the client hotfixes/updates will install. Below is a representation of the error message for all-just change the KB number: OS Version = 6.1.7600, Platform 2 OS Description = Windows 7 - x64 Ultimate Edition TimeZone = Eastern Daylight Time Initial LCID = 1033 Using Simultaneous Download and Install mechanism Operation: Installing Package Name = KB2413613 Package Version = 10.0.30319 User Experience Data Collection Policy: Disabled Number of applicable items: 0 KB2413613 does not apply, or is blocked by another condition on your computer. Neither the BBS or Windows Event logs contain any references at all to the failed installs. This has been the case for me since the first update to .NET was released. This is a fresh realtime install. So, anybody have any ideas?, or is this normal if one does not install the extended portion.
@RickSteele - The earlier version of Client .Ner 4 package has that problem until I downloaded the latest client package from SoLor's repository. Since then, I don't have any problem installing the hotfix for client .Net package.
Thanks for the answer, but, I install that particular package-still no joy; I am wandering if it has something to do with the fact I install all of the Visual runtimes first.
Does anyone have a list of the updates removed from the repository from before 15 Sep? Superceded updates can be removed by running the script below: Code: @echo off Title Windows 7 Automated Superceded Updates Uninstall Script set /a "Superceded"=1 for /f %%A in ('type list.txt') do ( set "Superceded" echo If update KB%%A is currently installed, uninstalling ... start /wait wusa /uninstall /quiet /kb:%%A /norestart echo. set /a "Superceded"="Superceded"+1 ) List.txt contains the number relating to the update to be removed, such that update KB982454-v2 is listed as 982454 The current contents of list.txt is: Code: 123334 941158 958685 970486 971468 971736 972270 974624 975849 976036 976662 976746 976983 977074 977178 977222 978000 978054 978206 978571 978637 978886 979101 979373 979443 979559 979619 979744 980077 980078 980408 980436 980959 981076 981107 981109 981112 981119 981124 981128 981129 981130 981145 981152 981166 981180 981187 981194 981197 981208 981214 981266 981275 981286 981303 981347 981382 981394 981466 981506 981550 981574 981613 981618 981619 981620 981636 981709 981711 981721 981750 981761 981773 981776 981791 981793 981842 981845 981848 981851 981852 981872 981878 981898 981957 981983 982063 982064 982164 982199 982214 982296 982300 982316 982323 982347 982381 982383 982386 982405 982454 982479 982502 982519 982520 982613 982615 982632 982633 982635 982643 982664 982666 982667 982669 982709 982728 982764 982867 982927 982936 982937 982938 983289 983385 983401 983402 983404 983458 983460 983461 983466 983484 983528 983531 983533 983543 983544 983545 983615 983633 1000002 1000003 1000005 1000006 2028566 2028625 2028666 2028685 2028686 2028765 2028771 2028827 2028840 2028962 2028965 2028988 2029558 2030901 2032276 2064460 2160329 2175609 2182005 2183461 2209360 2217044 2223201 2249857 2250979 2257386 2257924 2261116 2262325 2275828 2276597 2277904 2284538 2286198 2295805 2297652 2300135 2316513 2386792 2388144 2398632 The advantage of doing it this way is it simplifies the removing of superceded updates. If the update isn't present, it doesn't matter. If an update is replaced by a newer version of the same update, I haven't listed it for removal (as running the script will uninstall the newer version if installed). So, having the list of updates removed from the repository from before 15 Sep, I can complete the list.txt When there are a large number of updates superceded the automated method will greatly simplify the removing of superceded updates that take up unnecessary disk space. Additionally, I'm sure most people who have been installing these updates may not have uninstalled the superceded updates, so having the complete list will nicely free up some disk space! Once SP1 comes out, this will still be beneficial, but of course starting with a new list. Installing sp1 on a system with all the updates installed so far is ok, there is a command that can be run after the final RTM SP1 that can remove all the pre sp1-installation updates (and make uninstalling sp1 impossible).
Gr8 idea, but I guess SoLoR does not keep the older lists...it may also be easier to simply make a complete list (using dism /online /get-packages) and uninstall all (KB*) packages listed before installing sp1
no i dont keep backups and when SP1 comes its better to do fresh install anyway with intergrated SP1 iso.
Thats true, and like I was saying you don't need to uninstall the updates/hotfixes if you did install sp1 and not do a reinstall, as you can simply use the compcln command. I don't know whether its present in the beta's or not, but should be in the rtm sp1, like with Vista which had it under sp1 (under a different name) and was part of sp2. There were two reasons why I thought this would be handy: - For those that have installed all the updates thus far, but haven't been uninstalling the 'removed' updates, it would be good to clean things up without having to resort to a reinstall. A reinstall once sp1 integrated comes out would still be a good thing. - Once SP1 comes out and a new hotfix list evolves, the list could be updated on each hotfix release, and be used as a simplified means for people to uninstall superceded updates. Its easy enough to uninstall one of two hotfixes when they become superceded, but when there are potentially dozens, especially if Zukona releases post sp1 packs, it would greatly expediate and simplify updating. Also, if uninstalling has been looked over for several weeks etc, it doesn't matter as the uninstall list could take care of it So, as I was saying I was hoping it could be useful for current systems, but in any case it should definitely be useful on sp1 installs, with a new list, once that becomes a reality.
I've again updated the code for the list.txt to reflect the updates made redundant by the 24 Oct updates as per Solors list. The list doesn't list all the superceded updates, but at over 180 it isn't too bad. If you copy the first window code into notepad and save it as 'Superceded Uninstall.cmd' ('Superceded' is an alternative, incorrect but better looking spelling than 'Superseded'), and copy the second window text into a file called 'list.txt', ensuring they are in the same folder, if the first file is then run it will automatically uninstall all the superceded updates that are listed in list.txt The script will show you what number position on the list that is currently being processed, and the superceded update that is currently being checked for, and subsequently removed if present. I've only designed it to be used in conjunction with Solors updates. **** It is actually better to install the new updates and reboot if you haven't done so already, and run the script than running the script before installing updates. There is a simple reason for that, but I won't go in to explaining it but its rather simple if you think about it!
Yeah! Well, if you haven't installed the newest updates, removing the old update that the newer one is meant to replace means you revert back to the GDR or even RTM version of the files, then you have to restart as they are in use then install the new updates and restart. Running it after the new updates, the files are no longer in use or needed, and are therefore removed. The list takes into account LDR and GDR updates too, since all the necessary updates are in Solor's list and aren't removed. On a side note, I accidentally listed kb958488 in the list, I have just rectified that
Sorry for all the posts If anyone has a very old Windows 7 installation, hasn't removed any old updates themselves and has been been installing all of SoLoRs updates from as long ago as when he had them on Skydrive, I'd like to ask a favour The favour involves using regedit. Its safe as long as you know what you are doing, but just be careful if you do use it! The structure of the registry in regedit is like a computer drive Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Currentversion\Component Based Servicing Click on Packageindex, so its highlighted, click on file, then export, and save it to a known location. The file will then need to be uploaded, say to mediafire which is free. Then, just copy the link to the file here. The contents of the export contain only Windows update info, there is nothing personal that will be there if the export is carried out like explained. The file contents will look complex and a mess, but its actually quite easy to get the kb numbers out of it. I will then alter the contents of the list.txt code, which should reflect almost all superceded updates. This will alow for people to have a cleansed system for the next few months whilst we wait for Windows Sp1. After Sp1, I will be maintaining the files on each new update release. I'll post the files on mediafire once the list.txt is as complete as I can get it, and update them after each Solors release.
If you can't find anyone that has all this info, would that then mean there is no big use for this? Personally, I would think someone would not want to use SoLoR's updates on anything but one's personal computer. From there, my reasoning is that if someone likes to experiment with updates like these (as I do) he/she would or should have the knowledge to integrate them into a build and install from that. I can't really imagine someone would run Win7 for 6 months and use SoLoR's updates and never reinstall. I may be wrong, but that is certainly not the way I go about things. My current Win7 disc is up to date with Oct 24th's updates, and I would not want my June disc anymore for obvious reasons. Maybe I'm somewhat of an install junkie, but as it stands my Win7 disc and its customizations is well done (replaced system files for custom themes, has many reg tweaks applied, has 1gb of software (and WPI) included, etc.). I just don't believe in running an OS for longer than 3 months anyway, and it would be so much better to integrate the updates into the install.wim (one way or another) and install fresh. Just my thoughts on the matter...
Thats true it can be still beneficial though, particularly if superceded updates weren't removed or you missed some if manually removing them yourself. Post SP1, the list will be started from fresh and of course maintained and uploaded to mediafire (because its free and practical). Alternatively, SoLoR is more than welcome to add it to the repository, the list can be sorted automatically to numberical order if maintained in excel then simply copied back over the list.txt contents.