That's hard. Because here it was working and not there, it really makes the bug hunting difficult, but it was good to implement some logical conditions, in the code, to avoid probable problems. I already found the problems with the help of a friend @haris_mdlf69 and @bala1. IMCK packets were previously attached to the message. As the size of the package has already passed the maximum attachment size limit, allowed in forum messages, and is being made available via FileServer, I thought it would be interesting to make a complete package available. I think this makes it easier for everyone, instead of having to merge projects. Download in my signature. Please do the download again! New package size arround to 50mb.
About the support for components removal is the same builds as Toolkit supports. About the new components, becareful. They are tricky. You need to retain in System Apps Menu these components: ClientCBS InputApp (will be in Menu only for 17763 to 18363) ShellExperienceHost StartMenuExperienceHost UndockedDevKit (this is not present in any Menu) But available to remove with list.
I just ask because is curious for me .... before (in time when i write here abou beta) i just deleting hole component menu and apply all tweaks without issue .... if we dont talk about cortana delete whitch in windows 10 break menu and other soft problems but maybe because i miss new thinks to remove ... maybe will be thath ... i will look thx
I did a different method. Because the User will always be able to extract directly over the previous IMCK version without fear of losing his personalized lists. This way, on the first run, the file "Examples_List.zip" will be extracted. Then, you customize your lists and in the next few times this file will no longer be extracted. Keeping your lists intact. So the lists are inside that zip.
Can you bring me the oobe panther folder. I have a script that copy the panther folder to pendrive if you are in VM please install with a pendrive not directly from ISO. put the PANTHER.cmd script in pendrive's root. when the error occur: shift + F10 (open cmd) your pendrive shoudl be D: dir (to see its content) if "PANTHER.cmd" is there just type panther. Code: D: dir panther will copy the Panther folders to your pendrive. Should be 2 folders. Compress to zip and send to me. Shoud be fit as attachment here.
Today try again but with 22000.1936 iso and not 22621.1702 ...same issue ... soo here u go my friend ...thx
It works well used code change: Code: set "Langs= ar-SA bg-BG ca-ES cs-CZ da-DK de-DE el-GR en-GB en-US es-ES es-MX et-EE eu-ES fi-FI fr-CA fr-FR gl-ES he-IL hr-HR hu-HU id-ID it-IT ja-JP ko-KR lt-LT lv-LV nb-NO nl-NL pl-PL pt-BR pt-PT ro-RO ru-RU sk-SK sl-SI sr-Latn-CS sr-Latn-RS sv-SE th-TH tr-TR uk-UA vi-VN zh-CN zh-HK zh-TW " set "LOCALES=%ROOT%\LOCALES\LOCALES_zh.cmd" You should add a filename policy that determines the language to determine which display language should be used
You did it directly. But you wouldn't need to make the change, within IMCK. The LOCALE_zh file inside the LOCALES folder should start. I'd even like you to report bugs you find this way to me. And that way while you do the translations, the variables that have not yet been translated will be displayed in English and you will be able to use the tool in hybrid mode. Remember the LOCALES will call your LOCALE_zh, so the LOCALE_zh need to follow the layout of LOCALE_pt only to avoid the code block that calls LOCALE_** at end of LOCALES.cmd. About HEADER we need to put it in english in pt file. Please do it in english end chinese langs in you file. We need a fixed location here in the thread for each language maintainer to place their updates. My suggestion is that you could use your first post to post your language pack updates. So this post will be pinned by @bala1 to the maintainer list. Could it be? When you release a new version just let us know with a new message pointing to your link. You can put your post link in yout signature too. It is up to you. I made some changes due to reported bugs. If you are using multi languages on your host send me a screenshot of the host information screen in English. This was an issue fixed in the en-US version with en-IN language installed. This displayed multiple languages with strange characters inside the variable (en-IN\0en-US). And, it could cause problems in creating the "AutoUnattend.xml". I'll send it to you today. For now, just replace from this: Code: for /F "tokens=3 delims= " %%o in ('reg.exe query "HKCU\Control Panel\International\User Profile" /s /v "Languages" ^| findstr.exe /I "REG_ _SZ"') do (set "HostLanguage=%%o") to: Code: for /F "tokens=3 delims=\ " %%o in ('reg.exe query "HKCU\Control Panel\International\User Profile" /s /v "Languages" ^| findstr.exe /I "REG_ _SZ"') do (set "HostLanguage=%%o")
Out of curiosity, can you send me your autounattend.xml Edit it replacing your password and reminder passaword with XXXXXXXX. If you want. replace the other user data as well. There are multiple entries, so use the replace tool to replace all entries. You can send me via PM. Please make the above suggested change before new tests.
If anyone gets a message similar to "PrecleanUp Registry Operation" and got stuck. Just press "Y" to continue. It will perform the unmout and discard. It is rare, but could happens. Especially if you close the script abruptly for some reason. In the search for error messages, I ended up interrupting the output display of messages right at that moment that asks if you want to do the initial cleaning. It is fixed and comes out in todays version. Spoiler: about trajectory A little about the trajectory of this project: In this release it was expected to find some simple problems, but crashing problems were unusual, hehehehe We have been preparing this version for release since November 2022. Just when we thought it was all right... But it's taken from there, to now doing revisions for us to release and the fact that we're dealing with the multi language tool, we had not tested it in another language besides pt-BR. Spoiler: About the giant package: It will return to what was before. Keep 2 folders with packs and with ISOs results in too many storage consuming. Extract in MSMG Toolkit's folder is the best option. As it is the structure of IMCK. I will release in the package only what is complementary. It's better this way. Spoiler: The Ethics Now the factor that weighs the most. Distributing "ToolkiHelper.exe" directly is out of the question. This is @MSMG's work, exclusively from him. That is, this was distributed in this brief moment to facilitate your tests and to be able to solve the problems more effectively. Your feedbacks was critical to the refinement of this localized release version. We hope you like the end result. We hope to release this version today.
Soo u can make permanent folder link for download and have archive for all version if u have it in past and thath zip have if i remeber aroung MB?
I will do it soon as it is stable and will keep only the stable ones. But no full packages. Full package, only if the @MSMG grants me authorization to distribute within the package.
Yeah i understand its not problem give inside ur bat some invoke,wget,curl for get msmg and extract in future if u want.... yeah i mini thath minimal package ... maybe i badly write