Just another cumulative for build 10240 (which have LTSB) LTSB will never be 10586 and an update will never transfer one build to another, that's ESD/ISO job when an update is named "for Windows 10" = build 10240 and "for Windows 10 Version 1511" = build 10586 it's not the first time and won't be the last
Microsoft has been bypassing recent Insider Preview builds with cumulative updates. One would think IP users have the right to receive the fixes first before the general public.
Today I did my first AIO (Win10) and $oem$ folder with a setupcomplete.cmd and OEM Branding. It worked as expected even with all updates integrated via sysprep.
Has Any one can help ??? i integrated KB3140768 with offline mode but has be error ~ Processing 1 of 1 - Adding package Package_for_KB3140768~31bf3856ad364e35~amd64~ ~10.0.1.3 [==========================100.0%==========================] Error: 14099 The specified image is no longer serviceable and may be corrupted. Discard the modified image and start again. Package Package_for_KB3140768 may have failed due to pending updates to servicin g components in the image. Try the command again.Package Package_for_KB3144756 m ay have failed due to pending updates to servicing components in the image. Try the command again.The command completed with errors. For more information, refer to the log file. i have already add the KB3140741 services stuck , after it i add the KB3140768 has be error , has any one know what problem about it ??? thanks for the information ..... now i need to solve becos i stuk at KB3140768 cant be integrated
actually it's for any w10 build after 10240 including insider previews Code: assembly version: 4.0.10608.16393 files version : 4.6.1532.0 [/QUOTE] It says it's not applicable to insider preview build 14291, even if installed manually. The files version is 4.6.1528 on the insider preview though, not sure of the assembly version. I guess maybe the code is different in the Redstone Insider preview than TH2 Windows 10.
The 'any w10 build' is a theoretical sentence, based on update.mum applicability info since that latest 14xxx previews already include 4.6.2 (regardless the older version), it won't need this just like 10586 including 4.6.1 as for assembly version, i'm sure it's like 4.0.14291.1001, so it takes precedence
True, and we'll probably get files 4.6.1532.0 or newer in the next build anyway. People, don't forget to recompile runtime targets after installation of the update. This can be done easily with the Easy Ngen runner in my sig.