W10UI v5.7 - Normal 1809 cumulative update will be reinstalled (with .NET cumulative) after enabling .NET 3.5, to keep WU happy Spoiler BTW, i made another test after the above, enabled small feature, then checked WU, and LCU was offered and re-processed so unless you keep Windows features state as default, or configure the features before integrating updates, LCU be reoffered anyway
@abbodi1406 I noticed when using W10UI_5.7 to integrate the current CU / SS (2) and .net 4.7.2 into a en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483 (RTM) distribution that the Add-on SS kb4465659 was ONLY integrated into the install.wim but the Base SS kb4132216 was integrated into the install.wim / winre.wim / boot.wim index 1 / boot.wim index 2… The CU kbkb4471321 [CU .2665] was integrated into ALL the wims / indexes above… Seems odd to me that that the Add-on SS kb4465659 wasn’t integrated into ALL the wims / indexes above ??? No errors were reported… I saved the dism log and the dism log.bak files in case they are useful…
KB4132216 is the primary base but KB4465659 should have been integrated in all wims too investigating...
Found the cause when updating winpe images, W10UI check if update.mum contain reference to "WinPE" Packages but KB4465659's update.mum only reference KB4132216 as parent, the secondary applicability info is found in Package_for_KB4465659_GM*.mum workarounding...
W10UI v5.8 solved the issue with integrating (2) Servicing Stack updates into LTSB 2016... Thank You for everything you do for MDL...
Re-integration of the standard CU also working correctly: Code: ============================================================ Running W10UI v5.8 ============================================================ ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/4: Windows10.0-KB4470502-x86_DotnetFX_CU_Dec_11.cab 2/4: Windows10.0-KB4470788-x86_SSU_17763.164.cab 3/4: Windows10.0-KB4471331-x86_Flash_Dec_5.cab 4/4: Windows10.0-KB4471332-x86_CU_17763.194.1.5.cab ============================================================ Mounting install.wim - index 1/4 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image Version: 10.0.17763.1 Processing 1 of 1 - Adding package Package_for_KB4470788~31bf3856ad364e35~x86~~17763.164.1.1 [==========================100.0%==========================] The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image Version: 10.0.17763.1 Processing 1 of 2 - Adding package Package_for_KB4470502~31bf3856ad364e35~x86~~10.0.1.2273 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_KB4471331~31bf3856ad364e35~x86~~10.0.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image Version: 10.0.17763.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~x86~~17763.194.1.5 [==========================100.0%==========================] The operation completed successfully. ============================================================ Cleaning up OS image ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image Version: 10.0.17763.194 [==========================100.0%==========================] The operation completed successfully. ============================================================ Adding .NET Framework 3.5 feature ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image Version: 10.0.17763.194 Enabling feature(s) [==========================100.0%==========================] The operation completed successfully. ============================================================ Reinstalling cumulative update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image Version: 10.0.17763.194 Processing 1 of 2 - Adding package Package_for_KB4470502~31bf3856ad364e35~x86~~10.0.1.2273 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_RollupFix~31bf3856ad364e35~x86~~17763.194.1.5 [==========================100.0%==========================] The operation completed successfully.
Hi, I have a question: how to decrypt .cab windows update, and back to encrypt? I want to replace one .dll.
You mean CBS package (e.g. Windows10.0-KB4470788-x86.cab) or dynamic update (e.g. Windows10.0-KB4475321-x86.cab)? the first is Intra Package Delta, must use expand.exe to extract it it cannot be re-packaged to original state, only Microsoft have the utilities to create it besides, the update itself cannot be installed with changed files the second is regular cabinet archive, can be extracted with many utilities and there are few programs that can re-package it, cabarc, makecab, DXTool https://forums.mydigitallife.net/posts/1371124/
I mean KB4475321, which has digital signatures. I used this: https://forums.mydigitallife.net/threads/msmg-toolkit.50572/ Created an image, it is necessary to update the machines in the domain, from 1803 to 1809, is there a script for this?
W10UI Sorry, question. I made an upgraded iso file of w10 LTSC (new .195 version). After that i did a new clean install on C partition. Later i booted in macrium rescue usb and saw that strange new boot partition is on system disk . Named (X). Like this: W10 (C) System Reserved (F) total 500MB free 171 MB Boot (X) total size 503 MB Free 500MB Second question, does hibernation can interrupt process of making iso image with w10ui ? also, during process i saw at one point that was only at 60% but proceeded down with process, and up was written all the time that 60%. I tried install that iso, and it looks ok. HWinfo tells that is .195 version.....hope it's all ok Is this normal, what created it ? Can i delete that partition with some tool ?
That system partition wasn't there before install of new os, also in bootable iso where included w10ui tool...in root....maybe something went wrong during process of making that iso with tool. Yes, default system hibernation, or maybe hard disk sleep, not sure
Well, try to temporary disable hibernation i don't think hard disk can go into sleep, since that extracted updates are on the same partition/disk where iso created
Extra partition is there only when i boot from Macrium Reflect Rescue Usb. I can see it from macrium integrated winPE file explorer (after i click on browse pc for restore file). This morning i made a bootable usb WinPE from AOMEI Partition Assistant Standard Edition, and there is no strange boot (X) partition on my PC. So, it must be some strange system reading of Macrium, i think he reads itself two times like two partitions, sizes of that 2 partitions are not same but ok.... i think it's ok. Will see if during new OS installation will be that partition.