Jump to content

abbodi1406

Members
  • Content Count

    362
  • Joined

  • Last visited

  • Days Won

    86

Everything posted by abbodi1406

  1. 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
  2. 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
  3. You will have install.esd file in the iso not install.wim
  4. 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
  5. 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)
  6. Unlike x86, Win7 SP1 x64 image version in default is reported by dism as 6.1.7600.16385
  7. 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
  8. 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
  9. 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
  10. As soon as new updates founded the big one would be after monthly patch tuesday you can see or monitor the changes Here
  11. 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)
  12. 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
  13. .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
  14. Well, the detailed recipe is not easy to explain, but it depends mainly on any install monitor program to capture the changes in files and registry for me i use Total Uninstall 6 Portable and after that the captured registry keys will need some slight modifications to suite things up
  15. It's not recommended to change it, certain system function relies on it (like wmic.exe)
  16. HKEY_LOCAL_MACHINE\WIM_SOFTWARE\Microsoft\Windows NT\CurrentVersion
  17. Nothing different, mine is kind of preinstall the package manually and saves install time later ricktendo's and yumeyao's install the package after installing the system regarding managed code, don't know for sure
  18. - Never haved Vista, therefore, no - If the mechanism is still like Windows 8.x, yes i could and probably will
  19. Never encountered such error i even copied Wintoolkit to system drive root which is usually extra UAC protected, still works
  20. Yes it makes an important difference regarding how junction points and symbolic links are captured / managed inside the wim don't know the exact details or behavior, but the option RP_FIX is always set in microsoft releases (all wim files), that should be a strong clue Edit: here's a clear explanation i think: http://blogs.technet.com/b/zhou_minxiao/archive/2007/04/05/what-is-norpfix-switch-and-what-does-it-do.aspx so, it's necessary, but neither two options affect size
  21. I recommend checking for %MOUNT%\Windows\winsxs\pending.xml if exist, StartComponentCleanup process will not work and regarding SPSuperseded, it's useful only for Win7 RTM + SP1 i don't think we will see Service Packs for Windows anymore
  22. I'm not really familiar to PE projects or used it before a direct test failed as expected: i know that the correct way will be by creating .script or plugin like the one used for .NET 2/3 in Win7PE SE, but would require some skills and walking through i'll see if i could
×
×
  • Create New...