Just the spring2014 updated versions of 8.1 There's no point including 7 and 8 with them. People can build their own mega-aio versions later with the source indexes if they want.
Are you going to include next Tuesday's updates from Microsoft (if any) or will they be in a later update? Just wondering?
I have installed all six MSU in the right order. All is working very well but I can't execute Internet Explorer any more. I had created a restore point before installing Update 1. When I restore the system as it was before the installation, Internet Explorer is working well. If I reinstall Update 1, Internet Explorer does not open. Any ideas ? Excuse my English.
The more I think about this leak the less likely I would do anything with it right now. Update 1 is probably RTM here but it's those other MSU files that worry me. Doing this for a living for 12 years I know Microsoft can push out some foal updates that break functionality. These perquisite patches actually can fix issues that are in the RTM. We don't even know all the MSUs that will be released next week, could be some fixes there and some more in April.
Has anybody here happened to install this update on a system with an LSI SAS 9211-8i HBA card in use? Builds 17024 and 17025 seemed to render the OS unbootable after installing KB2919355, and its the same for 17031, at least in my experiences since my desktop has this card with an SSD RAID0 configured.
Few weeks back things went wrong for me (the first leaked update) and I was not able to uninstall, but I was able to restored, I only had one restoration point and I chose it!!
I hope people understand that they might still find bugs between now and Apr 8th when the Spring Update will be out to the gen public. Some of these "bugs", if these are bugs with the update, would prob be patched with an update after the Spring Update or with the Spring Update has been added to WU. This is why it is always best to just test on a VM till it comes out to the gen public and not on your main PC.
People will find bugs even after April 8th, this is the nature of the fallible man especially when writing software.... Even more so if it carries the M$ logo..
Can confirm some little bugs regarding Modern UI (in my case caused by using Custom Theme) ... but hey who cares . Didn't use that crap in the past and definitely won't start now . Rest works smooth on my ProfessionalWMC (Retail activation gifted by MS ).
True, if you aren't entirely confident about installing it on your own machine then VMs are a good choice. Personally I've always tended to dogfood pre-release MS products and updates on the systems that I sit down and use everyday as I have always found that's the ultimate test to get a feel for the product so to speak. If something breaks I can deal with it, plus I have good working backups anyway which are regularly tested.
Something is wrong with this procedure. I cannot get Windows Setup to run after installing these updates and doing resetbase. It whines about drivers. I've tried swapping the setup files with the versions from the newer bing leak as well, no dice... I don't know if they work without resetbase, but there's no point using the updates without resetbase because the boot.wim gets too large. I've already verified that the boot.wim works fine without the updates. I'm going to file this endeavor under "cool, but not working for now" I've tested multiple different integration methods, including the verbatim method from the ADK chm: Add the Windows 8.1 updates to the image Mount the Windows PE image. Dism /Mount-Image /ImageFile:"C:\WinPE_amd64\media\sources\boot.wim" /index:1 /MountDir:"C:\WinPE_amd64\mount" Add the Windows 8.1 Update into Windows PE. This is the same package used to update Windows 8.1: Dism /Add-Package /PackagePath:C:\MSU\Windows8.1-KB2919442-x64.cab /Image:C:\WinPE_amd64\mount /LogPath:AddPackage.log Dism /Add-Package /PackagePath:C:\MSU\Windows8.1-KB2919355-x64.cab /Image:C:\WinPE_amd64\mount /LogPath:AddPackage.log Dism /Add-Package /PackagePath:C:\MSU\Windows8.1-KB2932046-x64.cab /Image:C:\WinPE_amd64\mount /LogPath:AddPackage.log Optimize the image: Dism /image:c:\WinPE_amd64\mount /Cleanup-Image /StartComponentCleanup /ResetBase Unmount the Windows PE image. Dism /Unmount-Image /MountDir:"C:\WinPE_amd64\mount" /commit
I'm almost done with it actually. It just won't have those superfluous updates that don't seem to be required. I'm going to try a last-ditch effort and toss in a wpeinit.exe call in the winpeshl.ini and see if that works, but if it doesn't I'm out of ideas on those updates...
@josef00 Its confirmed by me (the Spring Update is a cumulative update, so it contains all of the previous updates & hotfixes).