new wzor update supersedes all cum updates, except: 2883200arm_microsoft-windows-lockscreencn_31bf3856ad364e35_6.3.9600.16408_none_b0c763cc5b9dce1b.manifest 2883200arm_microsoft-windows-mrt-v1.0_31bf3856ad364e35_6.3.9600.16404_none_bd6897043dde8fc0.manifest both may be included in the arm version of Update 1 2901101msil_microsoft.build.resources_b03f5f7f11d50a3a_4.0.9600.20487_en-us_c1d7bf93a10487c6.manifest no problem 2901101 is LDR update and already superseded I also do not believe the installation order he posted is a must, even it's a safe way. If I'm not very wrong, the "old" cum updates must not be installed before Update1 Also i do not think one has to install both updates for the service stack (or even one). It could be, that the new service stack is not necessary for those update. One indication i assume this, is, that the updates are for embedded also, but the service stack update is not. Also interesting: 2919442-1 "MSU" can not be opened with cbs package inspector (.cab opens) Just notice it superseds nearly every update (except some IIS, cameracodec, adobe,.net35,.net45).
Release public hotfixes that we're getting are going through testing and are normally being crossversion, superseding all named components and maintaining a proper history chain (unless resetbase was used). Private unreleased KBs can have fetched system files from different buildrepositories, and not always reference release components, as a result can have a walshed unserviceable system if such updates are installed (as in these builds the files are fetched not from the rtm gdr branch, but from test ones which may look alike being a supported one - just for to pass applicability checks, since Updates are meant to be applicable for all systems). If these Update 1 MSUs are installed incorrectly, most likely you will have a corrupted HAL and an unbootable system (startup repair fail). The release (RTM) is going to be crossversion and more organized.
I just wanted to say, that we will see a RTM update 1 that supersedes all older updates. The old versions of update 1 did not supersede the monthly update rollups. So if MS would have published this/or kind of this, a user has to install all of them also. The new version looks better, since it supersedes all of them. (makes a clean desk) Like always, the beta updates will not be included in KUC.
where can I download this hotfix : kb2911037 this update change ntoskrnl.exe to 16468 (my now 16452).
If you don't want to use your "real" e-mail address, just make one up. [email protected] for example.
does your system ask for this update? If not don't waste any more time on it because you might mess with the OS. I'm sure you don't have 512 GIGABITE RAM
List of NOT superseded updates after Update 1 999994mspaint hotfix 2894852.net35 update 2894856.net451 update 2897066iis hotfix 2898871.net451 update 2908387.net451 hotfix 2913236x86erratamanager 2926995.net35 hotfix 2934802adobe-flash-for-windows List of NOT superseded updates for the DVD 2898464DVD 2897942DVD 2892082DVD 2898464DVD 2914220DVD 2891213DVD 2890660DVD 2890139DVD 2913253DVD 2895233DVD (to make the "new DVD" most up to date, you also have to extract the boot-files from 2919355 (like it had to be done for 2883900DVD/2894179DVD)) List of Additions not included in Update1 917607Windows Help program Client 931125RootsUpd 976002Windows Browser Choice 2693643Remote Server Administration Tools 2790621Connector for Windows Server 2012 R2 2835517Media Feature Pack for N and KN versions of Windows 8.1 2877939ServerEssentials-MediaPack 2899189Camera Codec Pack 2917500rvkroots.exe All other updates are superseded by or included in Update1 Attention: since some components in Update1 have the same version than the "old" updates you should uninstall all of the "old" before you apply Update1 otherwise you will not be able to uninstall some of the "old" once. I hope MS will change that in the RTM version of Update1. NOTE: Leaked Update1 still not RTM (I hope)
Fresh install when UPD 1 goes RTM if MS does not come to the party on the "old" updates because I, like so many others I'm sure, use Code: DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase from the command prompt. Of course now nothing can be uninstalled the conventional way-only via cleanmgr. Thanks for the headsup Komm. Also, are all in place dynamic updates applied automatically during an inplace 8 to 8.1 upgrade and, if I have it correct, not required for a fresh 8.1 ISO (not an upgrade); 2914220DVD is a printer driver compatabilty update, also, dynamically applied. However, I have been known to be wrong.