26100.1, for Reconstruction. 26100.1742, 26100.1 + 1742 Baseline CU. Then, each new msu CU includes both 1742 and its latest CU. Q: For the latest update, do we need the whole msu CU which includes both 1742 and the latest CU? A: No. We need only the latest CU of the msu CU.
Thanks. But I was talking about any build "greater" than 1742. Especially when "customization" is needed.
10166.0, official spp. Q: Compatible with 10240.16384? A: Reconstruction, OK. Q: The reconstructed 10240.16384, boot to Desktop or BSOD? A: OOBE ---> Desktop ---> Windows Update ---> 2019-05 CU ---> Restart ---> 2025-04 CU ---> Restart ---> Your device is up to date. ---> UBR 20979. Edit: It won't boot with updates integrated.
Spoiler: missing-brand couldnt get to brand but everything else is ok its pro edition but with server layout [packages - aka Server features...]
The reconstructed 10240.16384 has Windows\WinSxS\pending.xml. Q: The official image does not have it. How does Microsoft make it?
[About 14393.0 Hyper-V Server 2016] There are several updates. I found the followings are OK to fix them for Reconstruction. December 13, 2016 — KB3206632 (OS Build 14393.571) package_3785_for_kb3206632~31bf3856ad364e35~amd64~~10.0.1.8 for Microsoft-Windows-Security-SPP-Component-SKU-ServerHyperCore-Default-Package~31bf3856ad364e35~amd64~~10.0.14393.0 package_1035_for_kb3206632~31bf3856ad364e35~amd64~~10.0.1.8 package_3786_for_kb3206632~31bf3856ad364e35~amd64~~10.0.1.8 for Microsoft-Windows-Security-SPP-Component-SKU-ServerHyperCore-License-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Do you think you can use them to repack\revert Microsoft-Windows-Security-SPP-Component-SKU-ServerHyperCore-Package~31bf3856ad364e35~amd64~~10.0.14393.0?
Thanks. The image itself has the same "pending" issue. Code: <InstallerQueue Length="0x00000001"> <Action Installer="{3eca0b00-79bb-42b9-8421-a26a5cbb37e4}" Mode="install" Phase="0x00000026" Family="Microsoft-Hyper-V-Drivers-Hypervisor-Bcd, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" New="10.0.14393.0"/> </InstallerQueue>
Microsoft-Hyper-V-ServerHyperCoreEdition-Package~31bf3856ad364e35~amd64~~10.0.14393.0 ---> Microsoft-Hyper-V-Online-Package~31bf3856ad364e35~amd64~~10.0.14393.0 ---> Microsoft-Hyper-V-Hypervisor-Package~31bf3856ad364e35~amd64~~10.0.14393.0 ---> Microsoft-Hyper-V-Hypervisor-onecore-Package~31bf3856ad364e35~amd64~~10.0.14393.0 ---> amd64_microsoft-hyper-v-h..-onecore-deployment_31bf3856ad364e35_10.0.14393.0_none_79af78b22a711a5a.manifest ---> amd64_microsoft-hyper-v-drivers-hypervisor-bcd_31bf3856ad364e35_10.0.14393.0_none_433654b7ff3a7dac.manifest Code: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved."> <assemblyIdentity name="Microsoft-Hyper-V-Drivers-Hypervisor-Bcd" version="10.0.14393.0" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" versionScope="nonSxS" /> <bcdedit xmlns="urn:schemas-microsoft-com:asm.v3" Element="current" InstallValue="auto" Property="hypervisorlaunchtype" UninstallValue="off" /> <fveUpdateAI xmlns="urn:schemas-microsoft-com:asm.v3" fveCommand="WindowsBootEnvironment" /> </assembly>
Q: How to make Server showing and\or working exact Features of Client with the least Server packages?
I am used to use the installed system. And I do it for my own purposes. e.g. To check if the reconstructed image is alright.
No. I want to check 'systemreset" functions, and other purposes via command line, not Settings. e.g. Server Settings does not have "Reset This PC", then I need "systemreset". Windows 10 has this command line for Client and Server. Windows 11 26100.1, no.