Jump to content

abbodi1406

Members
 View Profile  See their activity

  • Posts

    465

  • Joined

  • Last visited

  • Days Won

    196

 Content Type 

Everything posted by abbodi1406

  1. abbodi1406
    Maybe you could ask wimlib author, or use it as alternative
  2. abbodi1406
    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
  3. abbodi1406
    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)
  4. abbodi1406
    It won't stop working after 30 days
  5. abbodi1406
    SmartVersion patches are the most convenient way to get other languages ISOs http://forums.mydigitallife.info/threads/49558
  6. abbodi1406
    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
  7. abbodi1406
    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
  8. abbodi1406
    Updated
  9. abbodi1406
    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
  10. abbodi1406
    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
  11. abbodi1406
    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
  12. abbodi1406
    Can't be done including LP will need a new separate addon
  13. abbodi1406
    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
  14. abbodi1406
    Won't be Addon'ed until RTM
  15. abbodi1406
    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
  16. abbodi1406
    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
  17. abbodi1406
    That's just a regular update related to WMF i'm not sure how it's related to .NET 4.5 framework or addon
  18. abbodi1406
    Deployment Image Servicing and Management toolVersion: 6.1.7600.16385You can't service Win 8.1 image using Win 7 Dism you need Windows 8.1 ADK
  19. abbodi1406
    Windows 10 isn't supported http://www.wincert.net/forum/topic/12666-windows-10/#entry111632 http://www.wincert.net/forum/topic/12666-windows-10/#entry111635
  20. abbodi1406
    Those updates are superseded (replaced) with hotfixes but WU doesn't acknowledge those hotfixes, thus it demands for those updates you can safely ignore them, or simply let WU install them
  21. abbodi1406
    As ricktendo stated, in Windows 8.1 only some .NET updates have both GDR+LDR branches 2898847,2898850,2966826,2966828,2968296,2972103-v2,2972213,2973114,2977765,2978041,2978122,2979573,2979576there are some hotfixes that are LDR only (all are .NET related except one 2974735) 2925384-v4,3011110-v2,3000059-v3,3013375LDR is as good as GDR
  22. abbodi1406
    All updates are for Post-SP1
  23. abbodi1406
    Updated
  24. abbodi1406
    - Where? - In Options > Misc, change one of Wintoolkit Temp or Mount folder pathes btw, what are the sizes of the three partitions you have (c:, d:, f:)?
  25. abbodi1406
    - attach C:\Windows\Logs\DISM\dism.log - update your ADK to latest (Update 6.3.9600.17029) btw, since your current system is Win7SP1, why do you use ADK to update Win7 image? - you are integrating updates from D:\ , using Dism from C:\ , to Mount directory on F:\ , and Scratch (extract) directory on C:\ so the updates are extracted from d: to c: then copied to f: that's a long way try to change mount folder to C: or D: , or change Temp folder to D:
×
×
  • Create New...