A1: You have to list the Feature name and find its package in registry hive SOFTWARE. A2: I can't. It is removed from system structure and made as an Fod package, then difined\controlled in\by FodMetadata. e.g. Microsoft-Windows-Telnet-Client-FOD-Package.
Q1.1: Does it possible to have a specific example with all the details? Q1.2: Could a custom feature be added by this way to a customized image ? Q2.1: Could such PoD packages be created with FodMetadata, files etc, to match a removed feature from the system structure ?
Neat. Would you happen to have a .mum replacement guide laying around? I tried to make a hidden feature visible for removal but the .mum failed integrity checks. It did, however, let me remove the feature. It looks like the main or even only edit to your LCU files was adding more assembly names to update.mum but I'm not sure. I'd like to understand the of the art of update creation so that corruption is unlikely and a GN edition doesn't go without updates. Are the edition-specific packs simply altered packs that are available?
When you modify mums, especially when adding content, you need to ensure that their corresponding components exist. If they do not exist, you need to create them. Many times, you need to modify them layer by layer, all the way to the manifests, and even the components themselves. As of now, I do not have a replacement guide for mum because the structure is too complex and writing it as a script can result in poor performance. For example, to determine whether the Microsoft-Windows-Client-Required-Package for 20348 needs to be updated, it is necessary to determine whether its sub packages and sub manifests have been updated. To do so, I need to traverse all possible sub component updates, which will nest many layers of loops in the script. I will write it as a program to improve performance. For signature verification failure, if it is offline, generate a cat and sign to solve it. If it is online, it is necessary to patch the Servicing Stack. In this regard, gailium119 has already been implemented. I didn't understand the last question. Are you referring to modifying the LCU?
Then I guess you can send it today, my old laptop features are bad, I will install it to it, this is my purpose.
Manual test1 of reconstructed 10240.16384 + CU + Resetbase offline Code: C:\WINDOWS\system32>dism /English /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.16384 Current edition is: Current Edition : Starter The operation completed successfully. C:\WINDOWS\system32> Code: <InstallerQueue Length="0x00000001"> <Action Installer="{c145fd5d-1b9b-4738-9961-64034a3da28f}" Mode="uninstall" Phase="0x00000018" Family="Microsoft-Hyper-V-Guest-Integration-Drivers, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" Old="10.0.10240.16384"/> </InstallerQueue> Manual test2 of reconstructed 10240.16384 + CU + Resetbase offline Code: C:\WINDOWS\system32>dism /english /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.16384 Current edition is: Current Edition : Starter The operation completed successfully. C:\WINDOWS\system32> Code: <InstallerQueue Length="0x00000001"> <Action Installer="{c145fd5d-1b9b-4738-9961-64034a3da28f}" Mode="uninstall" Phase="0x00000018" Family="Microsoft-Hyper-V-Guest-Integration-Drivers, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" Old="10.0.10240.16384"/> </InstallerQueue>
Well that should give me some food for thought for now. Having a pain of a time getting a stripped-down iso that will take consecutive LCUs. Seems like no one is sure when is best to remove what. And I'm not sure what a "source" is because I feed DISM all kinds of sources and it tells me it can't find what it needs. I'll figure it out, though. Perhaps some neural net program could be implemented for package creation to much success. Of course the initial legwork would be tough and it may be worth millions to enterprise so I probably wouldn't see it here. I imagine an AI that understands Windows servicing and could create and sign packages to essentially create brand new editions, or discover and build the packages of any other. On the last question. I was just wondering how much editing goes in to a custom LCU, or really any update. I briefly looked over the last-modified dates but couldn't be sure what all was necessary. Your reply sounds like much more than the update.mum. No pressure to describe it all if it's long, I'd totally understand and I'm too new to this to traverse much.
Your Starter does not have that package which is inherited from EnterpriseS. Use another way for a clean Starter. And it does not matter with that package, because EnterpriseS has it too, no problem. So, it's another problem due to problematic 10240.16384 reconstruction. PS: "Your Starter" does not necessarily mean "in Official Starter structure". Manual test3 of reconstructed 10240.16384 + CU + Resetbase offline (based on aforementioned) Code: C:\WINDOWS\system32>dism /english /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.16384 Current edition is: Current Edition : Starter The operation completed successfully. C:\WINDOWS\system32> Code: C:\WINDOWS\system32>dism /english /image:K: /add-package:z:\Windows10.0-KB5035966-x64.cab Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.16384 Processing 1 of 1 - Adding package Package_for_KB5035966~31bf3856ad364e35~amd64~~10240.20520.1.0 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /english /image:K: /add-package:z:\1\Windows10.0-KB5035858-x64 Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.16384 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~10240.20526.1.5 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32> Code: C:\WINDOWS\system32>dism /english /image:K: /Cleanup-Image /startcomponentcleanup /resetbase Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.20520 Error: 0x800f0806 The operation could not be completed due to pending operations. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> There is not Pending.xml. It still shows pending error. [Double-Check] Code: C:\WINDOWS\system32>dir /b K:\Windows\WinSxS\*.xml migration.xml C:\WINDOWS\system32> Code: C:\WINDOWS\system32>dism /english /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.16384 Current edition is: Current Edition : Starter The operation completed successfully. C:\WINDOWS\system32> Code: C:\WINDOWS\system32>dism /english /image:K: /Cleanup-Image /startcomponentcleanup /resetbase Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.20520 Error: 0x800f0806 The operation could not be completed due to pending operations. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> Now the only way is to renew the script for a clean image.
Manual test4 of reconstructed 10240.16384 + CU + Resetbase offline (with clean image created in new way) Code: C:\WINDOWS\system32>dism /english /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.16384 Current edition is: Current Edition : Starter The operation completed successfully. C:\WINDOWS\system32> Code: C:\WINDOWS\system32>dism /english /image:K: /add-package:z:\Windows10.0-KB5035966-x64.cab Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.16384 Processing 1 of 1 - Adding package Package_for_KB5035966~31bf3856ad364e35~amd64~~10240.20520.1.0 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /english /image:K: /add-package:z:\1\Windows10.0-KB5035858-x64 Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10240.16384 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~10240.20526.1.5 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32> Code: <InstallerQueue Length="0x00000012"> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-TCPIP, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-NETBIOS, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-RasServer, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-RasBase, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-TCPIP6Helper, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-NetworkBridge, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-NetworkTopology-Inf, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-Tunnel, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-LinkLayerDiscoveryProtocol, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-NDIS-PacketCapture-Drivers, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-Ndis-IMPlatform, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-NDISUIO-NetcfgGC, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-Native-80211-NetCfg, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Hyper-V-Guest-Integration-Drivers, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-WorkstationService-NetcfgGC, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-SMBServer-NetcfgGC, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-Network-Security-NetcfgGC, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-Network-QoS-NetCfg, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> </InstallerQueue> Wait. All is New 10240.16384 to be installed online. This is new problem. This is in "official" structure. Let me test in "custom" structure. Code: <InstallerQueue Length="0x00000011"> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-TCPIP, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-NETBIOS, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-RasServer, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-RasBase, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-TCPIP6Helper, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-NetworkBridge, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-NetworkTopology-Inf, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-Tunnel, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-LinkLayerDiscoveryProtocol, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-NDIS-PacketCapture-Drivers, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-Ndis-IMPlatform, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-WorkstationService-NetcfgGC, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-Network-Security-NetcfgGC, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-Native-80211-NetCfg, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-NDISUIO-NetcfgGC, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-SMBServer-NetcfgGC, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> <Action Installer="{81a34a10-4256-436a-89d6-794b97ca407c}" Mode="install" Phase="0x00000026" Family="Microsoft-Windows-Network-QoS-NetCfg, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.10240.16384"/> </InstallerQueue>
Simplify the LCU like the system itself. If any package you modify is updated, it needs to be modified again. Adding is more complex than simplifying.