Hello our master for what I have observed you definitely abandoned the evolution of the toolkit for W8.1 systems at least is that what interests me in this way seems to be the same thing that M$FT is doing and forcing everyone to use some version of Windows 10 I will be wrong ? please wait for something thank you boss thanks
The issue is with Pre-Superfetch.reg, below is the correct value for setting the Prefetch or Superfetch. Code: ; Disable Windows Prefetch and Super Prefetch [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\Memory Management\PrefetchParameters] "EnablePrefetcher"=dword:00000000 "EnableSuperfetch"=dword:00000000
Other than component removal, Am I not updating the Toolkit's other features and packs to support Windows 7 or 8.1? Also did added the support for removal components using list method with template files. If I had enough time and good health, would have been added the support for removing the Windows 7 or 8.1 components using ToolKitHelper method.
Hello @MSMG For more details about integrating by order: Servicing Stack Update - Windows10.0-KB4598481-x64.msu - SHA1: 749FE79FD2E31B145DE37C2F9EBF4F711D174DC2 Adobe Flash Player Removal - Windows10.0-KB4577586-x64.msu - SHA1: C9BB49DF325C20DDC147137B3F769FA44D800DDE Dynamic Update - Windows10.0-KB4586858-x64.cab - SHA1: 31934446993448F36FC46340F1F0D88BC079A0C6 .NET Cumulative - Windows10.0-KB4586876-x64-NDP48.msu -SHA1: AB1407801539DFE4AF2423400875A596FC032739 Windows Experience Feature Pack - Windows10.0-KB4592784-x64.cab - SHA1: 2235AB500866AEABBFE59E96ECCD908263934180 Cumulative Update (RollupFix) - Windows10.0-KB4598242-x64.msu - SHA1: 725AEED030BC68B2D07096503BD26918AC1FE488 Definition Updates for Windows Defender - defender-update-kit-x64.zip - SHA1: 14482F5F3B254662D480B655D60FCA157C0D5544 Enablement Package - Windows10.0-KB4562830-x64.msu - SHA1: 93A5C65488AFFB6E73A0A48AD6A58D8BC1713FD7 Then after that integrating .Net Framework 3.5 (NetFx35) It's correct or not? If not correct please, explain to us.
I use W10UI_9 for updates integration, it integrates in specific order, depending on the used settings.
The bug happened when I use : "Integrate Open Secure Shell (SSH) Client & Server" in windows 10 LTSC 1809. After I installed the system (via setup.exe) I check "Add a feature" there's The OpenSSH Server shows "not installed". So does it have the same result as this command? Get-WindowsCapability -Online | ? Name -like 'OpenSSH*'
In next version the Toolkit will integrate the updates in the order required by the ToolKitHelper.exe. Yes the order is correct, it's just the .NETFX35 and Enablement you need to add after the CU so that the CU won't write the extra pending.xml data. Yes doing so will make the WU re-offer the CU but you can overcome this by again re-integrating the CU after doing the above step, this will not write the extra pending.xml data. The current steps specified in the readme.txt is same as the above only change is the enablement package now will be added after the CU.