ToolKitHelper.exe.config is the app configuration file, it's already present in all previous Toolkit versions, this is just an updated one, copy it to the bin folder and replace the existing one. Usually, the new changes added to the config are required for App built for .NET Framework 4.6x and older versions, the App built for .NET Framework 4.8.x doesn't require these changes. But still the long path names are not working by the App and that's why have added these old settings to see how it works. Working on a separate File and Folder Helper class for ToolkitHelper program to use Native Win32 internal commands like DeleteFileW, CopyFileW or MoveFileW to deal with long folder path issue.
No, Toolkit v13.3 will support only the 2262x.1265 [KB5022845] update. Since they have added new moment 2 features in 22621.1344, there are too many changes and requires updating the Toolkit.
Apart from Windows Update removal, there are updates to all components to support the current patch Tuesday update and also fixes the issue of NcsiUwpApp removal breaking the Network Icon Status in System Tray.
I hate to say it, but I feel that Windows 11 will be a constant fight for you from now on. I hope not, as I am sure that you already have enough to do now.
are ETA allowed to ask.? been checking daily. was going to start but then saw the mention of 13.3 update.
I must have gotten lucky. Removing the NcsiUwpApp doesn't break the NCSi indicator for me. @MSMG did you have a chance to look at the issue with the shared Edge Webview systemapp and secure assessment browser issues as mentioned here... https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-1230#post-1775060
before i remove components could anyone help i have some doubts about some apps. Internet explorer- safe to remove.? Game explorer.?? needed for microsoft games. i use solitary. i dont use account.. i only use store to update solitary and installed apps AAD broker plug in Account control Edge classic browser.?? setting sync.? xbox callable UI.? i dont have xbox live
Now that Windows updates can be removed, I am going to see how annoying it is to do manual updates. I hate the way Defender always come back but with more built in control over updates, it might be reasonable to live with.
Remove it using dism not the toolkit, I never had it reappearing, not sure why @MSMG decided to use the toolkit over dism to remove defender, like it used to do on old versions.
It always comes back with CU installs. With updates removed that won't be a problem since the only time I will ever update is when I install a new modified build over the top.