Did you read the change log, the Xbox Live (Xbox.TKUI) is required for Store to function and so it's removed when store is selected.
Great explanation, I was observing that, however, I am in a project with Windows WEST <EMB <POSTREADY. The LP or Ip are different for Thinpc and WEST version, especially the Wimpe's Cabs, are incompatible, some work, some do not. My project is looking like a frankenstein rscrsc. But I'm getting it, and I'm very excited, I use your program to integrate some apps, and the rest use the dism not to generate as much conflict. As said by Steve Ballmer, developers, developers, developers! Many use sysprep, but I do not like their method, it's beautiful in theory, but in practice it sucks.
- The Option to Integrate Windows Language Packs in ToolKit is to integrate the Language Packs and it requires the pack made by me as it contains Windows Language Packs, Language Features Packs, WinPE Language Packs. - Only the Language Codes present in the Integrate Windows Language Pack Menu are supported. - You are using the Bengali (India) [bn-IN] Language feature pack which is an optional package available to be added upon en-GB image. - The Integrate Windows Language Packs doesn't support additional/supplementary packages or Language Interface Packs. - Right now, the Integrate Windows Update search for updates files to be in Windows10-KBXXXXXXX-x64.cab or Windows10-KBXXXXXXX-x64.msu. So if you want to integrate the microsoft-windows-languagefeatures-basic-bn-in-package_679f41a31fa39e91da733edba47cc8e3cd8013d4.cab then do manually add it to the image using the DISM command in the command-line.
Yes that's why I have made it easier for them to download the readily available files and follow the instructions. - Ask users to copy the required Language Packs files downloaded from the ToolKit download link to <Packs\LanguagePacks\<OS>\<Arch>\<LangCode>>. - Ask user to Enter the Language Code for Integration. If they still want to use the files manually then the error message displayed in the ToolKit v8.0, very clearly gives which file is missing and where it has to be copied, so that they can easily create the folder and copy the required file in required format. And yes for some languages there are extra fonts packages available and I have planned to add support them in the coming versions.
I do add the Windows Embedded 7/ThinPC Language Packs when I do upload the W7 LP and also the ToolKit does integrate it without any issues. Will check with the WinPE-LP integration for ThinPC and see if anything has to be fixed.
When I try to cleanup my Windows 8.1 image, I'm getting the error "cannot perform image component clean-up when pending.xml is present..." I've correctly followed your guide Windows 8.1 Pro x64 - German
May be some updates/feature or .NetFX has set the pending.xml flag and so you are not it's not able to cleanup the image. The First Post was modified in a last minute due to too many characters, anyway will re-do the test and report back.
Thank you !!! I did it again. Everything works fine. The result is only 2.9gb ISO file. It's very impressive, cause it's smallest size i ever made.
Why do cleanup and reset base for Boot.wim and WinRe.wim not 100% ? Is it normal ? Spoiler: Cleanup and ResetBase =============================================================================== MSMG ToolKit - Cleanup Source Images with Component Cleanup & ResetBase =============================================================================== ------------------------------------------------------------------------------- ####Starting Cleaning Up Source Images with Component Cleanup & ResetBase###### ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Performing [Boot.wim, Index : 1] Image Component Cleanup... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.17040.1000 Image Version: 10.0.16299.15 [===========================99.5%========================= ] The operation completed successfully. ------------------------------------------------------------------------------- Performing [Boot.wim, Index : 2] Image Component Cleanup... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.17040.1000 Image Version: 10.0.16299.15 [===========================98.8%========================= ] The operation completed successfully. ------------------------------------------------------------------------------- Performing [WinRe.wim, Index : 1] Image Component Cleanup... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.17040.1000 Image Version: 10.0.16299.15 [===========================99.0%========================= ] The operation completed successfully. ------------------------------------------------------------------------------- Performing [Install.wim, Index : 1] Image Component Cleanup... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.17040.1000 Image Version: 10.0.16299.15 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- ####Finished Cleaning Up Source Images with Component Cleanup & ResetBase###### ------------------------------------------------------------------------------- =============================================================================== Press any key to continue . . .
So, in spite of that, I should use the option to remove Telemetry because at least some components of it will be removed? Isn't that option useless since it doesn't remove all its components?
Yes it's useless for RS3 and I had thought of removing the Telemetry menu for RS3 as only content delivery manager is left in it. or at least I will rename that menu in RS3 to Remove Content Delivery Manager. As I said in my previous post in coming Branches of Windows 10 there won't be any way to remove the required components using DISM like you have at present, then the choice left is through manual method.
I just want to know which Components except Microsoft Telemetry Services(Windows Content Delivery Manager Package) will disable Windows spotlight. Please tell me. I didn't remove Microsoft Telemetry Services, but still can't use Windows spotlight
Hi MSMG today working with Toolkit V8.0 in W10 PRO x64 (1709) acording script none issues but after make ISO I always see Dism.log for observe some issues so I encounter this 2 errors then I ask I can make install? or is better wait one answer by you thanks in advance
Help me understand if I'm wrong... Let's start with this ISO it_windows_10_multi-edition_version_1709_updated_sept_2017_x64_dvd_100090836 I mount the HOME version to turn it into PRO Workstation So far everything OK... Then I integrate the downloaded updates with WHDownloader 0.0.2.2 Placing Windows Windows10.0-KB4054517-x64 to ToolKit-v8.0\Packs\WHD\w10\x64\Cumulative Windows10.0-kb4053577-x64_c9809c15b7c929213f18b369c0611a98684cb453 to ToolKit-v8.0\Packs\WHD\w10\x64\ServicingStack Windows10.0-KB4054022-x64 to ToolKit-v8.0\Packs\WHD\w10\x64\ServicingStack Process the whole thing and recreate the new ISO, but after installing the updates are downloaded again... .. Where am I wrong?? Thank you