You need Microsoft-Windows-Client-LanguagePack-Package-amd64-ru-ru.esd in your casee from UUP files when you download 10.0.26100.1_ru-ru and you exract in lp folder deleting the en-us
Got it, thank you very much! Of course I could have guessed about "lp" myself, but it only occurred to me after your hint...
@balanadi I tested your script without an error ran in a vm worked very well for mine! I will customize to remove store and do more testing, thank you for your script.
I found this one in a 26100 pro to LTSC reconstruction ... Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="stage"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.26100.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="install"> <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.26100.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="Microsoft-Windows-EnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.26100.1.mum" /> </package> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.26100.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend>
to remove store just delete the folder Appx cause already is removing store before starting the reconstruction
I see, but in my case the task is different. I don't need to transform anything because I already use IoT Enterprise LTSC. Therefore I think that in my case file 1.xml should look something like this: Spoiler Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-IoTEnterpriseSEdition" version="10.0.26100.1" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="Microsoft-Windows-IoTEnterpriseSEdition~31bf3856ad364e35~amd64~~10.0.26100.1.mum" /> </package> </servicing> </unattend> I assumed that these actions would clear the WinSxS folder and replace its contents with the sxs package files. Which would significantly reduce the size of the WinSxS folder, but this did not happen, to my regret. Apparently, in my case, there is no need to do all this at all and just delete the sxs folder as unnecessary?
My question to you is : if you just install Microsoft-Windows-IoTEnterpriseSEdition without removing Core and Professional maybe that is the reason you have so many in winSxS folder ... there are 3 editions in your image now ...
@balanadi I have included modern calc in the appx dir, it installs no problem as I added to the Add-Appx.txt However I have both Calcs now & tried to delete the win32calc though the script complains & causes some errors in the process, can you advise a simpler way to achieve this?
It's been a while since anyone has thrown out anything new. Either it's time for summer vacations, or all the ideas have run out?
Most people want both small size and the ability to update, so there really isn't much to talk about.
If we discuss which file belongs to which function and whether it can be safely deleted, then thousands or tens of thousands of contents can be discussed.
I disagree with you on this point, because there are as many opinions as there are people. Personally, I created a script a long time ago that does everything I need in the form of install.wim. Nevertheless, the opinions of other users on this subject are very interesting and very important to us. So there's no need for excessive modesty, share your ideas with the audience (if you have any, of course), and we'll choose from them what interests us most, what will make the OS more stable, more transparent, and cleaner of all the unnecessary nastiness that MS embeds in the image. p.s. Why am I telling you all this? It's not the script itself that's important, but the ideas behind it. When we create a script for our own tasks, we literally pick out the commands (codes) that are important and interesting to us from their scripts, bit by bit. That's why I'm saying that constant exchange of information is very important for us.
It's not about the words, but about the fact that we don't yet know an effective solution for removing unnecessary components from the Windows image. Because in fact, these components are not physically deleted, but simply their tables of contents are erased. For example: Edge folders take up 550 MB in the image, we supposedly delete them and they really don't work, but the image itself doesn't shrink by a single gram. This is because the table of contents has been erased, but the “body” itself remains in our image. This was specially done by MS so that there would be the possibility of system recovery. That's why I pay such close attention to the scripts posted by our colleagues. Who knows, maybe someone will suggest something interesting on this subject?
Yes, 24H2_Integrator_10.19 is the latest version as of today. I can't speak for everyone, but it doesn't work for me and a number of other people. Until SunLion releases something new, I recommend using version 24H2_Integrator_10.10.
Hello, have you tried this reconstruction method yourself? I tried it out of curiosity, but somehow nothing worked out for me with the reconstruction of PRO in LTSC. No matter how I twisted this code, but it was PRO so it remained PRO ... I wanted to try to make Windows 11 Build 27898.1000 PRO into Windows 11 Build 27898.1000 IoT LTSC. It has an IoT Enterprise edition, do you happen to know how to reconstruct it into the IoT Enterprise LTSC version? So far, I haven't been able to do it.
1、key 2、Windows\Branding\Basebrd 3、Windows\System32\spp\tokens\skus The main elements of version conversion usually require modifying the registry to correctly display the converted version information.