Removing Cortana certainly causes some issues on RS2. The start menu acts very funny and pinned things keep coming back, disappearing, and just flat out not working. I think moving it out of the default "remove all" is a good idea for those who don't need it because they have a start menu replacement, but maybe just disabling Cortana via the registry instead of killing the package is a better idea.
Notepad++ shows line numbers and syntax highlighting. PRO-TIP: Instead of 'REM' better use '::'. Although a line with REM is not processed, it still needs time to 'read' the line in the process, where the :: is interpreted as broken 'Jump Target' and skipped without 'reading'.
Not so, they just haven't updated their page yet. The release notes are available (check the link I posted) and the new version will appear on their page one of these days. Cheers.
I did check your link. Filehippo & MajorGeeks both got the April 27th Version. My Avira Antivirus which is on March version said mines is already up to date.
TestRoot package is a part of the Install.wim and comes within the image, just use the install_wim_tweak.exe to get the package list and see in it. Only, if there was space for more menus and menu commands I could add it, so at present you can add the package to the RemovePackages.txt list and remove it using 4->4 Menu.
Well, I'm not having any issues with the Start Menu when Cortana or any other package listed in the ToolKit Remove Components are removed. I have tested several times with the ToolKit and installed the OS.
Some people ask for an option for Removing All Components in one go and some ask for Remove All Except this or that and some do ask to move this or that component to advanced or manual removal section. It will be difficult to fulfill each one's wishes coz either I do have to make all component removal manual or all-in-one go. So, please do wait for the GUI where the freedom to choose the desired list of component can be achieved.
Never mind - at the moment I'm testing it on a host running untouched Win10 Creators update and so far everything is working fine, so I'll just use virtual machine to play with toolkit. Thanks for your help!
I copied the zip file to the root of E:\, then extracted it to a folder with the same file name ToolKit-v7.1 then the error happened. Try it for yourself. That also happened on v 6.9 and for a while I stopped using the tool thinking something missing in my OS which is the Creators Update is preventing it to work. Then I tried putting it on C: and it worked like a charm.