Yes, maybe your chipset needs driver for working with W11. But if untouched ISO installs on your machine, than it is some issue with boot.wim after updates integration. Also don't use this option: Code: [2] Integrate -> [4] Windows Updates -> [3] Integrate Windows Setup Media Updates This "[3] Integrate Windows Setup Media Updates" changes boot.wim. I had fixed some problems here in some previous version of IMCK. But I changed a lot of things. I had made these changes available in the versions of Toolkit.cmd that I made available in february. But MSMG did not add them in the May version. I believe it was due to lack of time.
No, it is not yet supported for updates integration to 24H2 nor Component Removal via ToolkitHelper methods. And some other minor things. But you can use it for that and almost everything else.
MayBe your Issue are the "Dynamic Updates" . . . this updates containe files they not realy for the Wim´s but more for whatever Install medium direct. Open "Dynamic Updates" eq: KB5043353 with Archive Program and you will see files they should go into the Sources Folder of eq: a Install iso . For normal the Files should be moved by MSMGtool by Update integration Process but if after Updating a Wim only the Wim is Copyed to Install Medium thats dont have Updated Files in iso Sources Folder then there is missing Driver Issu ! MayBe also normal Drivers can be missed but thats is to known if the Present hardware is known ?
I'm going to provide a new temporary update for Toolkit.cmd. But I'm also out of time and I can't even keep up with releasing updates for my tool, hehehehe.
for people who are using lists to remove apps with the toolkit using DISM those are new packages in the 26100 build you can add to the RemoveAppsList MSTeams Microsoft.OutlookForWindows Microsoft.Windows.DevHome MicrosoftWindows.CrossDevice other packages are the same as previous build
ok, 24h2 question if you will never install updates, will component removal work on this build? another question does dism package removal lieve traces behind? compared to the toolkit way? last question, I promis if i remove packages via toolkit helper, then remove packages via dism, will this be ok? not dism then toolkit helper? thank you
Only, for DISM removal methods. In the provisional updated version of "Toolkit.cmd" that I will make available, I will allow the use of removal via ToolkitHelper. And update the update integration mechanism to 24H2. I don't know how to answer that. What I do know is that ToolkiHelper performs a safe removal so as not to interfere with the functioning of other components. But even so, it is not free of problems. Example: Removing Edge breaks the File Explorer file search. This way there are no problems, because if ToolkitHelper removes something, DISM will no longer find it. So whatever ToolkitHelper kept for some reason (to preserve functionality, for example) will remain safe. In my tests everything has always worked well, within my needs. But many people want to remove everything aggressively... So, there is always room for testing.
isn't dism removal safer than toolkithelper i've tried toolkithelper before when the version is not supproted it break the windows setup, otherwise it's fine
Windows Setup is not removable with DISM. These are just files that are around boot.wim and install.wim (i.e., they are the files that make up the ISO along with boot.wim and install.wim). But from what you said, you know this. There is a removal option called Windows Setup. Did you remove Windows Setup? If so, which build did you test it on, in which you had this problem? I mentioned something about problems with the Windows installer, a few posts above. But related to update integration problems. In short, there is always room for testing. There are many variables to consider and they vary depending on the user. Both are safe to use. The only problem is the limitation that MSMG places on ToolkitHelper. There are specific builds that are supported. So when ToolkitHelper eventually falls behind MS's frenetic release of updates, I can only leave Toolkit.cmd free to use ToolkitHelper in any build. But we know that there may be problems since the new 24H2, currently are not officially supported by ToolkitHelper.exe. To update DISM, simply install the recent ADK and place it in the Toolkit bin folder.
i didn't mean break windows setup literally, i mean the installation of windows doesn't go through, you start setup normally, but in the end you don't get to the desktop, after a couple of restarts it doesn't boot and it shows some kind of a bsod screen much like boot error or i don't remember exactly, but removing windows components with toolkithelper when that windows build is not supported always breaks everything up, and never works, so until the new builds are supported by toolkithelper, better use dism to remove what you want, that's my conclusion
I see. But MSMG made some components available for removal that can cause errors like this in any build. These are components that need to be replaced, such as the start menu itself. Do you remember if you removed any of the components below, explained by MSMG? Try creating a new ISO, keeping these components.
no i never remove such things, i'm not obsessed with stripping windows from everything like some people do, i only care about removing telemetry stuff, CEIP, bloatware apps like news, teams, onedrive, skype etc, and some things that aren't needed like some network components such as OpenSSH, Offline Files, Assigned Access, Multi Point Connector, i also used to delete the two oobe components so i get a quicker setup process, OOBENetworkCaptivePortal and OOBENetworkConnectionFlow, and also ContentDeliveryManager to stop promoted apps from getting installed
Yes, I will provide an update. And I will enable the possibility of using ToolkitHelper to remove components for 24H2. I have already performed tests and the resulting ISOs are working well. Including Windows Update is working. Repeating, in other words, something I always say: "working well depends on the combination of components you remove". It is necessary to read the Descriptions to avoid problems. On Saturday I released IMCK 13.7. Now, focus on Toolkit.cmd to make it compatible with 24H2, transferring some things that are already ready in IMCK.
Possible bug on MSMG 13.7: After applying: Apply Tweaks->Disable Windows 11 Hardware Requirements (even if that's the only thing applied on "Win11_24H2_English_x64.iso") upgrade installation (setup.exe) from within already installed (pre-24h2) windows fails with the following message: Setup has encountered a critical error. Sorry we're having trouble determining if your PC can run Windows 11. Please close Setup and try again. Error code: 0x80888002 - 0x40008
Open Toolkit.cmd and update the image service build under Code: :: Check whether the selected Source OS is compatible with ToolKit's Custom Component Remover Or just set IsCustomRemovalBuild=Yes. It's been working fine since 24H2 1591 for me by doing this.
That's not all. The menu is still unusable. But it allows removal via the ToolkitHelper list. This has been solved in the new version of "Toolkit.cmd" (not yet released). This problem is also something that has already been resolved in IMCK. And it has also been resolved in the "Toolkit.cmd" that I am preparing. All that's left is to finish implementing the new algorithm for integrating Updates for 24H2. I want to change Toolkit.cmd as little as possible so that @MSMG only needs to continue when he comes back. I have many changes related to the automations made in IMCK that I need to revert in Toolkit.cmd, due to the Bypass Hardware Requirements that in IMCK is controlled by an option in a configuration file for applications to occur at the appropriate times such as (Integration of Updates, Tweaks and AutoUnattend file) and in Toolkit is applied only via Tweak. For those just arriving, I used to maintain a version, with MSMG's permission, called "Custom Toolkit" here in his own Thread. This version just got a different name "IMCK" and a new thread, especially for it due to the need to separate the places for providing support. As the links are available in my signature. EDIT: Many may have doubts about how things will happen when using a Build 24H2. Firstly the unsupported build message may appear. On "MSMG Toolkit" it is the official supported build for the latest "ToolkitHelper.exe" version. In IMCK I suppressed this message for all "BuildNumber.1" only. But that was a small code mistake on my part, after all, the current "ToolkitHelper.exe" when it comes to base builds (read: the ".1" builds), only supports up to 22631.1. I will fix this in the next IMCK (this does not affect the functionality), but I will already have this fixed in the "Toolkit.cmd" that I will make available here in the next few weeks. But that was a small code mistake on my part, after all the current ToolkitHelper.exe only supports base build 22631.1. I will fix this in the next IMCK (this does not affect functionality), but I will already have this fixed in the "Toolkit.cmd" that I will make available here in the next few weeks. Follow the rules of Toolkit. And integrate update during IMCK use. The IMCK has a Updates downloader to help you to get the updates from UUPdump. Just use an UUPdump image without integrated updates. It will generates the 26100.1 build that is working by all my tests till this moment.