It is not the script that provides support for current builds. It is mainly, the "ToolkitHelper.exe" application that is developed by MSMG. And only he who offers updates. Stay tuned for the support made available. In the main post, the builds supported for each version of Windows are described. Above these builds, you can test and report to us if it worked correctly for you along with the procedures used. But there is a simple method to have full support for new builds. Use a supported ISO and upgrade via WHD Base Line through "Toolkit". Then remove whatever you want. About this: I have to check if after a WHD update through the "Custom Toolkit", or not, change the Script "ImageBuild" variable for the newer version, if yes, it may interfere in the Components Removal. But with the flexibilization of this limitation that was in "ToolkitHelper.exe", I believe this is not a problem. Note: Problems found may be related to new Microsoft implementations. So we have to wait for MSMG. But do not assume when some update will be released. Eventually he comes with the surprise. The "Custom Toolkit", I leave free for the tests in any build, as MSMG released the latest toolkithelper.exe without limitation so we can test. But keep in mind that without limitation does not mean compatible. It's a bet, you can find problems.
Cleanup the Source Image using [Apply->Cleanup Source Images] menu. Note: Not recommended to use due to SFC bug with recent Latest Cumulative Updates (LCU). I'm confused by this step. Its not optional but it says not recommended. Should i use it on windows 11 Windows 11 v21H2 without any integrated update?
New VirtualCreate_ImageIndexEditions.zip 2022-03-08 (updated with 2022-03-08 @abbodi1406 "uup-converter-wimlib-78r") Download in my signature. Note: To work with Virtual Create, it is not necessary to extract the file. Just save it to the Toolkit folder.
Updated script: New Download, attached to the previous post. A launcher with option for the official version (directly from the author's GitHub) and an option for the custom version that is in the package. The version I customized, was aiming a bit of security. When you select to remove, a list appears. You choose what you want to remove. Multiple selection can be made. Tested for Windows 10. If you can, I would like it when someone tests in Windows 8.1 and Windows 11, inform me if the Host OS appears in the CMD window is correct as "W81" and "W11". Thank you guys! Download link: https://forums.mydigitallife.net/attachments/livesession_windowstoolbox-christitustech-zip.58614/
I get an issue with this Registry: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl] "EnableLogFile"=dword:00000000 When I integrate this .reg using MSMG Toolkit, when I make a clean install I get a nice blue screen. When not integrated, the install works fine. Is there a way to fix it? Tested in both, 10 and 11!
Just replace "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet" to "HKEY_LOCAL_MACHINE\TK_SYSTEM\ControlSet001" manually. It's become to: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\TK_SYSTEM\ControlSet001\Control\CrashControl] "EnableLogFile"=dword:00000000
He doesn't need to add the "TK_" in the original .reg file. Because if he wants to use it in a windows live session, it won't work. But it is crucial to change from "CurrentControlSet" to "ControlSet001". If not using from Toolkit 11.9 onwards. @ultimate_live If you are using Toolkit from 11.9 onwards, it should have converted correctly. If you are using an older version then 11.9, go into the bin folder for 12.0 and copy the corrected "ConvertReg.ps1" file into the folder for the Toolkit version you are using, then replace the older file. EDIT: Corrected the information, as of which version it was fixed.
I´m using latest Version 12.0. But I get blue screen while installing Windows 10 or Windows 11. If I don´t use it, the install works fine. Should I change to "ControlSet001" ?
Yes. Read this... https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-886#post-1633278 Note: Ignore "CurrentControlSet" as it is only used for OnLine (Live Windows). For OffLine images, just observe "ControlSet001". For both OnLine (Live Windows) and OffLine images "ControlSet001" works.
Si, I change the .reg from: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl] "EnableLogFile"=dword:00000000 to Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CrashControl] "EnableLogFile"=dword:00000000 and then adding to Toolkit and it will do the rest?
Has anyone here managed to stop Edge from re-downloading/updating itself if everything related to it is purged? WebView2 keeps being added/updated as well and a "empty" Edge install that fails on itself after a reboot.
Hi guys. Sorry for the intrusiveness, I wanted to clarify whether it is worth waiting for the official tool, just a month has passed since the developer appeared and he wrote that there will be a new tool soon. Thank you for your understanding and sorry
Yes, there will be an update. As I understood it, msmg wanted to test the latest CU that was released last Tuesday, to verify and spot any potential issues. Depending on his findings, he will update the tool in a few days. Cheers.
Yes, just that. If problems occur again, it is this registry entry that is causing you the problem. But I don't think so. Another thing... In case the problem occurs again. Take a shot of the error or write down the stopcode error.
I didn't really understand what your questions are. But I think, that you want to know if it is worth waiting? The least you could do is to read up on what has happened since you last joined the thread. It has not been a month. He was here on March 4th. But I believe he is not back from his land yet. He just came to make available some packs and new repository link. He talked about his personal life and is giving due attention to his family. The work here is honorable and freely available. We can only be patient and wait.