yes I totally agree and I always think about it since the first Toolkit even in Windows 8.1 times so I believe that we should collaborate with our master in other parts of the Toolkit itself a good example is the readme as you said in my view the our master as a programmer knows how I’ve never seen doing his job the best possible before but the Readme needs to improve to be more objective we’re going to combine our thinking and improve the Readme what you think friend ...
I think, the better way is leaving README as it is (as a Main workflow for different OS) and create a separate HELP file with the next stucture: Code: • Option 1 Description • Option 2 Description The main issue is a time (as usual) for such big, accurate and detailed work... (I have my own draft on my native language. Also I'm not "an English man in NewYork" (C), as well)
If you are integrating features like Drivers, Language Packs, DaRT, Updates to boot.wim and winre.wim then you need to mount them.
From Updates description provided by MS site or open the update file with 7-zip and open the package xml file to know to if the update is applicable to WinPE images.
There was PDF Documentation provided in early stages of Toolkit and due to frequent changes in the Toolkit structure had stopped updating it, will take time to update it.
well I think it’s a case to think about better because the readme is very important since it’s the beginning of everything and as for the language I don’t see any problems, I’m also from Brazil and I give my "way" using the Qtranslate application (qsoft .com) fantastic tool since it has translation into languages that I never saw just my two cents ...
Something weird. Toolkit v10.8 Windows 10.19042.572 downloaded via Microsoft tool (therefore, esd file) If I convert the esd to wim usind DISM in command line, it converts all the indexes though some other problems arise If i convert to wim using Toolkit... it converts and keeps only Windows Home ?
@MSMG So here my report. I've done 2 tests prepearing the same LTSC image. Integrating .NET 4.8, Applying Updates (SSU, CU, .NET), Removing packages, etc. The only differences: • Boot images were mounted Code: Do you want to mount Windows Setup Boot Image ? ['Y'es/'N'o] : Do you want to mount Windows Recovery Image ? ['Y'es/'N'o] : • The way Updates were applied (accordingly) Spoiler: RESULTS 1) Everything as usual - No issues - Mounted: install.wim only (as usual) - Windows Updates: applied to install.wim only (as usual) 2) Windows Install failed - Mounted: all *.wim images - Windows Updates: applied to all *.wim images Errors: As I remember, after applying to mounted images boot.wim, winre.wim Code: [===== 9.2% ] The operation completed successfully. [===== 9.4% ] The operation completed successfully. install.wim was OK: Code: [==========================100.0%==========================] The operation completed successfully. Windows installation failed on very early stage, just after pressing [Install] button. Error was about issues with drivers for the storage media with image (Flash / DVD media) ---------------- I guess, there should not be such problems, because I didn't do any manipulations with boot.wim, winre.wim itself... They were only mounted and all updates were applied to all mounted images - that's the only difference. Also, I'm usually see 99% instead 100% for cleanup (usual usage, with only install.wim mounted) in v10.8 I don't remember was v10.7 affected also or not. Spoiler Code: ------------------------------------------------------------------------------- ####Starting Cleaning Up Source Images with Component Cleanup & ResetBase###### ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Performing [Install.wim, Index : 1] Image Component Cleanup... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.20246.1 Image Version: 10.0.17763.1518 [===========================99.0%========================= ] [==========================100.0%==========================] The operation completed successfully.
The Toolkit's ESD to WIM conversion exports only the indexes selected, if you want all indexes then select A
So, while the components are being cut from 19042.572. I'll write a test. Was taken 19041.1, integrated updates .572 and 20h2 (will be 19042.572) without cleaning. Next, the image is installed on the VM for verification. Sfc / scannow is also being updated .610 is established. Next test: removing components with version 10.8, installing on a VM, and checking the update installation .610. In the previous test, you couldn't install updates after Toolkit. I'll let you know when I do.
For integrating updates to boot.wim or winre.wim you need to use WHD update pack menu and should copy the required updates to WHD folder with the necessary Setup Media updates (kb4582760). It's normal that the cleanup won't show 100% always, sometimes 20%, 80%..
Hmm... I didn't applied KB4582760 at all (I didn't know about that KB, thanks!) Probably, I need to find a better place/website to track updates more accurately and quickly. What you can recommend? (more handy than catalog.update.microsoft.com) Other updates were in WHD correspondent folders. Spoiler: LTSC UPDATES Packs\NetFX48\w10\ : Microsoft-Windows-NetFX48-Package~31bf3856ad364e35~amd64~~10.0.16299.15.cab Packs\NetFX48\w10\ : Microsoft-Windows-NetFX48-Package~31bf3856ad364e35~amd64~ru-RU~10.0.16299.15.cab WHD\w10\x64\ServicingStack : windows10.0-kb4577667 WHD\w10\x64\Cumulative : windows10.0-kb4577668-x64 WHD\w10\x64\NetCumulative : windows10.0-kb4578973-x64-ndp48 That's all I used to.
Code: [E] - Integrate Windows Updates using [Integrate->Windows Updates->Windows Updates] menu. Note: The Toolkit supports updates either in .msu/.cab format. If using Windows Updates Menu, then Copy the Windows Updates to Toolkit's <Updates\w10\<Architecture> folder E.g: <Updates\w10\x64>. if using WHD Update Pack Menu, then Copy the Windows 10 WHD Update Pack files to Toolkit's <WHD\w10\<Architecture> folder (E.g. <WHD\w10\x64>). Copy Windows Cumulative Update file to <WHD\w10\<Architecture>\Cumulative> folder (E.g. <WHD\w10\x64\Cumulative>). Copy Windows Defender Update files to <WHD\w10\<Architecture>\Defender> folder (E.g. <WHD\w10\x64\Defender>). Copy Windows Dynamic Update files to <WHD\w10\<Architecture>\Dynamic> folder (E.g. <WHD\w10\x64\Dynamic>). Copy Windows Enablement Update files to <WHD\w10\<Architecture>\Enablement> folder (E.g. <WHD\w10\x64\Enablement>). Copy Windows Flash Player Update file to <WHD\w10\<Architecture>\FlashPlayer> folder (E.g. <WHD\w10\x64\FlashPlayer>). Copy Windows .Net Cumulative Update file to <WHD\w10\<Architecture>\NetCumulative> folder (E.g. <WHD\w10\x64\NetCumulative>). Copy Windows Servicing Stack Update file to <WHD\w10\<Architecture>\ServicingStack> folder (E.g. <WHD\w10\x64\ServicingStack>). Copy Windows Setup Media Update files to <WHD\w10\<Architecture>\SetupMedia> folder (E.g. <WHD\w10\x64\SetupMedia>). Copy Windows WinPE Update files to <WHD\w10\<Architecture>\WinPE> folder (E.g. <WHD\w10\x64\WinPE>). https://forums.mydigitallife.net/th...-17763-xxx-pc-rs5.77945/page-216#post-1490183
I must be following the wrong route then. I follow this one: [1] Source > [6] Extract Source from Media Creation Tool Image I get no option to select what gets exported, it just starts exporting and always end up with Windows Home, Index:1 I suppose.
I tried this but it didn't ask me what XML file to import. Do I need to move the XML file to a certain folder to use it? I tried just doing option 4 > 6, it kept office, mail, edge, photos and store pinned.