McRip's server is not responding and neither is he. At this point, it appears he's taking some time off from maintaining the repos (I hope he'll be back soon though). Check out komm's KUC utility a few posts prior. It will download the latest updates for you. -------- McRip: we all understand the frustration involved in the recent DDOS attacks on the repos. Take a few days (or even weeks) off from worrying about it and then please take a fresh look at things again once you feel ready. There are many people here who value all the work you do.
If someone would step up and could create a dedicated repo sync app that would sync (and delete) the hotfixes on the repo with a folder on ones HDD (using md5 hash verification or something) maybe he will be willing to restore it
McRip was spending much time, money and effort keeping these online for us, I do hope he is back soon. I for one will be donating to help him out!
Dear all member when i use win toolkit cant download the McRip update pack ... so i have try look the comment for it just know McRip take some rest ... so can any one teach some how to use win toolkit download KUC update pack ... sorry for my poor english ... and thanks for the information ~
someone can upload the following updates? THX! Added: KB2554746-v2 (Additional/MSQM) KB2781498 (Additional/KB2506143.Windows.Management.Framework.3.0.CTP) KB2781512-v2 (Additional/KB2506143.Windows.Management.Framework.3.0.CTP) KB2801466 (Additional/VPC) KB2524732-v2 KB2591271-v2 KB2732673-v3 KB2781049 KB2790804 KB2790817 KB2796313 KB2796647 KB2797789 KB2797918 KB2798286 KB2798787 KB2799035 KB2799360 KB2799406 KB2800170 KB2800422 KB2800789 KB2801453 KB2803752 KB2803759 Windows OS Kernel version 7601.22244 KB2459530-v4 KB2800213 KB2693010-v2
ricktendo64, is that I can integrate your "Microsoft. NET Framework 4.5 x86/x64 Full Slim + Updates" to ISO?
Or you can reverse integrate .NET4.5 into Win7 image, though as we know, it can be a lengthy process.
Or you can make a sysprep'd image. Install Win7 in a VM as .vhd format, apply all updates and install the latest .NET 4.5 installer. Then perform sysprep (OOBE->Generalize->Shutdown). When done, mount the .vhd file with Disk Management and then capture (via Imagex) the drive letter on which it is mounted and you'll have your install.wim. Then put that install.wim in a Win7 iso. Doing this is a more lengthy process than just doing an offline integration of updates, for example, but it has some advantages. You don't have to worry about any pending updates situation, for instance. I think the ngen run for .NET seems to not happen from the sysprep'd image when including .NET 4 (make sure you run the ngen though). I'm actually working on making a sysprep'd Win7 image right now with IE10 included. What I did this time is clone the VM (I use VirtualBox) before I run sysprep (but with all updates/hotfixes applied) and then save that VM so I can use it later on (say, 2 weeks from now if I wanted) and install/uninstall updates and then sysprep from that again, which then is a pretty quick process. MS seemed to have done a really shoddy job with their Win7 SP1 iso, which is why I've been using Win7 RTM with SP1 integrated, and then performed sysprep on that to get the SP1 image. I cleaned reg up (which by then saved 1000 registry errors -- yes, as I said MS SP1 image is awful) and also noticed that the SP1 integrated ISO I made was several hundred MB's smaller. Anyway I've been using that as master image and every now and then do another sysprep image with updates/hotfixes.
True, if done entirely from scratch. But one could clone/save a VM install of Win7 SP1 without any updates applied, which would save you from having to install Win7 in a VM, at least. The installation of updates/hotfixes in the VM is not really any slower (although that could depend on hardware involved) and the sysprep itself doesn't even take a minute. The longest time is then taken by capturing the image (several minutes). Saving the iso with updated install.wim only takes a few seconds. The longest part would be to install Win7 in a VM, which can be prevented by having a VM of Win7 install cloned and ready to go for that purpose. I just captured my updated install.wim for Win7 x64 and it was 3.30gb in size with over 400 updates included (this one without .NET 4.x included). I also included an extensive hosts file (C:\Windows\System32\drivers\etc\) for safer surfing (see my signature for the one I included). EDIT: taken sig links down for now as I was approached by MDL mod that this requires approval from MDL Team