Being biased myself i blame win8 first. I cannot fathom how ms could take such a stable system like win7 and screw it up so bad to make win8. I've seen people have some very strage and hard to track problems on win8. Everything fine under win7.
This was the first time I have actually come across an issue with the AHCI drivers, it seems only the 12.8.0.1016 is affected (although the earlier 12.8.x.x driver may also be affected). I'm currently using 12.5.0.1066 as I know that one is definitely fine (as far as I can tell). Could be, but since it was only with 12.8.0.1016 I blame that instead . I will definitely give the next driver a go though! I mentioned it in the Windows 7 Hotfix repository thread because it is the same driver as Windows 7, so Win 7 is probably affected too. It could well be though that it is only an issue affecting Windows 8 with this driver.
i am adding all updates for windows 7 through dism command Code: Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x64" However as I now have 426 to add to an originan install.wim, its takings hours to complete, any idea how to speed this up, was thinking of splitting the update folder into 4, so have 4 passes ?
These days I find it better to make sysprep'd images. Offline integration is OK in itself but the sheer amount of updates (and pending updates that come along with it) is just getting a bit too much. Using sysprep you install the OS in a VM and run the update script(s) live and you can reboot so no pending updates. Also, you can check what WU offers at the end of it all, etc. I recently made 2 Win7 images that way with IE10 installed and they work perfectly. I used to literally make hundreds of images using offline integration but since I've used sysprep I haven't really gone back to offline integration as there's really no advantage to it for me. But even then I divide the updates up into 6 or 7 folders and run each folder with a script and then reboot, until all updates are installed. I then do the WU satisfy updates with its script (as found in McRip's updates) and then to be sure run WU too.
same here. i used offline integration in the beginning but i do everything with sysprep now. it's just more convenient for me. install windows in a VM, install the updates and recapture the image. i then reuse the updated image for future update integrations. -andy-
Found an issue I was having with one of the hotfixes that I was integrating. It's KB2752407. After I installed my Intel(R) USB 3.0 eXtensible Host Controller driver, it would prevent me from installing my AMD video driver. I couldn't figure out why it was happening until I narrowed it down, one by one, to that particular hotfix. McRip has it part of the "main updates" folder but honestly I don't see the need unless you have a laptop.
@ mcrip having issues with "Office 2013 Update Pack AUGUST 2013 x86" receiving message something like "Non existent or corrupted file. Check for AutoPlay\Docs\x86.exe". Downloaded twice and hash matches...
Faster... well to me it's relative to what you get, so maybe it would be faster but to me it's faster-for-lesser. When you install Win7 in a VM and then, instead of logging in as a user, you press CTRL-SHIFT-F3 you enter audit mode and you can reboot indefinitely and it will stay in that mode until you are ready to sysprep (the sysprep dialogue comes up automatically every time you reboot, but you can click it off when not needed yet). So then I install all the updates via a LDR-GDR script such as McRip includes. I usually divide the main body of updates into 6 or 7 folders, and put the script in each folder and install the batches in each folder, one by one, rebooting in between each batch. Then I install the WU-satisfy updates via the script that comes with it, reboot, and run WU itself to see what updates, if any are offered. So since you've rebooted you will have no pending updates and you can check on the state of your install before committing to the sysprep. You can also save that state (clone your VM) and keep it for some time in case you want to include some other updates later on (like if you know Patch Tuesday is coming or whatever). So I always keep some clean installs in VMs copied, so I can just add them to VirtualBox and start updating those images, which saves from having to install Windows each time you want to make a sysprep'd image. After you're satisfied you perform the sysprep (OOBE->Generalize->Shutdown) which takes only about 30 seconds. You will have created the VM as a VHD (VirtualBox allows this) so after sysprep you can mount the vhd straight via Disk Management and then you use imagex (I use WAIK when dealing with Win7) to capture the mounted drive to install.wim. Then you have your install.wim and you can save it into an iso.
new updates Got the following updates offered on WU on an image (W7 x64) that has latest McRip batch of updates installed: important: KB2870699 (ie10 update) KB2872339 KB2876315 KB2868116 optional: KB2574819 KB2592687 KB2853952
McRip in your changelog, you forgot the KB2859537 to remove Superseded by KB2872339 for x64 (and it's KB2790113 for x86)
KB2859537 Superseded by KB2875501 (hotfix) KB2790113 Superseded by KB2872339 McRip covered the patch tuesday updates only be patient until he completes the hotfixes scan