I have provided a CustomFiles folder inside ToolKit's Packs folder in which you can copy your custom files like wallpapers. You need to create the proper folder structure inside the CustomFiles folder and then copy the required files. For Example: For Themes : <toolKit\Packs\CustomFiles\<OS>\Windows\Resources\Themes> For Running Post Setup Scripts : <toolKit\Packs\CustomFiles\<OS>\Windows\Setup\script\setupcomplete.cmd> For Copying files to System32 Folder : <toolKit\Packs\CustomFiles\<OS>\Windows\System32> For Wallpapers : <toolKit\Packs\CustomFiles\<OS>\Windows\Web\Wallpaper> Note : If you use any Custom Files that will overwrite an existing file then some times you need to take file/folder permission to overwrite it.
It's not that I'm refusing to Add new features to the ToolKit which the users are requesting But rather it's due to the DOS batch scripting limitation where it was difficult to implement some features like choosing the menus according to per user choice and other features like MUI Integration, AIO, Add-ons requires more time to test. MUI integration will be available soon as I have worked on it and also added to the GUI version and so the same will be added to the CMD version too. The code is already open-sourced long before, and some of the members are using it with their own customization, and do provide feedback and code-fixes too.
Ok will explore the option to put the code on Github and see what can be done. And, for the GUI version code, Right now I don't have any plan to release the code at this stage as it's too early to say.
No, not all. I was just saying why should any project become open-source. I wasn't saying that you refused to implement anything. It's exactly the opposite, the fact that you add plenty of features and is working actively on the Toolkit that opening the source is unnecessary at this point.
I am also trying to delete the entire ToolKit-v6.3 folder now after this failed removal of components process, it says I don't have permissions even though I took ownership of the folder and set it to every one! what the heck
it is not necessary to modify the updated build of January 2017. Take the original image (14393.0) from July 2016.
Latest version probably contains extra cancer cells and more aggressive efforts to force filth on their customers. Micro$sloth has proven time and again that they cannot be trusted and lack integrity. The "newer is better" approach has serious flaws. Got to be careful and smart when it comes to saying yes to anything from the Redmond Mafia.
There is no latest version, the updated jan iso doesn't contain any new features, it's just the 1607 + 4 updates integrated and the CU is from November 2016. So just integrate all updates incl January CU and you have a newer/more uptodate iso then the "newly" released iso.
Updated the ToolKit to v6.4 Highlights: + Improved .Net Framework 3.5 and WHD General Updates Integration Speed for Windows 10 + Moved WIM Component Cleanup with ResetBase from WHD Updates Integration to Apply Source + New Feature to Remove Windows Components using Package List + Merged Windows Store and Xbox Apps Removal Changelog v6.4 + Updated the Feature "Integrate Microsoft .Net Framework 3.5" to Improve Integration Speed (Thanks to tito & xinso). + Updated the Feature "Integrate WHD General Updates" to Improve Integration Speed for Windows 10 Source OS (Thanks to tito & xinso). + Updated the Feature "Integrate WHD Updates" to Reflect the WHD Hotfix Repository Update List. + Moved the Option "WIM Component Cleanup with ResetBase" from the Feature "Integrate WHD Updates" to "Apply Source". + Updated the Feature "Remove Default Metro Apps", Merged Windows Store and Xbox Apps Removal to Fix Store not Working When All Apps Except Store Are Remvoed for Windows 10 Source OS. + Updated the Feature "Remove Default Metro Apps" to Remove Microsoft Xbox Speech To Text Overlay App for Windows 10 Redstone 2 Creators Update Preview Source OS. + Updated the Feature "Remove Windows Components", Merged Windows Defender App Component with Windows Defender Component in Remove Advacned Windows Component Section for Windows 10 Redstone 2 Creators Update Preview Source OS. + Updated the Feature "Remove Windows Components" to Remove Windows Defender Application Guard Inbox Component for Windows 10 Redstone 2 Creators Update Preview Source OS. + Added a Feature "Remove Windows Components Using Package List". + Fixed Minor Bugs in the ToolKit (Thanks to MDL Member Kenafri).