I have not tested whether installing updates on a live system breaks Edge functionality. Has this happened to you? In MSMG script there is nothing special in integrating updates part so integrating using W10UI should produce the same result as integrating using MSMG Toolkit.
Yeah, LTSB with Edge (integrated through MSMG Toolkit) gets updated without problems when the image is mounted offline and the toolkit performs the update. Once OS is installed, Edge functions without problems until a new CU is released. Updating either via Windows Update or through cab installation results in OS simply ignoring Edge. Everything get's updated, except for Edge, which causes version mismatch and Edge cannot be used past that point. I think this happens only if MS actually includes updates to Edge that change it's version. If CU does not update and/or alter Edge version on any OS (Home, Pro, Enterprise non-LTSB), then such an update would not break Edge on LTSB. Otherwise it would. I also recall seeing MSMG Toolkit LOG that did display an error either during Edge integration into LTSB or during the update process. Mabe that was that registry thing...
It's hard to happen that a cumulative update does not update the Edge. Usually every month has security patches for browsers (IE and Edge). Here are the posts of xinso about the registry fix: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-44#post-1300728 https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-46#post-1301912 EDIT: Have you somehow managed to get the Edge working after installing a CU on a live system? Older versions of the MSMG Toolkit do not have the fix to enable the full resetbase while W10UI has (not by default) that would be the most significant difference between the 2.
New Updates Installers W10UI 4.2 - few improvements and fixes - detailed documentation for options in ReadMe.txt - added workaround for resetting 16299 WinPE images (they have the same restriction as OS image) - added option to update or skip winre.wim (if detected within install.wim) - oscdimg.exe will be detected automatically if Windows 10 ADK is installed - iso name will have the cumulative update version, and today's date (e.g. Win10_16299.214_2018-02-10.iso) WHD-Windows8.1-Updates-Installer 4.0 - reworked and improved the script to provide similar features as W10UI - support for different targets (online os, offline mount directory, wim file, iso distribution) - continous messeges in cmd window - process online updates for offline targets (if possible) - add block tweaks related to diagtrack (telemetry service) when installing Monthly Rollup - oscdimg.exe will be detected automatically if Windows 8.1 ADK is installed - iso name will have the monthly rollup version, and today's date (e.g. Win8.1_9600.18909_2018-02-10.iso) Spoiler: Remarks # for offline integration, if "Block Windows10/Telemetry" option is active, a simple script will be created on desktop RunOnce_W10_Telemetry_Tasks.cmd after installing the OS, you need to run it as administrator, it will be self-deleted afterwards # WinPE images (boot.wim/winre.wim) will be updated only with: - servicing stack update - baseline updates - Monthly Quality Rollup - extra few WinPE updates WHD-Windows7-Updates-Installer 4.0 - reworked and improved the script to provide similar features as W10UI - support for different targets (online os, offline mount directory, wim file, iso distribution) - continous messeges in cmd window - workaround to safely integrate servicing stack update KB3177467 for offline targets - process online updates for offline targets (if possible) - add block tweaks related to diagtrack (telemetry service) when installing Monthly Rollup - oscdimg.exe will be detected automatically if Windows 8.1 ADK is installed - iso name will have the monthly rollup version, and today's date (e.g. Win7_7601.24023_2018-02-10.iso) - to rebuild wim files, you need either imagex.exe or install Windows 8.1 ADK Spoiler: Remarks # for offline integration, if "Block Windows10/Telemetry" option is active, a simple script will be created on desktop: RunOnce_W10_Telemetry_Tasks.cmd after installing the OS, you need to run it as administrator, it will be self-deleted afterwards # for offline integration, to process x64 update KB2603229 correctly, a simple script will be created on desktop: RunOnce_KB2603229_Fix.cmd after installing the OS, you need to run it as administrator, it will be self-deleted afterwards # for offline integration, to rebuild wim files, you need either of: - imagex.exe placed next to WHD-W7UI.cmd - Windows 8.1 ADK is installed - Host OS is Windows 8.1 # WinPE images (boot.wim/winre.wim) will be updated only with: - servicing stack update - Monthly Quality Rollup currently, the release include only the main script (with Convenience Rollup update KB3125574) WHD-W7UI_WithoutKB3125574.cmd require extra hard work to update, will try to done it ASAP.
WinRE.wim copy was left in the same folder as the updates... is that normal? Hopefully it was just a copy and the updated one was placed back into install.wim...
Scroll down to bottom: Code: ============================================================ Running W10UI v4.2 ============================================================ ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/3: Windows10.0-KB4074588-x64_CU_248.cab 2/3: Windows10.0-KB4074595-x64_Flash.cab 3/3: Windows10.0-KB4087256-x64_SSU.cab ============================================================ Mounting install.wim - index 1/10 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.15 Processing 1 of 1 - Adding package Package_for_KB4087256~31bf3856ad364e35~amd64~~16299.245.1.0 [==========================100.0%==========================] The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.15 Processing 1 of 1 - Adding package Package_for_KB4074595~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.15 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17 [==========================100.0%==========================] The operation completed successfully. ============================================================ Cleaning up OS image ============================================================ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.248 [==========================100.0%==========================] The operation completed successfully. ============================================================ Adding .NET Framework 3.5 feature ============================================================ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.248 Enabling feature(s) [==========================100.0%==========================] The operation completed successfully. ============================================================ Reinstalling cumulative update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.248 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17 [==========================100.0%==========================] The operation completed successfully. ============================================================ Updating winre.wim ============================================================ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Mounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.15 Processing 1 of 1 - Adding package Package_for_KB4087256~31bf3856ad364e35~amd64~~16299.245.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.15 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~16299.248.1.17 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.248 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.248 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image File : I:\W10UI_4.X\winre.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.16299.15 Exporting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Adding updated winre.wim ============================================================ 1 file(s) copied. ============================================================ Unmounting install.wim - index 1/10 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image File : i:\W10UI_4.X\16299.15_Work_NL_x64\sources\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully.
There is one change regarding the Update scripts that i forgot to mention if the target is a distribution folder and the updated iso is created successfully, the target folder will removed this is just to avoid duplication, since you can always extract the new iso however, if you don't want this, search for this line in the script and delete it (it will be near the end) Code: if %errorlevel% equ 0 rmdir /s /q "%target%" >nul
On my runs it didn't leave it there, when all indices were done it was deleted. I always run the script on an extracted iso with iso creation set to 1. In the past this has been discussed and afaik @abbodi1406 modified the script to also delete it when it is run on install.wim only.
I always select install.wim for offline image directory, not the whole source folder because the script does not detect anything that way. Should I select the whole ISO folder?
Select the extracted iso folder, not the sources folder i.e. C:\ISO\sources\install.wim -> Target = C:\ISO
i have a question, sorry if it has already been discussed here : i have a win10 x64 iso that does not contain any update (i.e, 16299.0), and i want to integrate updates into the iso, should i download and integrate all the updates that were released all over last months ( sept, nov, dec, jan and feb) or integrating only the last updates of february (CU and flash => Windows10.0-KB4074588-x64 and Windows10.0-KB4087256-x64) will be enough ?
Thank you, i already know that but it does not really answer my question, integrating only these updates into win10 iso that does not contain any update will be enough ?
I remember one time you telling me that old win7 updates were necessary for system stability and security so why this only applies for win7 and not for win10 ?
Windows 10 Cumulative Updates are, as the name states, Cumulative, containing all previously released CU fixes. A CU will never superseed/replace a SSU or a flash update.
SSU = Yes Flash = i noticed the jan. 2018 flash update got offered when i already integrated the most current one (feb. 2018): https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-267#post-1411143