it was a typo error, It's only for Windows 7 - Windows 10 v1803, Use v8.8, it's available under Archive folder in download link. Will add back the support in future versions.
Use the new version the feature to integrate custom tweaks has been added. Copy the registry files to Packs\CustomRegistry\<OS>\<Arch>> folder and use the [5] Customize->[5] Import Registry Settings from Registry File.
You need to copy the patched uxtheme.dll file to the respective folder and use the Menu from Integrate Custom Features.
how to integrate custom cursors? folder is empty... any examples or custom files for cursors available
Thanks. You did not compress Packs subfolders? It will be easier for download, if You compress. 9.4 arrived without Packs subfolders.
hi there, thanks for the latest version of the toolkit! i'm unable to download from mega, could be a firefox issue, tryed via mediafire, but the toolkit version is not yet uploaded there, could there be a direct link to the toolkit file temporellery? would not take me long to download the file? thanks! Majid
and also mega's website is really bad with accessibility, I use a screen reader mediafire on the otherhand is great!
In the coming days, will add more detailed info to the Toolkit's website regarding it's usage. Usually the Custom Files, Registry, Recovery, UxTheme, Terminal Server things are just place holders which the users need to fill in and use the menu in the ToolKit to import them. You can follow this steps - Copy the cursors to the folder <Packs\CustomFiles\w10\x64\Windows\Cursors> - Create a folder <Packs\CustomFiles\w10\x64\Windows\Inf> - Copy the cursors related inf's to the folder <Packs\CustomFiles\w10\x64\Windows\Inf> - Copy the custom registry settings to call the inf in the <Packs\CustomRegistry\w10\x64> folder. - Use the ToolKit's Integrate->Custom Features->Custom Files Menu. - Use the ToolKit's Customize->Import Custom Registry using Registry File Menu.
Thx for the new version but am wondering if removing components can be sped up? It takes 40 seconds to remove just one component. I think you got it down to about 10 seconds at one point with v9.3.2
The ToolKit full pack files are around 40-50 GB and each time making changes to the Pack files and uploading them is not so easy here since I do have a very low upload speed here. And, Also keeping them unpacked will make it easier to update and makes it comfortable for users to only download what they need. You can always right click on the set of folders and download them as zip files.
@MSMG Which build v1903 is better to use for modification? 18362.0, 18362.1, 18362.30, 18362.175, 18362.239?
Use chrome browser since the IE or Firefox don't have much buffer to download from MEGA also you can use the MEGA Extensions to download more efficiently. I do use the MEGA hosting for many reasons like - 50 GB Free storage space, now my MEGA account space has reached full. - Convenient for me to upload and maintain. - So far haven't got one take down notice. You don't need to download all the pack files, just make a note of only required folders and download them, you can also select a couple of folders and download them as zipped. Will try to see If I can provide any other download mirror.
Yes that's due to: - Component removal data is not gathered dynamically at run time but instead it is pre-processed and thus the code size is big. - Component removal MUI data has been added for v1809 and v1903 which makes a large chunk of code size. - For v1809 the component removal is done more in-depth, check out the final install.wim with the older version. But that's not which makes the removal slow but it's the code protection added to Toolkit's component removal program which takes more time to execute the code, even I have reduced the compression level to 1 to make it more faster then the previous version but still it take quite a amount of time due to the MUI data added. I need to work on dynamic processing of gathering component removal data which will make the total code size and execution speed to minimal.