Everything posted by abbodi1406
-
Microsoft .NET Framework 4.8 for Windows 7
Updated
-
WinToolkit does not work!
- 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:)?
-
WinToolkit does not work!
- 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:
-
WinToolokit 1.5.3.2 Bug
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
-
WinToolokit 1.5.3.2 Bug
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
-
WTK fails sfc /scannow
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
-
microsoft media creation toolkit
You will have install.esd file in the iso not install.wim
-
ISO Modify dateI
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
-
WinToolokit 1.5.3.2 Bug
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)
-
WinToolokit 1.5.3.2 Bug
Unlike x86, Win7 SP1 x64 image version in default is reported by dism as 6.1.7600.16385
-
ISO Modify dateI
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
-
WTK fails sfc /scannow
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
-
Silent install wont start after W7x64 installed
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
- UpdateLists info
-
Microsoft DirectX End-User Runtimes (June 2010)
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)
-
UpdateCache Test
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
-
Microsoft DirectX End-User Runtimes (June 2010)
I would say it's permanent
-
Microsoft .NET Framework 4.8 for Windows 7
.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
-
Microsoft .NET Framework 4.8 for Windows 7
Updated
-
Microsoft .NET Framework 4.8 for Windows 7
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
-
SOLVED [WIM Manager] Missed sub-string
It's not recommended to change it, certain system function relies on it (like wmic.exe)
-
SOLVED [WIM Manager] Missed sub-string
HKEY_LOCAL_MACHINE\WIM_SOFTWARE\Microsoft\Windows NT\CurrentVersion
-
Microsoft DirectX End-User Runtimes (June 2010)
The result is the same.
-
Microsoft DirectX End-User Runtimes (June 2010)
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
-
Microsoft .NET Framework 4.8 for Windows 7
- Never haved Vista, therefore, no - If the mechanism is still like Windows 8.x, yes i could and probably will