Jump to content

abbodi1406

Members
  • Content Count

    379
  • Joined

  • Last visited

  • Days Won

    106

Reputation Activity

  1. Like
    abbodi1406 got a reaction from dingo in Microsoft .NET Framework 4.8 for Windows 7   
    Description:
     
    The .NET Framework is a popular development platform for building apps for Windows, Windows Store, Windows Phone, Windows Server, and Windows Azure. The .NET Framework platform includes the C# and Visual Basic programming languages, the common language runtime, and an extensive class library. read more.
     
    Info: The .NET package will be slipstreamed as pre-installed
    OS: Windows 7 SP1
    Notes:
    - The addon will conflict with some Windows Updates (.NET 3.5 Family), so leave the addon's integration to the last.
    - Add main addon first before LangPack addon, to get ASP.NET service localization properly.
    - To function properly, .NET 4.7.x require D3DCompiler_47.dll component, which is found in either the current "Monthly Quality Rollup" or "update KB4019990". It is recommended to integrate it first, or you can install it later.
    Windows6.1-KB4019990-x64.msu
    Windows6.1-KB4019990-x86.msu
    .NET 4.8:
    .NET 4.7.2:
    Languages Codes Reference:
     
  2. Like
    abbodi1406 reacted to Thiersee in WinToolkit does not work!   
    This is the wrong screenshot !
    I meant "Options/Misc." in WTK-first-window NOT Options in the AIO.
     
    1), 2), 3): OK.
     
    a) No, your working DISM, either in C:\Windows\System32 or C:\Program Files x86\Windows Kits....; OK, I see you are using Windows ADK .
     
     
     
    @abbodi1406:
     
    Lego should update the download-link for the new version!
     
    Thiersee
  3. Like
    abbodi1406 got a reaction from Troubadix in Visual C++ Redistributable Runtimes   
    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++ 2019: 14.27.28914.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_2019_WinAll / vcredist_x86_2019_WinAll: Visual C++ 2019 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 run
    if 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++ 2019 runtimes are binary compatible and upgrade to VC++ 2015-2017 and cover all VS 2015-2017-2019 programs
    # To complete VC++ 2019 function 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_20200604.WA
    vcredist_x86_Win7_20200604.WA
    vcredist_x64_2019_WinAll_14.27.28914.WA
    vcredist_x86_2019_WinAll_14.27.28914.WA
    vcredist_x64_2013d_WinAll.WA
    vcredist_x86_2013d_WinAll.WA
    vcredist_x64_SxS_Win7.WA
    vcredist_x86_SxS_Win7.WA
    vcredist_x64_SxS_Win810.WA
    vcredist_x86_SxS_Win810.WA
    you can find latest releases -> here
    SHA1 checksums:
    9265d0f6857752c7cf9ade625b39a4b9a1e9d158 *vcredist_x64_Win7_20200321.WA 146491bbb05532100ce9111c253a7cac7d7ae89b *vcredist_x86_Win7_20200321.WA 91408b22b460473fd770c2965335d9bfc685006a *vcredist_x64_2019_WinAll_14.26.28619.WA 80e03ce6bb4c6f07f7c5bfae3291b252b74f1b58 *vcredist_x86_2019_WinAll_14.26.28619.WA 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
  4. Like
    abbodi1406 got a reaction from Troubadix in Microsoft .NET Framework 4.8 for Windows 7   
    Description:
     
    The .NET Framework is a popular development platform for building apps for Windows, Windows Store, Windows Phone, Windows Server, and Windows Azure. The .NET Framework platform includes the C# and Visual Basic programming languages, the common language runtime, and an extensive class library. read more.
     
    Info: The .NET package will be slipstreamed as pre-installed
    OS: Windows 7 SP1
    Notes:
    - The addon will conflict with some Windows Updates (.NET 3.5 Family), so leave the addon's integration to the last.
    - Add main addon first before LangPack addon, to get ASP.NET service localization properly.
    - To function properly, .NET 4.7.x require D3DCompiler_47.dll component, which is found in either the current "Monthly Quality Rollup" or "update KB4019990". It is recommended to integrate it first, or you can install it later.
    Windows6.1-KB4019990-x64.msu
    Windows6.1-KB4019990-x86.msu
    .NET 4.8:
    .NET 4.7.2:
    Languages Codes Reference:
     
  5. Like
    abbodi1406 got a reaction from robertcollier4 in Visual C++ Redistributable Runtimes   
    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++ 2019: 14.27.28914.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_2019_WinAll / vcredist_x86_2019_WinAll: Visual C++ 2019 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 run
    if 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++ 2019 runtimes are binary compatible and upgrade to VC++ 2015-2017 and cover all VS 2015-2017-2019 programs
    # To complete VC++ 2019 function 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_20200604.WA
    vcredist_x86_Win7_20200604.WA
    vcredist_x64_2019_WinAll_14.27.28914.WA
    vcredist_x86_2019_WinAll_14.27.28914.WA
    vcredist_x64_2013d_WinAll.WA
    vcredist_x86_2013d_WinAll.WA
    vcredist_x64_SxS_Win7.WA
    vcredist_x86_SxS_Win7.WA
    vcredist_x64_SxS_Win810.WA
    vcredist_x86_SxS_Win810.WA
    you can find latest releases -> here
    SHA1 checksums:
    9265d0f6857752c7cf9ade625b39a4b9a1e9d158 *vcredist_x64_Win7_20200321.WA 146491bbb05532100ce9111c253a7cac7d7ae89b *vcredist_x86_Win7_20200321.WA 91408b22b460473fd770c2965335d9bfc685006a *vcredist_x64_2019_WinAll_14.26.28619.WA 80e03ce6bb4c6f07f7c5bfae3291b252b74f1b58 *vcredist_x86_2019_WinAll_14.26.28619.WA 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
  6. Like
    abbodi1406 got a reaction from Kontus in Microsoft DirectX End-User Runtimes (June 2010)   
    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
    Size: 13.13 MB
    MD5 : 19d9de7038fc9f869e3126f20a785785
    SHA1: a2a0880986ed464403035822d296fc2b76f7ff25
     
    DirectX_June2010_x64.WA
    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
  7. Like
    abbodi1406 got a reaction from izeadot in Microsoft DirectX End-User Runtimes (June 2010)   
    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
    Size: 13.13 MB
    MD5 : 19d9de7038fc9f869e3126f20a785785
    SHA1: a2a0880986ed464403035822d296fc2b76f7ff25
     
    DirectX_June2010_x64.WA
    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
  8. Like
    abbodi1406 reacted to Legolash2o in WinToolkit x64?   
    I guessed but it's already set as AnyCPU so no performance benefits would be seen setting it to x64.
  9. Like
    abbodi1406 got a reaction from niTe_RiDeR_Pr0 in Microsoft DirectX End-User Runtimes (June 2010)   
    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
    Size: 13.13 MB
    MD5 : 19d9de7038fc9f869e3126f20a785785
    SHA1: a2a0880986ed464403035822d296fc2b76f7ff25
     
    DirectX_June2010_x64.WA
    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
  10. Like
    abbodi1406 got a reaction from ebiyahya in Visual C++ Redistributable Runtimes   
    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++ 2019: 14.27.28914.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_2019_WinAll / vcredist_x86_2019_WinAll: Visual C++ 2019 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 run
    if 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++ 2019 runtimes are binary compatible and upgrade to VC++ 2015-2017 and cover all VS 2015-2017-2019 programs
    # To complete VC++ 2019 function 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_20200604.WA
    vcredist_x86_Win7_20200604.WA
    vcredist_x64_2019_WinAll_14.27.28914.WA
    vcredist_x86_2019_WinAll_14.27.28914.WA
    vcredist_x64_2013d_WinAll.WA
    vcredist_x86_2013d_WinAll.WA
    vcredist_x64_SxS_Win7.WA
    vcredist_x86_SxS_Win7.WA
    vcredist_x64_SxS_Win810.WA
    vcredist_x86_SxS_Win810.WA
    you can find latest releases -> here
    SHA1 checksums:
    9265d0f6857752c7cf9ade625b39a4b9a1e9d158 *vcredist_x64_Win7_20200321.WA 146491bbb05532100ce9111c253a7cac7d7ae89b *vcredist_x86_Win7_20200321.WA 91408b22b460473fd770c2965335d9bfc685006a *vcredist_x64_2019_WinAll_14.26.28619.WA 80e03ce6bb4c6f07f7c5bfae3291b252b74f1b58 *vcredist_x86_2019_WinAll_14.26.28619.WA 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
  11. Thanks
    abbodi1406 got a reaction from unwanted_69 in Microsoft .NET Framework 4.8 for Windows 7   
    Description:
     
    The .NET Framework is a popular development platform for building apps for Windows, Windows Store, Windows Phone, Windows Server, and Windows Azure. The .NET Framework platform includes the C# and Visual Basic programming languages, the common language runtime, and an extensive class library. read more.
     
    Info: The .NET package will be slipstreamed as pre-installed
    OS: Windows 7 SP1
    Notes:
    - The addon will conflict with some Windows Updates (.NET 3.5 Family), so leave the addon's integration to the last.
    - Add main addon first before LangPack addon, to get ASP.NET service localization properly.
    - To function properly, .NET 4.7.x require D3DCompiler_47.dll component, which is found in either the current "Monthly Quality Rollup" or "update KB4019990". It is recommended to integrate it first, or you can install it later.
    Windows6.1-KB4019990-x64.msu
    Windows6.1-KB4019990-x86.msu
    .NET 4.8:
    .NET 4.7.2:
    Languages Codes Reference:
     
  12. Like
    abbodi1406 got a reaction from Extended in Microsoft .NET Framework 4.8 for Windows 7   
    Updated
     
    only Regular Addon this time
    if you want the Full use the previous one, or copy netfx_Full_LDR.mzz file of it
  13. Like
    abbodi1406 reacted to Kelsenellenelvian in workgroup   
    Your answers are very argumentative and counter productive. I am doing my job here as staff to protect WinCerts interests and you are being grossly disrespectful. WinCert absolutely HAS to obey licensing laws or our funding from adsense and our servers will be pulled and shut down.
     
    I am going to give you a 3 day vacation from your ability to post here and see if you can come back a bit more respectful. 
     
    Also I am still removing you link because that is still against copyright laws as you cannot redistribute that file without RealVNC's permission. (A simple link to thier site is enough) 
  14. Like
    abbodi1406 got a reaction from Tony003 in Microsoft .NET Framework 4.8 for Windows 7   
    Description:
     
    The .NET Framework is a popular development platform for building apps for Windows, Windows Store, Windows Phone, Windows Server, and Windows Azure. The .NET Framework platform includes the C# and Visual Basic programming languages, the common language runtime, and an extensive class library. read more.
     
    Info: The .NET package will be slipstreamed as pre-installed
    OS: Windows 7 SP1
    Notes:
    - The addon will conflict with some Windows Updates (.NET 3.5 Family), so leave the addon's integration to the last.
    - Add main addon first before LangPack addon, to get ASP.NET service localization properly.
    - To function properly, .NET 4.7.x require D3DCompiler_47.dll component, which is found in either the current "Monthly Quality Rollup" or "update KB4019990". It is recommended to integrate it first, or you can install it later.
    Windows6.1-KB4019990-x64.msu
    Windows6.1-KB4019990-x86.msu
    .NET 4.8:
    .NET 4.7.2:
    Languages Codes Reference:
     
  15. Thanks
    abbodi1406 got a reaction from ebiyahya in Microsoft .NET Framework 4.8 for Windows 7   
    Description:
     
    The .NET Framework is a popular development platform for building apps for Windows, Windows Store, Windows Phone, Windows Server, and Windows Azure. The .NET Framework platform includes the C# and Visual Basic programming languages, the common language runtime, and an extensive class library. read more.
     
    Info: The .NET package will be slipstreamed as pre-installed
    OS: Windows 7 SP1
    Notes:
    - The addon will conflict with some Windows Updates (.NET 3.5 Family), so leave the addon's integration to the last.
    - Add main addon first before LangPack addon, to get ASP.NET service localization properly.
    - To function properly, .NET 4.7.x require D3DCompiler_47.dll component, which is found in either the current "Monthly Quality Rollup" or "update KB4019990". It is recommended to integrate it first, or you can install it later.
    Windows6.1-KB4019990-x64.msu
    Windows6.1-KB4019990-x86.msu
    .NET 4.8:
    .NET 4.7.2:
    Languages Codes Reference:
     
  16. Like
    abbodi1406 got a reaction from Kontus in Microsoft .NET Framework 4.8 for Windows 7   
    Description:
     
    The .NET Framework is a popular development platform for building apps for Windows, Windows Store, Windows Phone, Windows Server, and Windows Azure. The .NET Framework platform includes the C# and Visual Basic programming languages, the common language runtime, and an extensive class library. read more.
     
    Info: The .NET package will be slipstreamed as pre-installed
    OS: Windows 7 SP1
    Notes:
    - The addon will conflict with some Windows Updates (.NET 3.5 Family), so leave the addon's integration to the last.
    - Add main addon first before LangPack addon, to get ASP.NET service localization properly.
    - To function properly, .NET 4.7.x require D3DCompiler_47.dll component, which is found in either the current "Monthly Quality Rollup" or "update KB4019990". It is recommended to integrate it first, or you can install it later.
    Windows6.1-KB4019990-x64.msu
    Windows6.1-KB4019990-x86.msu
    .NET 4.8:
    .NET 4.7.2:
    Languages Codes Reference:
     
  17. Like
    abbodi1406 reacted to bphlpt in Windows Installation - Where I can change the modification date   
    1 ) Take the DateToIntegr8.vbs script above, (just delete the .txt part of the name) and save it wherever you want, say C:\time.
    2 ) Then open a command prompt in that directory.
    3 ) Enter the following command: cscript DateToInteger8.vbs "06/09/2014 10:30:00 PM", where the date and time are that of your local time zone
    4 ) Use calc.exe (programmer mode) to convert to hex (QWORD) - Enter the output from DateToInteger8, which will be a decimal value, in the calculator in decimal mode, then switch modes to hex to see the hex value you need.
    5 ) @KEiGHT, in his local time zone got: 1CF842195DB5400
    6 ) You can validate that the value you have is correct by entering in the command prompt: w32tm /ntte 0x1CF842195DB5400
    7 ) @KEiGHT, in his local time zone got: 151004 20:30:00.0000000 - 6/9/2014 10:30:00 PM
    8 ) Zero pad the value from the calculator to get 16 digits: 01CF842195DB5400
    9 ) The leftmost 8 digits will be the highpart (01CF8421) and the rightmost 8 digits will be the lowpart (95DB5400).

    I'm not sure if the date displayed in the OS version selection window is that of your local time zone or GMT, so you might have to adjust the values you enter above slightly, but since the output from w32tm includes GMT you should be able to figure out what you need to change.
     
    So you found the .xml file where you need to enter this revised value?  Where is it?
     
    Cheers and Regards
  18. Like
    abbodi1406 reacted to nonspin in Windows Installation - Where I can change the modification date   
    Highpart/Lowpart explanation:
     
    Highpart: Date
    Lowpart: Time
     
    convert/verify: w32tm
    example:
    <CREATIONTIME><HIGHPART>0x01CB88D1</HIGHPART><LOWPART>0xDB7CCA61</LOWPART></CREATIONTIME>syntax: w32tm /ntte 0xHIGHPARTLOWPART
     
    Open DOS-Box: (Win+R) CMD
    w32tm /ntte 0x01CB88D1DB7CCA61
    149707 16:42:02.2122081 - 11/20/2010 6:42:02 PM
  19. Like
    abbodi1406 got a reaction from Legolash2o in Differences between cab and express cab files   
    express cab contains only the update manifest files + xml file.. those are used by WU to identify the original package contents and to determine what components of it are needed for the system so it download them only
     
    i.e.
    if the update are multilingual, it will download only lang resources matching your system
     
    only WU knows how to handle this mechanism
    so, express cab are useless and cannot be used for integration
  20. Like
    abbodi1406 reacted to bphlpt in HELP: Couple of integration questions   
    Read the entire thread.  Yes he was trying to use all possible updates, but he did quite a bit of analysis to determine which lists are the most complete and up to date and without duplicates.
     
    What is your intention?  Just to satisfy Windows Update or get all available updates?  And are you building an install source just for your personal home use or are you making an install source for business use or what?
     
     
    1. Yes there are that many updates available if you include the request only updates.
    1a.  I haven't checked all of the various lists, but reasons can include:
     
    * some lists might, or might not, include updates that are obsolete
    * some lists might not be up to date
    * some lists might, or might not, include request only updates
    * some lists might, or might not, include updates that cannot be applied on an offline image
    * some lists might, or might not, include updates that only apply to optional features

    2&3. Windows Update does not, and cannot, download request only updates, even though the request only updates ARE "real" updates, they just might, or might not, officially apply to you at this time.
     
    Request only updates are updates, or hotfixes, that have been developed by MS to deal with specific problems and generally they have not been tested quite as extensively on as wide a variety of systems as the "regular" updates that are pushed out by Windows Update, so there is a very small possibility that they might cause an issue on your system.  But that risk is extremely small and I know of no one personally that has ever had an issue if they installed those request only updates.  But even regular updates have caused issues in the past so it is possible.  Back when MS used to put out Service Packs, such as SP1, ALL updates issued prior to that time would be included in the SP, both regular and request only, so many folks, including me, just figured they might as well go ahead and install the request only updates when they became available, even if they did not apply to them at that time, "just in case".  Others just wanted Windows Update to say they were up to date, and they thought "unnecessary" updates just added bloat and applied to issues that they were unlikely to have, so decided not to install them.  It's up to you to decide what you want.  If you decide that you do not want any of the request only updates, then you might find this thread useful - http://www.wincert.net/forum/topic/10811-15-mars-2014-updates-packs-gdr-windows-7-sp1/ - but I have not checked lately to see if all links are still valid or if it is up to date.  You'll probably need to at least read the first page and the last couple of pages in the thread using a translation program such as Google Translate to know for sure what is going on.
     
    As a general rule, you will be better off if you decide whether you want Request only updates or not, pick ONE list that seems to be kept up the best and meets your needs, and just use that one list.  Then pick up the few, if any missing updates after you have installed your system using Windows Update.
     
    Good luck!
     
    Cheers and Regards
  21. Like
    abbodi1406 reacted to ricktendo in Microsoft .NET Framework 4.8 for Windows 7   
    On Winows 7 C: is always the OS partition, this never changes
  22. Like
    abbodi1406 reacted to sweden8 in Microsoft .NET Framework 4.8 for Windows 7   
    @abbodi1406 - No problem, I value your .NEt pack and gladly wait :thumbsup_anim:
  23. Like
    abbodi1406 got a reaction from tommis15 in Slipstreaming Help!   
    From Additional, integrate these:
    PlatformPlatform UpdatesIE11 CABsIE11 UpdatesWindowsMediaCenterWinHelpWUClientonly IE11 is enough and needed to be integrated
     
    from Extra, generally you don't need any unless you know what they are for
  24. Like
    abbodi1406 reacted to Shandra in Is it possible to integrate SP1 into Windows 7 with Wintoolkit?   
    And keep in mind, that the OEM key from the sticker may be a "one-time only" key - as in using it, the activation will be bound to the hardware it is used on (I am mostly using SystemBuilder Variants(*1) for my system (as I build 'em myself or buy 'em without OS) and there thats not a problem (in short: I simply lack the Win7 OEM experience)), but as far as my knowledge has grown on the subject a vital change in hardware may or may not be activatable via phone or strictly license termin speaking may simply be rejected - so I see a reason to the "why someone will stick to autoactivation as long as possible", because then the OEM key could def. be used on changed hardware (if it is the first time this key is used - so why waste it on the OEM Hardware where its not needed) with just using the online activation. I am really not sure on this one, the MS specific sides (technet, etc.) are AFAIK strict on this one-time bound between key and hardware, other sides claim that an activation via phone is still possible.
     
    P.S.: with Win8 this whole OEM/Preactivation Discussion is Void - the new scheme where the "to be activated" key for OEM Systems is kept in the BIOS is a total different matter
     
    *1: Ok, from a German Point of view and an old Sentence about the resale of OEM licenses, MS SB variants where (AFAIK) the result of that verdict (as a different model to pure OEM license (like from Dell or such);  SB (OEM) license is nowadays what is nearly 100% of the time sold to the customer here in germany (and I know only a few (real minority) shops who are actually offering the real retail)... And I am not sure what that means for reactivation on different hardware or such, but according to magazines like the C't (not talking Win8+ here) SB licenses under our law should be reactivatable under new hardware (but that may well be just an urban legend).
  25. Like
    abbodi1406 reacted to Shandra in Is it possible to integrate SP1 into Windows 7 with Wintoolkit?   
    In addition, and as a final remark on my behalf (it is time to get back to my real studies, though it was fun and reminded me to the time of 2005 where I was one of the minorities who bought xp x64 and where often forced to get used to modify .msi's with Orca) - I tried it again with the (official technet) sysprep way... the reason why WinToolkit recognized my first preped image as being corrupt was that I have chosen a custom name for the image.... still now, and after I've named it right, and though simply building a .iso via WT from the syspreped .wim worked like a charm (the get-package information afterwards was the same as for a real sp1 install-media), it failed when I tried to integrate IE11 and its prerequisites. That doesn't worked out well - WT integrated fine, the install resulted in failures which may well be searched in this forum for the early times of IE11 and its integration. So i am not sure if I missed some KB or if it ain't be possible to use WT on a syspreped .wim (which makes no sense IMHO, so my guess would still be a fault in my procedures - and that one may include that I where using a WinPE.iso handed over to the VM that where build with the current ADK release for Win8+; I used that because it is much easier to apply the dism commands (/capture-image) to build the .wim then using the old variant with imageX). 
     
    As said, I still think that it is possible (else all technet sysprep how to build an oem/multilingual media, how to deploy sp1, etc. descriptions wouldn't make sense; At least for the sysprep way).  In the meantime where the vm(s) where occupied with their install I checked the MD5 sums of the KB976902 files with their corresponding parts of KB976932 (SP1) and there where no differences to be found (haven't checked all of the files), so it should - in theory be possible - to get along that way to a working (and future proof) image... But as the OPs question (OEM based Win 7) and my curiosity about Dreamsparks PreSP1 Server 2008 R2 .img are just a minority in cases that may be neglected in the development of WT (or the Foolproof assignments/modules therein (which in my experiences make up 3/4 the time in the development of a GUI based project)) I just give up with trying any further (and will continue with my real work/study again    ). 
×
×
  • Create New...