Q: Last night, the images made by my new 26100 Reconstruction script failed to boot to Desktop unexpectedly. Why? A: The constructed image, which is fine itself, is no good for reconstruction source image.
Q: What is the most weird Windows package? A: The Server Core Fonts package. It is divided into two parts: Part-1: The Parent package with only one of six Child-packages. Part-2: The other five Fonts Child-packages.
Q: For Client workstation, if I just want a fixed CU build, which Server packages can be removed? For easy custom update, we can reconstruct Server without this advanced Server Role package: Microsoft-Windows-EditionPack-Server-Roles-Full-Package
https://forums.mydigitallife.net/th...struction-project.80939/page-841#post-1843425 still fingers crossed for multilanguage enterpriseg
Q: Despite lacking a couple of required App dependency, is this 26100.1 EnterpriseG in official structure? 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-Windows-EnterpriseGEdition" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> <package identifier="Windows EnterpriseG Edition" releaseType="Product"> <update name="Microsoft-Windows-Foundation-Package"> <package contained="false" integrate="visible"> <assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-EditionSpecific-EnterpriseG-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-EditionSpecific-EnterpriseG-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-RegulatedPackages-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-RegulatedPackages-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-RegulatedPackages-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Client-Desktop-Required-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Desktop-Required-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Win4-Feature"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Win4-Feature" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Win4-WOW64-Feature"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Win4-WOW64-Feature" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Client-Features-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Features-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Client-Features-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Client-Features-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-EditionPack-Professional-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-EditionPack-Professional-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-EditionPack-Professional-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Common-RegulatedPackages-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Common-RegulatedPackages-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Common-RegulatedPackages-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Common-RegulatedPackages-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> <update name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package"> <package contained="false" integrate="hidden"> <assemblyIdentity name="Microsoft-Windows-Required-ShellExperiences-Desktop-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update> </package> </assembly>
hi, i have weird situation in 19045.5854 serverrdsh which i'm using. bitlocker is not enabled, but diskmanagement shows it is. ps. solution: enable and disable bitlocker (recovery key can't be saved on encrypted drive of course, print to pdf alternatively)
Q: What is old builds' System Core? A: e.g. [10240.16384 Client amd64] Code: Microsoft-Windows-Client-Features-Package-AutoMerged-admin~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-amcore~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-avcore~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-base~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-com~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-drivers~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-ds~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-enduser~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-inetcore~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-inetsrv~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-mergedcomponents~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-mincore~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-minio~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-minkernel~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-multimedia~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-net~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-printscan~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-redist~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-sdktools~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-termsrv~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-ua~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-vm~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-windows~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-Package-AutoMerged-xbox~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-admin~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-amcore~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-avcore~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-base~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-com~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-drivers~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ds~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-enduser~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-inetcore~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-mergedcomponents~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-mincore~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-minio~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-minkernel~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-multimedia~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-net~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-printscan~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-redist~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-sdktools~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-shell~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-termsrv~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-ua~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-vm~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-windows~31bf3856ad364e35~amd64~~10.0.10240.16384 Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-xbox~31bf3856ad364e35~amd64~~10.0.10240.16384
Is there a way to disable Defender via packages? Or create disablement cab packages and then integrate them via DISM? I really have this question...
Q: Which way is better? 1. Reconstruction: With residual of source image + Always bootable + Not fully customizable + Not capable of doing all Editions. 2. Neutral reconstruction: Without residual of source image + Always bootable + Fully customizable + Capable of doing all Editions.