Nope, Malwarebytes is OK but I don't use it anymore. My current AV does interfere with the Toolkit though, but simply turning it of during the process is enough to get a good build. I hope MSMG will be back soon. Cheers.
Just knew about your father loss, @MSMG Please accept my condolences. And thank you, one more time, for your wonderful tool. I also just read that nowadays UUP iso's are recommended instead of MCT ones. Do you know if those have .NET updates applied? Or only CU for Win itself? Thanks beforehand
@MSMG We are deeply sorrowful for your loss. Please accept our condolences, be strong in this time of sorrow. We all share in your grief.
You can choose inclusion of .net 3.5 when requesting the download package. In that case, .Net updates for that version will be included. If the .iso has any .Net version included, updates will be applied if you have chosen to do so. In other words, you can select if you want updates or not. Cheers.
Depending on the OS version, .Net 4.6-4.8 will be included by default and as such, updates will be integrated for that version. As for Net 5.0, it is a separate package so you can integrate it with the toolkit. Not sure if 5.0 receives .Net CU, I have only seen updated builds like 5.07 for integration with the toolkit. Edit: I've posted this question in the uupdump topic, just to make sure. Edit 2: Answered already. Only when you provide the NDP CU in the UUPs folder yourself. Only base builds in the dev channel got NDP48 updates by UUP. Hope this clears up any doubts, thanks Enthousiast for the prompt response. Cheers.
I'm slightly out-of-the-loop with getting the latest Toolkit to work. So to put this in recap: 1. I have to download the latest Toolkit .7z file from the MEGA mirror, unblock it and extract the contents to (say) C:\Toolkit\ 2. I also have to download the Toolkit.cmd file (also from the MEGA mirror), unblock it and overwrite the file in C:\Toolkit\ 3. Then, to the latest Toolkit.cmd, i have to apply the fixes from https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-992#post-1671669 Is that right or am i missing something here?
This is a very nice piece of software. I have one question. When apps are being removed like components (Camera, Xbox, etc.) and other features like OneDrive and Windows Defender. Upon next Windows 10 update, will all these features be replaced? Or can I simply use Chris Titus Tec Debloater tool to disable features updates and only allow security updates?
I am also getting errors when trying to uninstall windows app (Maps, Feedback Hub, etc.) I did not do this before and I am stuck?
pl try on win10 Host OS to remove metro apps , system apps , packages from 22000.xx build i think it will resolve the issue.
With the latest update of toolkit.cmd, there isn´t the option to integrate DaRT 10 anymore. There is just the option for DaRT 11. Were can I find the new version?
I used toolkit 11.6 for removing packages from 10.0.19044.1147 iso but it says Error: Unsupported Windows OS Image ToolKitHelper only support Windows 10 v1809, v1903, v1909, v2004 and v20H2 Does anybody know how to fix it ?
On Windows 11 ISOS I integrated Dart 10 and it was integrated correctly, but I haven't tested it working. Since this leaked Windows 11 is based on 19041, it should work. You will probably have to rename the files. Check the folder and files name requested by the Toolkit. I'm going to post a Custom Toolkit with a minor bug fix plus the new version of CreateVirtual Editions and I'm going to add an Official Toolkit named as Toolkit_Beta.cmd, with some Fixes to help everyone, until @MSMG returns. This is the file I'll be changing as I find something to improve. It already has the Skins integration, optimized too. When it's Windows 11 to integrate, for now, Dart 10.
This is related to updating the Toolkithelper.exe binary In this case, only when MSMG brings an update. In Toolkit, you will only be able to remove, at the moment, through DISM list.
Toolkit_v11.6\Packs\NetFX48\w81 Microsoft-Windows-NetFx48-Package_31bf3856ad364e35_x86__6.3.9600.16384 The program throws an error because the filenames are incorrect. Microsoft-Windows-NetFx48-Package~31bf3856ad364e35~x86~~6.3.9600.16384