So Microsoft releases an MSDN image as RTM / GA and then re-release the same KB update with a newer build on WU. Incredible. I miss the time when RTM was = RTM.
It's a newer build of two files. Original had .16655; new one has .16657. It's weird it wasn't released as a "-v2" of KB2939087. contains: ntfs.sys (still superseded by .17031) clfs.sys
Maybe the new one isn't much different of v1.0, that's why it's v1.1 both ntfs.sys & clfs.sys are superseded by 2934018 (.17056), so it's needed only prior installing KB2919355 (if you have trouble installing it)
Yes, thanks for the info! I haven't looked in the new ones from today yet (2934018) so I didn't see that clfs.sys was superseded by .17056. Thanks. moderate: Yes, KB2934018 supersedes KB2939087 (thx Abbodi).
17031 is the Main Base version for Windows 8.1 Update 17041 is ntoskrnl.exe version 17055 is individual components version
LOL @ M$ so much for attempting a clean ISO /w updates install yesterday. The several updates and number changes have mostly fixed my programs...just one troublesome driver with the "new" updates. I am sure it will get sorted out.
anyone has seen de_windows_8.1_with_update_x64_dvd_4048209.iso and de_windows_8.1_with_update_x86_dvd_4048128.iso ???
Nope ... a lot are waiting for it ... and it will come to those who wait, not those who permanently ask/demand .
If I am late with this, please forgive (was sleeping here in India). In win 8.1 update 1 iso of Apr, I am getting these updates: 2942844 2933809 2939087 and surprisingly 2919355 (116MB) First 3 could be fine but 2919355??
Windows Update often has version-specific packages dependent on the configuration of the user, in addition to the express full packages. An entry in the "available updates" window in the GUI, does NOT always mean that it's just the described is what is contained in the package therein. The Update comes as a msu bundle, bundling the April rollup together with the other updates, and the entry will only install what's missing. This can be fairly accurately tracked in the windowsupdate.log. In addition, components of a package aren't being updated if/when an associated feature with the package, is disabled in Windows Components, and then re-enabled post-installation of an applicable update that may contain the packages for the associated component, then an update may be re-offered, containing just the user-specific pack of the components required to be updated if applicable, instead of a full express update package.