abbodi1406

You know, imagex has a nice feature that makes the process much easier: APPEND IMAGEX [FLAGS] /COMMIT mount_path ["image_name"]Commits the changes made to a mounted image without unmounting the image. mount_path - The path of the mounted image to commit. image_name - If the /append flag is set, then a unique image name must be provided.Accepted FLAGS: /APPEND Captures the changes made to the wim into a new image in the wim. /TEMP Specifies the path where temporary files are stored.Example: imagex /commit c:\mounted_images imagex /commit /append c:\mounted_images new_image_nameso instead of copied/duplicating wim files and then re-merging, one could do it with one file: imagex /mountrw install.wim 1 c:\mountDISM /Image:c:\mount /Set-Edition:HomeBasicimagex /commit /append c:\mount HomeBasicimagex /unmount c:\mountand repeat the process for other editions afterwards, change the images' description and edition flag imagex /flags "HomeBasic" /info install.wim 2 "HomeBasic" "HomeBasic"

KB2834140 is a bi-update, it can be installed (offered) with/without platform update KB2670838 so if you installed it before KB2670838, you have to install it afterwards too

Installing WMF4.0 KB2819745 (or WMF3.0) will make KB3006625 superseded, thus removed

The 5.2 MB is KB3023607, it's bundled with both updates deepclean removes superseded updates correctly WU is the one requesting superseded updates, it's a total mess in Windows 7

Delete the two updates and re-download them

Mainstream support ended latest updated CABs: http://www.microsoft.com/en-us/download/details.aspx?id=43898

I ment to ask him about wimgapi issue, not to use wimlib instead -- prices looks OK to me.

You mean this? http://www.microsoft.com/en-us/download/details.aspx?id=40904

test5: CopyFolder now copy what inside the folder to destination, not the folder itself i.e. [CopyFolder]ASP.NET::Windows\infASP.NET contents are copied directly to Windows\inf, not the whole ASP.NET folder CopyFile works as expected i loved the detailed process percentage :')

Maybe you could ask wimlib author, or use it as alternative

The ability to copy files/folders to the WinSxS directory (as example) would be nice it's extra protected by TrustedInstaller as you know (implementing this would help) moreover, applying a wim file to the mounted image because wim preserve NT Security ACLs, and eliminates the need for extra privileges to add files to the protected directories using the current feature leads to error in mounting registry, i. e. [RUNCMD]dism.exe|/Apply-Image /ImageFile:VCredist.wim /Index:1 /ApplyDir:%WIM%this new feature if possible will help making correct complete addon for the vcredist 2005/2008 (which adds files to winsxs) it also will make it possible to create offline addon for Windows7's KB2533552

All updates in Extra (not needed for most users) Additional\_NotAllowedOffline (as there title says) Additional\WMF4.0 (require .NET 4.5 or higher to be present in image)

It won't stop working after 30 days

SmartVersion patches are the most convenient way to get other languages ISOs http://forums.mydigitallife.info/threads/49558

It was a mistake in update list (the hotfix is not set to be extracted of exe file) fixed, sorry about that redownload it or extract it manually

Each new hotfix rollup contain all previous updates, some of them are not even published last rollup have these KBs: KB2901983 KB2908383 KB2925382 KB2931368 KB2936388 KB2937676 KB2938782-v2 KB2954853-v2 KB2972107 KB2972216 KB2974336 KB2978128 KB2979578-v2 KB2996568 KB3009681 KB3011114 KB3018514 KB3022670

Updated

I don't know anything about signing or security cats replacing mum files is not a problem can be done with modifying the permissions (not recommended) or using cmd with trustedinstaller token or having the original files inside a wim file which preserve the nt security permissions, therefore can by applied using dism/imagex but like you said, install this update after OS install is not a big deal

Actually the reason is known each .mum file is paired with security .cat file to verify the contents modifying mum file cause the failed integrity check “Installed Updates” scans packages mum files in \Windows\servicing\Packages and make a cache database for it in \Windows\WinSxS\ManifestCache

Yes i know the files are the same and the modded cab will give functional servicing stack for modded or lited editions/aio this is not a problem but for users whou care about updates or WU, this would be a problem MS made that update exclusive for a reason there is a workaround for this issue, by replacing the altered mum/manifest files with the original ones after integrating the update but that would require RunasSystem/RunFromToken to be able to replace the files without changing permissions

Can't be done including LP will need a new separate addon

Modifying update.mum file will result later in failed integrity check, specially when using System Update Readiness Tool or checking "Installed updates" in control panel

Won't be Addon'ed until RTM

4.x updates can be satisfied with LDR however, some 3.x updates require GDR to satisfy WU (KB2894852, KB2972213, KB2973114, KB2979573) like i said, both branches are OK regular hotfixes are already GDR only .NET hotfixes are already LDR only so, normal integration mode is the only available

LDR branch is practically deactivate/dead in Windows 8.1, almost all updates have only the normal GDR branch yes this includes hotfixes only some .NET (3.5 and 4.5) updates and hotfixes are having LDR, which is understandable because those frameworks are shared with other windows systems (7, 8) problems or issues happens in any updates (most botched updates are GDR) so, installing those .NET updates in LDR mode would be recommended