Integrate7 script – automatically slipstream updates and drivers up to 11/2023!

Discussion in 'Windows 7' started by Deleted member 190847, Jan 1, 2019.

    ngen has nothing to Integrate7, it just forces .NET Framework to compile its libraries for your CPU.
    If you don't run it, the system will do it automatically. But it will do it via background service thus slowing your PC until it ends.
    By running ngen, you just speed up the above process. Nothing less nothing more.

    ngen executeQueuedItems should be run after initial installation and after every update for .NET Framework (eg. after Windows Update updates are installed).
     
  1. ZaForD

    ZaForD MDL Expert

    Jan 26, 2008
    1,212
    200
    60
    @ wkeller,
    I made a 32bit version of Integrate7 for an old Netbook.
    With 'Starter' I had no IE icon on the taskbar, but killed the install straight away (too limiting)
    In Home Premium I had an IE11 icon on the taskbar, but IE11 kept trying to go to an MS site which I couldn't stop ?
    In Professional I had IE8 with an icon on the taskbar and it functioned fine.
    I'm assuming something went wrong with the IE updates/hotfixes, I'll re-download them and create a new ISO.

    I looked through the cmd file and saw settings for IE so I know its not removed.
    Should there be an IE icon on the taskbar ?
    And if I replace the Google references to DuckDuckGo in the IE section, will it mess up the script ?

    Thanks
     
  2. I used mainly Professional and Ultimate versions on all my PCs, and on both versions IE11 is working fine.
    On first, second or third run, IE11 will ask you to choose default startpage and search engine. It is normal and hardcoded by Microsoft.
    You can choose either your current settings (Google search and blank start page, in case of my script) or Microsoft's default settings.

    Yes, it should be. IE11 is integrated properly.

    No, it is unimportant which search engine you will set up.
     
  3. schubidubi

    schubidubi MDL Junior Member

    Nov 9, 2022
    78
    80
    0
    #664 schubidubi, Feb 22, 2023
    Last edited: Feb 22, 2023
    Hello @wkeller,

    do you consider to Update "Integrate7", with the "Server 2008"/"Embedded 7" ESU Updates? If not, are you willing to help me to integrate these, with your Tool?

    1. I think its needed to change the ESU variables in the script? But how?
    Code:
    REM Set ESU variables
    set "EsuCom=amd64_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_6.1.7603.25000_none_caceb5163345f228"
    set "EsuIdn=4D6963726F736F66742D57696E646F77732D534C432D436F6D706F6E656E742D457874656E64656453656375726974795570646174657341492C2043756C747572653D6E65757472616C2C2056657273696F6E3D362E312E373630332E32353030302C205075626C69634B6579546F6B656E3D333162663338353661643336346533352C2050726F636573736F724172636869746563747572653D616D6436342C2076657273696F6E53636F70653D4E6F6E537853"
    set "EsuHsh=45D0AE442FD92CE32EE1DDC38EA3B875EAD9A53D6A17155A10FA9D9E16BEDEB2"
    set "EsuFnd=windowsfoundation_31bf3856ad364e35_6.1.7601.17514_615fdfe2a739474c"
    set "EsuKey=amd64_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_none_0e8b36cfce2fb332"
    if "%ImageArchitecture%"=="x86" (
     set "EsuCom=x86_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_6.1.7603.25000_none_6eb019927ae880f2"
     set "EsuIdn=4D6963726F736F66742D57696E646F77732D534C432D436F6D706F6E656E742D457874656E64656453656375726974795570646174657341492C2043756C747572653D6E65757472616C2C2056657273696F6E3D362E312E373630332E32353030302C205075626C69634B6579546F6B656E3D333162663338353661643336346533352C2050726F636573736F724172636869746563747572653D7838362C2076657273696F6E53636F70653D4E6F6E537853"
     set "EsuHsh=343B7E8DE2FE932E2FA1DB0CDFE69BB648BEE8E834B41728F1C83A12C1766ECB"
     set "EsuFnd=windowsfoundation_31bf3856ad364e35_6.1.7601.17514_0541445eeedbd616"
     set "EsuKey=x86_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_none_b26c9b4c15d241fc"
    )
    2. Should i simply replace KB5022338 - Jan23 Cumulative from your script, with the KB5022872 Feb23 Cumulative for Embedded 7?
    Code:
    "%~dp0tools\%HostArchitecture%\DISM\dism.exe" /Add-Package /Image:"%~dp0mount\%%i" /PackagePath:"%~dp0hotfixes\windows6.1-kb5022338-%ImageArchitecture%.msu"
    
    3. Also, the .Net 4.8 Updates, would the following work? I added the two after line 465 and after line 487, in your "Integrate7"
    Code:
    copy /b /y "%~dp0hotfixes\ndp48-kb5020879-%ImageArchitecture%.exe" "%~dp0DVD\Updates" >nul 2>&1
    copy /b /y "%~dp0hotfixes\ndp48-kb5022509-%ImageArchitecture%.exe" "%~dp0DVD\Updates" >nul 2>&1
    copy /b /y "%~dp0hotfixes\ndp48-kb5023823-%ImageArchitecture%.exe" "%~dp0DVD\Updates" >nul 2>&1
    Code:
     echo start /w "" "%%CDROM%%\Updates\ndp48-kb5020879-%ImageArchitecture%.exe" /q /norestart>>"%~dp0DVD\sources\$oem$\$$\Setup\Scripts\SetupComplete.cmd"
     echo start /w "" "%%CDROM%%\Updates\ndp48-kb5022509-%ImageArchitecture%.exe" /q /norestart>>"%~dp0DVD\sources\$oem$\$$\Setup\Scripts\SetupComplete.cmd"
     echo start /w "" "%%CDROM%%\Updates\ndp48-kb5023823-%ImageArchitecture%.exe" /q /norestart>>"%~dp0DVD\sources\$oem$\$$\Setup\Scripts\SetupComplete.cmd"
    

    I really love your Scripts/Tools, more then any of the other scripts i found on MDL...

    It would be nice to keep Windows 7 updatet and deployable (on Home Machines from friends, family and myself) for as long as possible, cause some have really old Hardware, where Windows 7 is the better option...,imo!


    Greetings... :cool:
     
  4. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    16,141
    84,318
    340
    You don't need to change the ESU variables

    ndp48-kb5020879 is not needed anymore
     
  5. schubidubi

    schubidubi MDL Junior Member

    Nov 9, 2022
    78
    80
    0
    #666 schubidubi, Feb 23, 2023
    Last edited: Feb 23, 2023
    Ty, abbodi1406! Nice, that a Legend like you, come to help a noob like me.:sun:

    But are you sure about that? This is the ESU part from the Integrate7 script...
    Code:
    REM Set ESU variables
    set "EsuCom=amd64_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_6.1.7603.25000_none_caceb5163345f228"
    set "EsuIdn=4D6963726F736F66742D57696E646F77732D534C432D436F6D706F6E656E742D457874656E64656453656375726974795570646174657341492C2043756C747572653D6E65757472616C2C2056657273696F6E3D362E312E373630332E32353030302C205075626C69634B6579546F6B656E3D333162663338353661643336346533352C2050726F636573736F724172636869746563747572653D616D6436342C2076657273696F6E53636F70653D4E6F6E537853"
    set "EsuHsh=45D0AE442FD92CE32EE1DDC38EA3B875EAD9A53D6A17155A10FA9D9E16BEDEB2"
    set "EsuFnd=windowsfoundation_31bf3856ad364e35_6.1.7601.17514_615fdfe2a739474c"
    set "EsuKey=amd64_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_none_0e8b36cfce2fb332"
    if "%ImageArchitecture%"=="x86" (
     set "EsuCom=x86_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_6.1.7603.25000_none_6eb019927ae880f2"
     set "EsuIdn=4D6963726F736F66742D57696E646F77732D534C432D436F6D706F6E656E742D457874656E64656453656375726974795570646174657341492C2043756C747572653D6E65757472616C2C2056657273696F6E3D362E312E373630332E32353030302C205075626C69634B6579546F6B656E3D333162663338353661643336346533352C2050726F636573736F724172636869746563747572653D7838362C2076657273696F6E53636F70653D4E6F6E537853"
     set "EsuHsh=343B7E8DE2FE932E2FA1DB0CDFE69BB648BEE8E834B41728F1C83A12C1766ECB"
     set "EsuFnd=windowsfoundation_31bf3856ad364e35_6.1.7601.17514_0541445eeedbd616"
     set "EsuKey=x86_microsoft-windows-s..edsecurityupdatesai_31bf3856ad364e35_none_b26c9b4c15d241fc"
    )
    and this from your new v12 ESU bypass
    Code:
    set "xOS=x64"
    set "xBT=amd64"
    set "xBE=bbe64.exe"
    set "xSL=sle64.dll"
    set "xMS=msiesu64.dll"
    set "_EsuKey=%_SxS%\Winners\amd64_microsoft-windows-s..edsecurityupdatesai_%_Pkt%_none_0e8b36cfce2fb332"
    set "_EsuCom=%_EsuX64%"
    set "_EsuIdn=4D6963726F736F66742D57696E646F77732D534C432D436F6D706F6E656E742D457874656E64656453656375726974795570646174657341492C2043756C747572653D6E65757472616C2C2056657273696F6E3D362E332E393630332E33303630302C205075626C69634B6579546F6B656E3D333162663338353661643336346533352C2050726F636573736F724172636869746563747572653D616D6436342C2076657273696F6E53636F70653D4E6F6E537853"
    set "_EsuHsh=193767A6217F337F400E81A2F26A4A5C22A4E3C33FD605EB1EEE38EF861E0FAC"
    ) else (
    set "xOS=x86"
    set "xBT=x86"
    set "xBE=bbe32.exe"
    set "xSL=sle32.dll"
    set "xMS=msiesu32.dll"
    set "_EsuKey=%_SxS%\Winners\x86_microsoft-windows-s..edsecurityupdatesai_%_Pkt%_none_b26c9b4c15d241fc"
    set "_EsuCom=%_EsuX86%"
    set "_EsuIdn=4D6963726F736F66742D57696E646F77732D534C432D436F6D706F6E656E742D457874656E64656453656375726974795570646174657341492C2043756C747572653D6E65757472616C2C2056657273696F6E3D362E332E393630332E33303630302C205075626C69634B6579546F6B656E3D333162663338353661643336346533352C2050726F636573736F724172636869746563747572653D7838362C2076657273696F6E53636F70653D4E6F6E537853"
    set "_EsuHsh=1502A9353C37FF55B0AD972704B8DEC738616966A57AC716B89C38C595A79B61"
    I wonder, cause they are different...?

    Edit: And your new v12 msiesu**.dlls, have other hashes and are much bigger then the actually included ones!
     
  6. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    16,141
    84,318
    340
    both v11 (6.1.7603.25000) and v12 works

    yeah, you need to update those, but i don't know which variant Integrate7 use exactly
    because registry will be different
     
  7. schubidubi

    schubidubi MDL Junior Member

    Nov 9, 2022
    78
    80
    0
  8. ZaForD

    ZaForD MDL Expert

    Jan 26, 2008
    1,212
    200
    60
    @ wkeller, thanks for replying mate ;)
    I think I've found what was causing my problems, I'll list them here in case someone else is having problems too.

    1. I used the script to 'pre-download' all the hotfixes, but it seems to stall towards the end. I thought it had finished, so I probably had a few hotfixes missing. :oops:
    Leaving the script running until the click to close message appears, fixes that problem.
    2. A couple of the Hotfixes were failing. Something about the unattended.xml being to large :confused:
    Cleaning out the Bin, Temp folders and Rebooting seemed to fix that one.

    Only problem now is find some settings to let Windows7 install on a UEFI setup in Qemu.
    But thats probably for another forum :D
     
  9. dudeluv

    dudeluv MDL Senior Member

    Aug 7, 2012
    328
    105
    10
    @schubidubi
    Yes made myself an updated ISO following your changes and installed on my HP8200 sff and all went well.
     
  10. E Fudd

    E Fudd MDL Novice

    Jan 20, 2023
    9
    3
    0
  11. 7theaven

    7theaven MDL Novice

    Aug 16, 2017
    17
    8
    0
    Hi all. Just started work on installing wkeller's W10 project (thanks again, WK) but I'm also very interested in an improved W7, so I'll make a start on this one, too. Only got as far as the first page of this thread but I have a question about the Daz loader. I've used that loader with W7 installs for many years and it's always worked fine on older machines with a standard old type BIOS, ie, not UEFI. But the first time I did a W7 build on a UEFI machine, I learned that the Daz loader doesn't work in that framework. Is that still the case?
     
  12. #673 Deleted member 190847, Mar 5, 2023
    Last edited by a moderator: Mar 5, 2023
    (OP)
    DAZ Loader could work on UEFI if your BIOS already has SLIC 2.1 table included. If it doesn't, DAZ will be unusable for you.
    So you will have these options when DAZ fails.

    Yes, but these updates are already included, so broken links have no impact on anything.
     
  13. schubidubi

    schubidubi MDL Junior Member

    Nov 9, 2022
    78
    80
    0
  14. dudeluv

    dudeluv MDL Senior Member

    Aug 7, 2012
    328
    105
    10
  15. #677 Deleted member 190847, Mar 6, 2023
    Last edited by a moderator: Mar 6, 2023
    (OP)
    Currently I didn't have enough free time to make updates/improvements, so I have posted this solution to at least install updates manually.
    Integrate7 v4.01 is mature now, but it (of course) could be done better like almost everything.
     
  16. schubidubi

    schubidubi MDL Junior Member

    Nov 9, 2022
    78
    80
    0


    Maybe you could only tell me, what i have to change to make your script compatible with BypassESU v12?
    (Edit: I would help to update your script, with future updates, when you don't have time)

    When its to complicated or it takes to much time for rewriting the script, to make it compatible with BypassESU v12, then I accept it and look for another solution to integrate the future Updates for Embedded7! :cool:

    Yeah, and again thx for your nice Tools! :)

    Greetings... :p
     
  17. Ok, I will release a new version within days. Not just with BypassESU v12, but also with some other tweaks (some backported from Slimdown10).
     
  18. CaptainSpeleo

    CaptainSpeleo MDL Addicted

    May 24, 2020
    819
    488
    30
    wkeller:
    If I understand you correctly, you plan to release a new version of Integrate7 after March 14th "patch Tuesday"?