Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by abbodi1406

  1. I got the same error: Thursday 01 January 2015 22:48:09 PM +03:00 Arab Standard TimeLog ID: 1xE2D811AEEC8CFA66AA57F586152675CE_frmStartup_en-US_376223***BASIC***Update Cache item error***EXTENDED***Items: 1String was not recognized as a valid DateTime.Windows6.1-KB969168-x64.cab|2540846|Microsoft-Windows-Agent-Package-TopLevel|6.1.7600.16426|GDR|X64|3405F2765E669BFD9CFACC1CD2BED450|Microsoft Agent|Neutral|6.1|http://www.microsoft.com/msagent/|21/12/2014 21:49:48
  2. 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
  3. 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
  4. 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
  5. 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
  6. - 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:)?
  7. - 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:
  8. All the errors in you log indicates ACCESS DENIED if you have Anti-virus, stop it, real time scanning may prevent the process and you may try this fix: http://support.microsoft.com/kb/968003
  9. Does the actual dism report 6.1.7601.17514? for me i get 6.1.7600.16385 on x64 system: it seems something not solid, so 6.1.7600.16385 doesn't always means RTM sorry for hijacking your thread hayedeh
  10. 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
  11. You will have install.esd file in the iso not install.wim
  12. Just a cosmetic reason to modifiers, so the iso looks as new It's working here as expected make sure you select a correct valid folder to create iso
  13. When using x86 dism, the Win7 SP1 x64 version is reported as 6.1.7601.17514 but when using x64 dism, the Win7 SP1 x64 is reported as 6.1.7600.16385 the cause of this confusion is when servicing x64 image using x86 dism, Windows\SysWOW64\Dism\DismHost.exe from the image is used (and its version 6.1.7601.17514) but when servicing it using x64 dism, Windows\System32\Dism\DismHost.exe is used (and its version is 6.1.7600.16385)
  14. Unlike x86, Win7 SP1 x64 image version in default is reported by dism as 6.1.7600.16385
  15. The option is to make all files in ISO to have the same date as install.wim file, it's not for altering the modification date of the images inside install.wim
  16. 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
  17. If he used latest dotNetFx452_Full_LDR_x86_x64_Slim.exe, it's already includes all .NET 4.5 updates, so no need for them separately
  18. As soon as new updates founded the big one would be after monthly patch tuesday you can see or monitor the changes Here
  19. Both addons works for Both Windows 7 and Windows 8/8.1 but the Full as noted, require enabling .NET 3.5 Framework in Windows 8/8.1, because Managed Code relies on .NET 2.0 (part of 3.5)
  20. It's not working for me somehow, i got the same result with or without it next to WinToolkit.exe i made the test on install.wim without DVD
  21. .NET 3.5.1 updates has nothing to do with this addon, separate products as for the other two KB2972107 and KB2979578, they are icluded in the hotfix rollup and should not be showing in WU the ini file have the cause, you used older addon #AddonsD:\Test\Win7\WTK\AddOn\dotNetFx452_x64.Windows7.AddOn.Regular.20140920.WA
  • Create New...