@TesterMachineOS I have found a nice tool your name writes in it. 26100.1_Pro_to_IoTEnts_amd64.7z Did you shared it in here? I have not seen that. I found it at another forum. I looked inside batch files they look also clean and simple. Why do not you share such good tools in here too. Thanks for it. It was one of the main reasons that i have read so many pages in here to add store to ltsc build. Can you add enterprise edition as base image too? Note: It does not remove current language pack before adding enterprises edition. Adding language pack to the edition after already has language pack. Does not it make problem? After "Removing Notepad-FOD-Package" it should also remove current language pack.
I recently posted this script here.. you can go to the index of this thread (page 1) OP#2 Where the reconstructions posted here are stored.. As for what you say about using Enterprise Edition as a base to create EnterpriseS + Store, it is a bit complicated, because it requires the Professional editionPack. But I think it is possible, I will work on this later..
@pm67310 A while ago you asked me about creating Windows 11 IoT Enterprise LTSC + Starter Style.. At the moment in Windows 11 Home + Starter Style + License EnterpriseS, well something that takes time and work to do, because you have to gather some packages.. Now doing it from Windows 11 Pro -> Windows 11 IoT Enterprise LTSC + Starter Style is possible, until now in the sxs I removed some packages.. leaving it similar to Starter, but leaving it as Home (Core) I doubt it will be possible, since some IoT Enterprise LTSC policies seem to be better for low-resource hardware than the Home version with ads and background app installation. I will post results on Windows 11 IoT Enterprise LTSC + Starter Style later. I will just tweak a couple of extra things in the sxs. Edit: I managed to compile it successfully but unfortunately it won't update... so oh well, I guess I'll focus on other Windows 10/11 builds, too bad, for now the only considerable one for limited hardware is Windows 11 22H2/23H2, for 24h2 use IoT Enterprise LTSC because new versions have other unnecessary additions, my recommendation for IoT Enteprise LTSC would be to use some optimizations, maybe disable defender and tune microsoft edge to avoid background consumption + disable unnecessary services.
Enterprise edition has only professional package. There is no enterprise package. Not much important i can do my own handmade build (i did) It's just advise/demand
Removing Microsoft-Windows-Notepad-System-FoD-Package removes its language pack After rebuilding, Notepad-FOD-Package is integrated. Leaving the system the same as the original LTSC. Packages: Code: Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~amd64~es-ES~10.0.26100.1 | Instalado | OnDemand Pack | 7/10/2024 12:41ÿa.ÿm. Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~amd64~~10.0.26100.1 | Instalado | OnDemand Pack | 7/10/2024 12:41ÿa.ÿm. Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~wow64~es-ES~10.0.26100.1 | Instalado | OnDemand Pack | 7/10/2024 12:41ÿa.ÿm. Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~wow64~~10.0.26100.1 | Instalado | OnDemand Pack | 7/10/2024 12:41ÿa.ÿm.
Do you mean like this? Code: Set "0=%~f0"& powershell -nop -c "iex ([io.file]::ReadAllText($env:0) -split '[:]CoreN_XML')[1];DelNudes '%_cad%\%_edi%.mum' '%Editions%'" :CoreN_XML Function DelNudes([String] $xmlFile, [String] $Editions) { if (test-path -path "$xmlFile") { $xml = [XML](Get-Content "$xmlFile") $xml.assembly.package.update | Where {$_.name.contains("Not-Supported-On-LTSB")} | Foreach-Object {[void]$_.ParentNode.RemoveChild($_)} $xml.assembly.package.update | Where {$_.name.contains("EditionSpecific-Professional-WOW64")} | Foreach-Object {[void]$_.ParentNode.RemoveChild($_)} $xml.assembly.package.update | Where {$_.name.contains("EditionSpecific-Professional")} | Foreach-Object {$_.name = "Microsoft-Windows-EditionSpecific-" + $Editions + "-Package";$_.package.assemblyIdentity.name = "Microsoft-Windows-EditionSpecific-" + $Editions + "-Package"} #{write-host $_.name} $xml.assembly.assemblyIdentity.name = "Microsoft-Windows-" + $Editions + "Edition" $xml.assembly.package.identifier = "Windows " + $Editions + " Edition" $xml.Save("$xmlFile") Remove-Variable -name xml } else { Write-Host The $xmlFile NOT FOUND..!! -f Red } } #:CoreN_XML
That sounds new to me! Where can I read, how to disable Defender feature as a part of Client-Desktop-Required-Package? If I do that for 26100.1 (if I can) and later add LCU, that updates Client-Desktop-Required-Package, would Defender remain disabled?
I can try it, I would need to use the shared packages of @iamaHUN where he also shared a build of EnterpriseSN The bad thing is that I don't have any Windows N edition ISOs downloaded, I always download Windows ISOs but not N. I will try to build using EnterpriseS (built with the script shared above) and then rebuild it to EnterpriseSN. So far I have not seen any build that removes the language pack from the system and then adds it back.. It always does the rebuild and then adds the language pack without removing it first.
I have not used any script to build any edition that I also do not know how they works. I only use files from them. I also never tried to add same package to any wim twice. If an install.wim have turkish language pack installed and if i try to install turkish language pack to same wim again if it will give error that package exists or not i do not know. Uupdump install.wims language categorised but also uupdump adds language packs to same wims so it can be possible? Same uupdump core install.wims can not seperately extracted without other cabs and packages too What your script uses as install.wim source? Prebuild uupdump install.wims or any 26100.1 original iso install.wim as base too? Is it change anything? It means same language pack can be installed to same install.wim because you do not remove existing language packs? I always removing all language packs by default. Adding all packages. At the end adding my desired language pack again for not to let any source file to be stay untranslated
I managed to compile it successfully but unfortunately it won't update... so oh well, I guess I'll focus on other Windows 10/11 builds, too bad, for now the only considerable one for limited hardware is Windows 11 22H2/23H2, for 24h2 use IoT Enterprise LTSC because new versions have other unnecessary additions, my recommendation for IoT Enteprise LTSC would be to use some optimizations, maybe disable defender and tune microsoft edge to avoid background consumption + disable unnecessary services.
I am looking for LTSC Insider Preview reconstruction (not a 25941), like I did 22H2 LTSC Resonstruction. is there a way?
Which version of Insider Preview are you looking for? There may be packages to integrate with or you may need to take one from the Windows 10 EnterpriseS packages.
Since build 18362 updates contain delta patches and renewed packages. Under renewed packages I mean the RTM version is 18362.1 and for example you have Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.18362.1 installed. If you add e.g. KB4503293 update, it will install Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.18362.175, which may patch some .1 version files or simply keep some originals. If the update wants to patch anything that is missing because the replaced packages, licenses or anything else that should be there, it will fail, because it cannot create the new patched file using the delta patches. In your case the system is looking for .1 Home licenses, but they are missing, so the process will fail. It would work up to build 17763 until a certain update version, but for a while MS using delta patches with this build as well.
Yes well, now I will focus on other editions, apart from 26100.1 I remember some starter packs for 16299, do you happen to know about that?