Is this works? I made a few fake ones none of them worked. If it is not good as it to be updates gives cbs error. I know you can update. It means it works as it should be. My updates gives error because of this package now. If updates gives error all effort is useless I will test later. Now i have another solution needs to be tested. I am sure it will work %90 but this problem should be solved in any condition. Biggest problem of server 2025. I do not know other servers. I used nearly exactly same mum not worked. I also used one of ordinary cats as catalog. Changed name. Searched components hiv there is no registry key with "target" in it. Also searched "Software" hiv. There is no "target" in there too. This package is a ghost. There is no registry key about it but how dism can know it is needs. Also in sessions.xml no "target" packet integrated. With update dism try to update this package. But wadaaa there is no such package. Result is error. If you do not take this error. Because you are using a base image like azurestackhcl or servertribune that already has this package. Also at that condition you need to delete this line for succesfull tribune install on azurestackhcl I think this is a like a copy protection for reconstructors.
At last I was able to achieve what I wanted from 25398 client. It is localized (Russian), 25398.1 (no integrated updates) and it does update with original non-modified LCUs It has working NETFX3, Store and all the Features on Demand. Settings are localized correctly, Win+X works, no flashing Spoiler Want to thank everyone for support here, it was a good experience, and I still have a lot to learn from you. Master xinso, thanks for patience, I am not always online, due to service, and sometimes ask same questions twice, your help is very valuable! Might also thank pp03 for help with NETFX3 language pack, gailium119 and zhanglin for their earlier and ongoing work. Creating a localized image that doesn't require custom updates is a good step! Time to switch to Azure Stack HCI for me, I really want to understand how to make an updatable full Desktop image now - without custom updates.
how did you do that? if so, i would rather to use system in my language with officially updates, not custom.
All the things we do with Azure Stack HCI are interesting mostly for future, - as it is released annually (with AC cycle ServerDatacenterCoreAC and probably with Client). Consider 25398 as previous version, when you had no ServerTurbine full or ServerDatacenter full, so do not try to take parts of datacenter full, - when we have LTSC branch, we are happy to use full. But time goes fast and soon a brand new branch would appear with core only server editions. Interesting task is to get what can be taken from same-build client to make a full desktop. Like with 1904x (windows server 2004 (20H2) and 21H2). You are showing a lot of datacenter full + added HCI edition. What is the value of that, except of failures and not-installed updates? HotPatching? We heard nothing in this topic yet about server-side hot patching, - only about installation of a client "hot patch" LCU - with a reboot required. Epic failure.
Every patch and update will work. The value is you have to take all if you want it to get updated. If take only needed packages updates will never successfully update. You will test and see in the future. At least i think so. I have no power to make one more try. Get very tired. Need test if i remove Microsoft-Windows-WirelessNetworking-HCI package with installwimtweak will it come back. If not no need to edit mums in the future
I see on your screens a big list of roles. Some of them are from datacenter only, if I understand tr-tr correctly. That means, you added some packages from server full, which are not available for example in 19041 and 25398, and it would be more difficult in AC builds I guess? But I am following your steps with great interest!
Exactly. If update has a "hotpatch" in name, it doesn't require restart on true-hotpatch capable system. Other LCUs are "baseline" For 24H2 we have one update with HotPatch in name. And there is a way to install it with couple of registry keys, - but it does require restart, - so hotpatch doesn't work as "hot", while as "patch" it works fine, version increases