Well the new idea now can be is to minimize ram usage and improve performance, but that depends on our dev.
Sergey130270, By the way, a new OEM version 24H2 [26100.1742] has appeared on the network. Just as in the previous version, the image contains three editions, including IoT LTSC. And another question: in your script I saw only five standard files for general image localization, but what about FODs? For example: when localizing an image, I use 8 main files and 88 FOD files. It turns out to be completely complete localization, but how do you deal with this issue? And RemoveList, in this version, why is the reserve empty?
Get-Features -для получения списка информации обо всех функциях определенного пакета в образе Windows. Get-Capabilities -получение списка возможностей образа и статус их установки. Get-ProvisionedAppxPackages -получение списка информации о пакетах приложений (.appx) в образе. После обработки образа скриптом Вы получите полную локализацию.
I got it, I already saw it, and out of habit, I looked for possible deletions in the RemoveList folder - thank you!
It’s not about that, it’s about ensuring that comments on this site are written in English. Regarding your script, very good job, thank you!
sergey130270, Here, in this Slimdown10 topic, it’s probably not entirely correct to discuss the Integrator topic? In itself, as for me, the Integrator script is so good that it can deservedly count on its own theme - Integrator. IMHO p.s. Well, for us, admirers of your Integrator in this topic, drop a link to your new topic.
here is the last script made by dark dinosaur. for online version windows 11 am suing 24H2 https://forums.mydigitallife.net/threads/slimdown10-–-turn-windows-10-22h2-or-ltsc-2021-into-classic-legacy-windows.86552/page-46#post-1815008
Good morning, Yes. I already had it here with me. I started taking a look, but there's not much to add, because in online mode some things won't be possible. I'll still do some more research.
Hello, the question is not entirely on this topic: I like it when the boot.wim file is not large, but I couldn’t find such a Russian one. That’s why I took the English boot.wim file, 234 MB in size. In it, index 1 has been removed due to its uselessness. That’s actually the question: In order for your script to properly localize the remaining index of my boot.wim file, what do I need to remove or comment out from your script?
Hi, you don't need to delete anything, you need to export the desired index first and change the index variable I'll write you the code tomorrow, I'm at work today. Good?
OK, I tried removing part of the code with index 1 from the script, and changing the value of the remaining second index to "1". The script reached this point and collapsed. Apparently I'm doing something wrong. p.s. Actually why do I need all this: I found in the Internet file boot.wim, as I wanted, relatively not large size (index 1 naturally in it removed). Localized it, and everything would be fine, everything seems to be normal, but at the start of the installation pops out the message Setup is Starting. And I want it to be Начало Установки. Dug through the whole boot.wim file in the Restorator, but could not find where this message is formed to edit it. That's why I want to try to localize this file with your script, in case everything works out and I will see this message in my language. It is clear that all this is a whim, but this little thing just does not give me peace of mind.
your script :: Unmounting image "%DISM%" /Unmount-Wim /MountDir:"%BootMount%" /commit add this code "%DISM%" /english /export-image /sourceimagefile:"%BootWim%" /sourceindex:2 /destinationimagefile:"%BootWimTmp%" move /y "%BootWimTmp%" "%BootWim%" >nul
Lads I am using SunLion's SD11v202_4.8.21 with a UUP Dump iso ver: 26100.1.240331-1435.GE_RELEASE_CLIENTPRO_OEMRET_X64FRE_EN-US Script runs normally though when I run in a VM getting this.