What's the point? If you need a core structure with enterprise licensing, just use my SKUwitch technique. Its universal and takes 30 second, (online)
server has package to remove defender client doesnt, from windows 11 so with server 2025 we could change it to enterprise and use it without defender the core wasnt the main point doesn't change the policy i can imagine
I installed the leaked 26100.1 wim and that activates without problems. I guess the files I used for reconstruction are not doing the job necessary for a clean wim. This thread is so convoluted with tests here and there it's hit and miss finding the right files unless you follow all posts here meticulously. 25398 was recommended as a good one to to have for various reasons compared to other newer releases, so I thought I'd give it a try. Maybe a cleaner package for this will emerge later at some point. I compared your log with mine and it looks like I have extra cab files where you only have them as esd. Also Microsoft-Windows-TabletPCMath-Package-amd64.cab is listed in mine and not yours. I will give it one last try with what you have in your log. Maybe my iso from the UUP Dump download was not configured correctly.
Okay, but does the hash on your .7z match mine that I posted? If not, can you make that package available for me to try?
I'm talking of kernel policies, the ones that matters, not about customizations. The latter can be changed, the former are sculpted in stone
some of the settings are not customizable afaik unstaging give this ability to change those sculpted in stone settings
Code: HashMyFiles.exe MD5 SHA1 CRC32 SHA-256 SHA-512 SHA-384 Full Path 25398.1_ServerDatacenterCor_to_Client_amd64.7z c8d4f243bc62d2e9dd4133e65c66e53b 862447dbf101d6bb4d40beec3f812ff4f6d2230c 50a05af9 4439f9f9f0e15394ab50dc3d184bd84d713595a74bfe19836900f48bec3d44e4 474e84bea7de088da2948c683a4daabe546ed3f5821e25d2db1dab813ab6fedfb2d089ba86e0c96bbc00b2e3b23036e2dff615844da9b71396b24f861860c387 f810f37c8948d0a7e3f6387b1c146616ab683f305eb9a3cff220c2dcced2c3cc72c2b83c0b47285ae43263838563b1ec E:\ISO\x\25398.1_ServerDatacenterCor_to_Client_amd64.7z 05/05/2024 23:52:45 05/05/2024 23:50:33 05/05/2024 23:52:52 1,842,783,404 7z A install.wim is extracted from ServerDatacenterCore_en-us.esd Code: Dism /Export-Image /SourceImageFile:C:\ServerDatacenterCore_en-us.esd /SourceIndex:3 /DestinationImageFile:C:\install.wim /Compress:LZX
Ace2, did the install wim from your esd come from uup dump? I ended up with an iso where the wim only had 1 index. See #15825 for uup config I used Code: dism /get-wiminfo /wimfile:install.wim Deployment Image Servicing and Management tool Version: 10.0.17763.3406 Details for image : install.wim Index : 1 Name : Windows Server 2022 Datacenter Description : (Recommended) This option omits most of the Windows graphical envi ronment. Manage with a command prompt and PowerShell, or remotely with Windows A dmin Center or other tools. Size : 9,549,638,691 bytes The operation completed successfully. Press any key to continue...
I know what unstaging does, after all, the unstaging thing started because a my question. What I'm asking is, to put it in poor words, what's the practical scenario where a enterprise core SKU can be useful?
Good question. As I wrote before .830 failed to me even on Pro SKU using the untouched .830 MSU... BTW I haven't tested KB5036910-x64-2024-05-03-EditionMatrix-830.esd, my installation works wonderfully, this is the very first time I feel I can use W11 as a main or secondary OS. So I'm not going to look for problems I don't have. As we say in my country you don't replace the members of a winning team.