abbodi1406
-
Posts
458 -
Joined
-
Last visited
-
Days Won
191
Content Type
Profiles
Forums
Events
Posts posted by abbodi1406
-
-
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
-
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
-
As soon as new updates founded
the big one would be after monthly patch tuesday
you can see or monitor the changes Here
-
-
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
-
I would say it's permanent
-
.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
-
-
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
-
It's not recommended to change it, certain system function relies on it (like wmic.exe)
-
HKEY_LOCAL_MACHINE\WIM_SOFTWARE\Microsoft\Windows NT\CurrentVersion
-
The result is the same.
-
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
-
- Never haved Vista, therefore, no
- If the mechanism is still like Windows 8.x, yes i could and probably will
-
Never encountered such error
i even copied Wintoolkit to system drive root which is usually extra UAC protected, still works
-
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 -
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
-
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 -
It`s the same thing for windows xp integration? if i put only framework 4 it has framework 1,2,3,3,5? or i have to put them all?
Yes same thing, framework 4 is separate from 3.5 and below
XP don't have any, so you need to put them all
-
He means x64-based edition of Wintoolkit
-
-
- Popular Post
- Popular Post
Description:
The Visual C++ Redistributable Packages install runtime components that are required to run applications that are developed by using Visual Studio. These packages install run-time components of these libraries: C Runtime (CRT), Standard C++, ATL, MFC, C++ AMP, OpenMP and MSDIA. read more.
OS: Windows All
Versions:VC++ 2022: 14.40.33807.0 VC++ 2013: 12.0.40664.0 VC++ 2012: 11.0.61135.400 VC++ 2010: 10.0.40219.473 VC++ 2008: 9.0.30729.7523 VC++ 2005: 8.0.61187 VC++ 2003: 7.10.6119.0 Vc++ 2002: 7.0.9975.0 + Legacy Visual Basic Runtimes
Files Contents:
vcredist_x64_Win7 / vcredist_x86_Win7: All runtimes for Windows 7 SP1 vcredist_x64_2022_WinAll / vcredist_x86_2022_WinAll: Visual C++ 2022 vcredist_x64_2013d_WinAll / vcredist_x86_2013d_WinAll: Visual C++ 2013, 2012, 2010, 2003, 2002 Visual Basic 6.0 Runtimes vcredist_x64_SxS_Win7 / vcredist_x86_SxS_Win7: Visual C++ 2008, 2005 for Windows 7 SP1 vcredist_x64_SxS_Win810 / vcredist_x86_SxS_Win810: Visual C++ 2008, 2005 for Windows 8.1/10
Important Notes:
# Integrating SxS 2008/2005 addons require launching Wintoolkit with TrustedInstaller privileges, to gain write access to WinSxS directory
for that, you need to use NSudo (or other similar tools):
- download and extract latest release Binary.zip
- launch Win32\NSudo.exe or x64\NSudo.exe, or run NSudo.bat as administrator
- make sure User is set to TrustedInstaller
- check "Enable All Privileges"
- paste Wintoolkit.exe path in the lower box (or Browse to the file)
- click runif you are using Windows 7 Simplix Update Pack, you don't need that, it already handle the required privileges
# vcredist_x64_Win7 / vcredist_x86_Win7 is AIO addon, mainly to be used with Simplix Update Pack, or else you need Wintoolkit with NSudo
# VC++ 2022 runtimes are binary compatible and upgrade to VC++ 2015-2017-2019 and cover all VS 2015-2017-2019-2022 programs
# To complete VC++ 2022 functions for Windows 7/8.1, you need to integrate Universal CRT components, which is available with latest Monthly Rollup, or updates KB3118401/KB2999226
Download:
vcredist_x64_Win7_20240411.WA
vcredist_x86_Win7_20240411.WAvcredist_x64_2022_WinAll_14.40.33807.WA
vcredist_x86_2022_WinAll_14.40.33807.WAvcredist_x64_2013d_WinAll.WA
vcredist_x86_2013d_WinAll.WAvcredist_x64_SxS_Win7.WA
vcredist_x86_SxS_Win7.WAvcredist_x64_SxS_Win810.WA
vcredist_x86_SxS_Win810.WAyou can find latest releases -> here
SHA1 checksums:
05e938f354c059d89d846d2e9a7591d05154aa70 *vcredist_x64_2013d_WinAll.WA 534f1e53080819aeb58e3b060d7c6a0a76b4d4d4 *vcredist_x86_2013d_WinAll.WA 8cc9f65fc444a878d8cabd0ad317597edb552f07 *vcredist_x64_SxS_Win7.WA 886faa949e7d51a40dc8d467f65c373f887c2ec3 *vcredist_x86_SxS_Win7.WA 94e267e5e6ff89854bd64b6260333664a266c754 *vcredist_x64_SxS_Win810.WA 206fda69fa2d3fd838dd9e3ee33f35c4cd7a2cae *vcredist_x86_SxS_Win810.WA
Credits to ricktendo for original repack AIO
- kalilou, salam mohibach, PheoBlue69 and 19 others
-
19
-
3
-
Description:
The Microsoft DirectX® End-User Runtime provides updates to 9.0c and previous versions of DirectX — the core Windows® technology that drives high-speed multimedia and games on the PC. read more.
Info: The addon will Slipstream DirectX runtimes into the windows image as Pre-Installed
OS: Windows 7 / 8 / 8.1 - x86 / x64
Version: 9.29.1974
Download:
DirectX_June2010_x86.WA
Mirror - Mirror
Size: 13.13 MB
MD5 : 19d9de7038fc9f869e3126f20a785785
SHA1: a2a0880986ed464403035822d296fc2b76f7ff25
DirectX_June2010_x64.WA
Mirror - Mirror
Size: 27.83 MB
MD5 : 78797de2739070bbc6329bc52a75d440
SHA1: 7244d80c532c882a0a945d9d97e0067dd0b35294
Note: on Windows 8/8.1/10 you need first to enable .NET Framework 3.5 feature
- izeadot, niTe_RiDeR_Pr0, Ali Sahandi and 5 others
-
6
-
2
-
No can do
maybe i will, but no promises
ISO Modify dateI
in Win Toolkit
Posted
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