Well no offense to this user since I dont know who he is but I already posted this info 3 or 4 posts above his. The difference between mine and his... I post from where mine came from, he never does.
Just curious about all of this - is anyone aware of why there is reluctance surrounding this leak? I haven't been reading on the various forums myself, just checking here for news. Is there a reason for the hesitation on this?
I don't think anyone knows much of what if anything it actually fixes. From what I've seen, integrating the update allows people to boot the first time into desktop mode bypassing the need to right-click the taskbar and check the box for people without touchscreens. Other than that it just seems like a huge bloated mess to allow people to pin store apps to their taskbar. *twirls finger* I dunno. I'm a bit pessimistic on large updates like this, but who knows? perhaps it could have performance fixes. I wish MS would come out with an official list with the things it fixes.
Indeed. Has it been confirmed that some of the "usual" leakers have access to the MSU files? I am just curious about, if access to those files exists, what is the hesitation from the "usual" leakers on leaking them?
I hate friday because I have to install a pc and cannot take the latest updates for this because they only wait
Microsoft.windows.8.1.and.server.2012.r2.spring.20 14.update.adk.kit.eeap.english-wzt i think murphy78 will love this Code: MICROSOFT.WINDOWS.8.1.AND.SERVER.2012.R2.SPRING.2014.UPDATE.ADK.KIT.EEAP.ENGLISH-WZT RELEASE DATE: 02/19/2014 FILES: ADK_140219-1702.zip SIZE: 3,182,812,377 byte SHA-1: EDF880A13DBB3FA4BB9CBDB13B2CF395D3172E15 MD5: 9927B91EBFFDA43025D1064ECF19F091 NOTE: this is original M$ files. EEAP - Ecosystem Engineering Access Program What’s New in Windows 8.1 Update? Windows image file boot (WIMBoot) New for Windows 8.1 Update, devices can be configured to boot and run Windows directly from a .wim file. This provides several benefits: • Windows can run on smaller solid state drives • Increases available disk space for end users • Reduces OEM manufacturing time To support WIMBoot, you will need updated versions of Windows PE and DISM. In addition, you will need to change some of your existing Windows customizations, recovery configurations and manufacturing workflows. This includes: • Windows PE is updated to support WIMBoot. You will need to recreate your Windows PE images to support WIMBoot. • DISM includes new command line parameter, such as /WIMBoot. When capturing and applying images, you must use this new parameter. • You can use your WIM Boot image as a recovery image, saving disk space. You will have to update your recovery configuration and disk partition layout on the devices you build. WIMBoot is only supported on Windows 8.1 Update images with the Windows 8.1 Update version of the Windows ADK. For more information about WIMBoot, see the following topics in ADK_Online.chm file. Note that DISM PowerShell cmdlets are documented in DISM_Cmdlets.doc included in this documentation package. Create and deploy WIMBoot images: • WIMBoot: Windows image file boot (WIMBoot) • Create WIMBoot Images • Deploy WIMBoot Images DISM Command line options: • What's New in DISM • DISM Image Management Command-Line Options • DISM Windows Edition-Servicing Command-Line Options Installing Windows 8.1 Update In this EEAP release, Windows 8.1 Update is available as an MSU file. You can update your existing Windows 8.1 images by applying the update. by WZT 03|05|14 Code: ADK_140219-1702.NFO ADK_140219-1702.zip ADK_Online.chm ADK_ReleaseNotes.pdf MICROSOFT.WINDOWS.8.1.AND.SERVER.2012.R2.SPRING.2014.UPDATE.ADK.KIT.EEAP.ENGLISH-WZT.NFO
I believe the meant MSU file is for ADK's new feature (WimBoot), not the whole general spring update this is basically new ADK version