Jump to content

abbodi1406

Members
  • Posts

    456
  • Joined

  • Last visited

  • Days Won

    189

Everything posted by abbodi1406

  1. 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
  2. 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
  3. Can't be done including LP will need a new separate addon
  4. 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
  5. 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
  6. 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
  7. That's just a regular update related to WMF i'm not sure how it's related to .NET 4.5 framework or addon
  8. 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
  9. 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
  10. 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
  11. - 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:)?
  12. - 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:
  13. Only this file? i don't think it's worth the trouble Wintoolkit's cleanup feature deletes all *.log files in Windows directory although, this MSDTC.LOG file is not actually a text log file, it's just a plain stream file
  14. You will have install.esd file in the iso not install.wim
  15. A copy of C:\Windows\Logs\CBS\CBS.log file would be helpful does the folder C:\Windows\WinSxS\Backup have files or it's empty? sfc error doesn't always means that the actual files in use is corrupted, sometimes the backups affected only
×
×
  • Create New...