Thank you so much ! Here's the link to the image but then again even though I have used it myself multiple times (heck I am using the image right now to type this message)please keep your caution , testing any random iso is sketchy as your already know , and I dont want to mess your PC up just to help a random person on the internet .. and also please ignore my goofy naming for the image .. : (link removed due to moderation rules)
Hey , I actually have been using Chris' Winutil since day one and yeah sadly , not even this script can run properly right now .. even though I already use chocolatey it still does not matter , running your script just gets stuck after checking the initial few lines , then just times out , shows the invoke-webrequest error for a mil-second and then the cmd windows just closes
I managed to download it. You can remove the link from your other post if it is not allowed to share such information.
The image you were using is the same I was: Windows 11 22H2 22621.525 Apparently it is not supported by the Toolkit, even though the latest version is. However, both apps seem to work for me. Everything works just like in case for Windows 10. I installed Home Edition by the way. Did you do anything after installing the system? The error most be coming from post-installation activities. Did you try it on a live machine on virtualized system?
To make the new SPbuild work. Just service supported ISO and add the updates tru Toolkit then remove components. Just follow the Menus and the options order. I just recomend one thing. Do not integrate the netfx35 until ending all things to Custustomize Menu, due to pending file creation. If you want to use the Dism CleanUp, do this using the Apply Menu --> option 1 Then, only then, you can integrate the Netfx35 and finalize your ISO. I don't know if it's feasible to use the /PreventPending switch to solve this problem in netfx35 integration. Only @MSMG could tell us something about this.
Supposedly integration of .Net Framework 3.5 was never a topic to go by, I just wanted to cover the areas where the problem could originate from in this particular case. And I don't understand what is wrong with Windows 11 22H2 22621.525, which seems to be an official release. It's from September, is H2 not released at that time? There should not be anything like 22621.1 in such case as an official release, but to be fair, I am not keeping up on Windows 11 release strategies. I was specifically looking for 22H2 image to acquire for this one time I had to, and seems like I am not the only one who stumbled upon it. Again, if I were to support versions, I would do something like this as an .XML control (not particularly a fan, would probably go for JSON, but as far as I understand XML data is already used for the Toolkit): <BulildNumber>22621</BulildNumber> <MinimumPatchVersion>1</MinimumPatchVersion> <MaximumPatchVersion>525</MaximumPatchVersion> <Component>component_name</Component> <ToolkitActionList>steps to perform (in the form of child nodes maybe)</ToolkitActionList> And that's it - apologies for the primitive representation, it should still serve a point. If anything that does not fall between minimum and maximum version, that specific action is not performed for the given version. I doubt that there are key changes for the components that are there since .1 version. You would keep extending the maximum version number for as long the same steps are applicable. And if you introduce a new component for removal, you would go as far back as possible to see if that works (preferably the initial release), and that should imply everything inbetween works. If something small is introduced along the way (such as an additional Registry path), you add it with a testing (if exists, do...) step to perform. This is what I would try to do at least, and this should keep the size and performance under control, however, I am far from being called a developer myself.
Wait , so both the apps work on my ISO ? That's weird because as soon as I install the windows nowadays , i first check running these apps right after installing the drivers , meaning almost no post installation customization takes place .. and I have tried the image on both a virtual machine and live on my PC and both have the issue .. and about the image version , I thought this is the latest version available , I always download the ISO's straight from Microsoft , isn't it the latest version out there ?
Basically you are expected to integrate the latest patch that was added by the Toolkit to be supported. Either that, or you would need to use the initial build, .1 version, which I am sure should be an Insider release as they switch to annual release, and H2 used to be released around September, so what you have should be the first official release for the public. The issue is that from development point of view tested things will be discarded for earlier versions supported, like you cannot use the newest toolkit for a patch that was used 2 versions ago. The real issue seems to be in our case (Windows 11 22H2 22621.525), that no matter what you remove, updating the system will not work. I think this is hardly acceptable. No need to integrate .NET 3.5, it is for much older applications, which strictly depend on it. I only asked it because if it was done wrongly, it could be influencing the way PowerShell works. You are doing something shady, because I could use the applications Either way, this iso that you created is broken (cannot be updated as I just mentioned), so do not use it for live systems.
Well , the problem with updating is actually nothing new for me apparently , since that has happened since day 1 of me using MSMG Toolkit , and I thought Windows Update breaking was normal when using a custom iso with a lot of packages removed.. well what should I do ? Any suggestion ? And also is there an updated iso which is supported by MSMG ? UUP Dumps ? Because I happen to always download all the patches regardless of me using them and paste them in packs folder after extracting them ( had to do this always cause whenever I started the removal process it would get stuck on some package with an error that did not make a lot of sense to me but worked enough to show which package it got stuck on) so which patch is this ?
One thing I can say is that these days not being able to update the system is just unacceptable. Also, since I have very little experience with Windows 11 (this is all I had so far, luckily), I am not even sure if the removed components would be re-added by the updates, just like in case of Windows 10. And if they would be added back, you have worked for pretty much nothing - unfortunately. Try again your .iso maybe, because both Home and Pro Editions work just fine on my end for these applications that you were facing issues with. I will let others answer your questions for Windows 11 as I will not be able to do so myself.
Well , in Windows 11 other than edge I dont think any other thing gets re-installed via updates so I think that isn't too bad but still and about the updates you speak of , could you please explain ? I didn't quite get it , do you mention windows updates ? Or do you mention image version updates not being compatible with newer version or not being compatible with MSMG Toolkit ? And the last question, is there something you made out from the ISO that could tell why the applications could not work for me on my live installation ? And also thank you so much for the prompt replies ..
No problem. I post it just for people know some good practice when you want to integrate netfx35. I even quote anyone in that message. It is not about this particularly Official available SBbuild by MS. This is a matter of MSMG choice. I believe it is to maintain the performance of ToolkiHelper. Yes it is an Insider. This is the basis for any of the SPbuilds even .525. Even for 22631.xxxx. That's right. Not only 22621. From 22622 to 22624 and 22631. All keep the base 22621.1. We usually download from UUPdump without integrating updates into the ISO generated there. So we get an ISO with SPbuild .1. I partially followed you in your message. But core windows is almost all XMLs. There are few new things that are configured with json. In the toolkit, only Unattended is with xml, you can make a json create this XML, but I think it will duplicate the code. Perhaps I lack information at the moment. But considering a previous suggestion (here), I had already thought of a way to put a Warning of SPbuild not supported by ToolkitHelper. As far as I know. This can only be done after the mounting procedure. So, to get the Image data, there is a certain amount of time lost. It is better for the user to learn what the tool supports and use according to it's current design. But still, if the image is not supported and you get this warning right at the beginning, it prevents you from continuing the work. But work on such an image can be allowed if one does not want to remove components. Perhaps such a person does not exist, heheheh. But we never know. Only if you want it. But my recommendation is only in this xase you want to integrate the netfx35.
Yes, I was focusing on Windows Updates. As for the Toolkit, it should just support everything that it did support already at some point, so it would not matter where you would start from. I have a lot of experience with Windows 10, so I will explain it from that point of view: whenever a Windows Update (file) has an update for the packages (components) that you have removed, the update will force back the components on the system. They are built up like this in recent Windows versions (I think starting from 19041) and there is no preventive action for that. You may not notice that Internet Explorer is added back for instance, but the subfolder in ProgramFiles will be there, and the same goes pretty much for everything else, included System Apps. Edge is just something that you will notice straight away. Basically you might as well just use an untouched installer if the removed stuff will be forced back as soon as they are part on an update that you intend to install. The only things that will stay away from the system are pretty much the non-system Apps (the ones that you see in start menu when you open it for a default installation), but even that works only because of the Registry tweaks from that vendor side that they have implemented for them. I was only able to get a stable system, when I only used Remove [8] Windows Apps from the Toolkit, it did not matter how carefully I tried to remove components. For other .isos it could work better, but I had the same that you have. There was absolutely no hint for what could have been wrong for you when trying to use these applications. I did try Windows Update whether it would be the same for you as well. Basically the installation of the LCU fails (and the reason for that is missing components - which you removed), .NET Framework and smaller system patches will still be installed. Here are the exact steps that I was using: - I am using VirtualBox 7.0.9 build 157775, which is an unreleased test version (it was published last week, and I use this because I was having issues with Windows 11 when using the extended features provided by Guest Additions - basically the system froze after a couple of minutes, probably due to driver issues) - I installed your system (Home Edition first, next time Pro Edition) without network connection - Once the installation was done, I installed Guest Additions (test 7.0.9 build 157748) for VirtualBox to be able to resize the window for the system, do copy-paste from memory between my and that system, and also access the shared folders, where I had the files for testing. - After rebooting from the installation for the above, copied the files (Install_Auto.bat, Optimizer-15.3.exe), went online, and immediately started them - and everything was working as expected If you were trying to perform the system installation while being online, I could imagine that some updates were being tried to be installed, which could have caused the problem that you were facing. And if it is true, the sole reason for this is that you created a broken system - you would not be having an issue with an untouched .iso, I am certain of that.
I make my new ISOs every month and have doin In-Place Update. Never returning removed components. There are an use tha repport this double the NTUSER.dat. I dont know how to check this dupplication. But I never had any problems with it.