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.
You can use The toolk menu to make that work. The resulted Install.wim cannot be serviced after that. Only if you make it in steps like. Mount only 7 x86 images, service that save. Then mount only 7 x64. Service that, save. Than w10 x86, than w10 x64. But as you said you dont make these changes just use the bellow path to assemble your AIO ISO. Use Tools --> WIM Manager --> Export You can use an tool from abbodi1406 "here" to join x86 with x64 and making a multiarch W7 ISO then a multiarch W10 ISO. Before use the above Export tool.
Your comments are welcome and appreciated by many. 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. By this I mean how Toolkit could have implementation for a version-based component removal that would support different patch versions between .1 and the latest, everything that has already been tested at some point. It is not about adding new features for us how to manage stuff using Toolkit, it should be for the Toolkit internal behavior on how to achieve this (there was once an .xml file uploaded along with the .exe, so that's why I thought managing this "version control" could be done in that format, but basically all it would need is a lookup data/mini database stored in any way.) With the current way, basically experience, knowledge, but most importantly support for something that was already put a lot of effort into is lost. Sorry, I am just still shocked that some intermediate version, that was working before, is not working now. For me it is not much of a problem, the Toolkit does almost exactly what I expect from it when it comes to Windows 10 (I only have this MixedReality/Tsprint issue open), which is almost exactly what I need. 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. Please go for it, because it seems that more and more people are getting confused about what the Toolkit is supposed to do. It would be a warning with a Y/N answer, where Y would let you proceed. Make sure to put it in red color or something (which should be the case for all errors), but I am not sure by hart what options are there for line coloring when it comes to pure batch files. I just had a quick look and it looks like the image version is extracted before the mounting takes place: ------------------------------------------------------------------------------- ####Source Image Information################################################### ------------------------------------------------------------------------------- Image : Install.wim Image Index No : 1,2 Image Architecture : x64 Image Version : 10.0.19044 Image Service Pack Build : 1288 Image Service Pack Level : 0 Image Build : 19044 Image Default Language : en-US ------------------------------------------------------------------------------- ####Mounting Source Images##################################################### ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- Mounting [Boot.wim, Index : 1] Image at <\Mount\Boot\1>... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.25370.1 Mounting image [==========================100.0%==========================] The operation completed successfully. Additionally, mostly in case of re-using images, it would nice if the Toolkit could detect which components are already not present, e.g. show them with "-" in the component removal menus when loading the list. From technical point of view this can be achieved, but not idea how much effort it would take
Well, what makes my iso a broken iso ? Because I integrated the local account patch just to be able to stay offline till I install all my drivers for the laptop and then afterwards I connect to the internet . I know the part that you trying to explain , that system applications will be re-installed reagrdless of me removing them from the iso and only the UWP apps will be gone for good (past the Windows 11 days , I too was a Windows 10 diehard but Microsoft declaring that Windows 10 will soon stop recieving updates and eventually developers will stop supporting it , I upgraded to Windows 11 (not to mention my Laptop came with a Win11 Home Key so it made all the more sense to stick with Win11). Considering you mention updates might be an issue , should I create an iso with similar settings but this time also remove Windows Update as well , because I haven't basically ever removed Windows Update from my builds just because some updates for Firmware updates are pushed through Windows Updates only and are not provided on Manifacturer's website but I think I am willing have that trade-off in exchange for a working Windows image .. considering Wnidows Update being gone should I work properly ?
Understood. Yes, yes. Too much things in mind. Only need to extract the ISO to obtain install.wim data.
This work is already done (not implemented yet), but it is not interesting to reuse Custom images. This makes the possibility of errors unpredictable. I went through this experience. It is better, whenever there is any problem, to start the image service from scratch. Since extracting the untouched ISO. By the way... The ISOs created through UUPdump are just an assembly of parts with direct MS downloads. Can we say, in quotes, that they are untouched ISOs? No. Because they are not ISOs originated by MS, only the parts are. However, they are certainly not custom ISOs.
Okay, I see you got a little confused over my reply. You broke the system by removing components for which the Toolkit offered options for in Remove Windows Components menus 1-7 ([1] Internet, [2] Multimedia, [3] Network [4] Privacy, [5] Remoting, [6] System, [7] System Apps). If you use pretty much anything of this (at least for an unsupported version), it will break the system by not letting LCUs installed either from .msu files by yourself, or using the Windows Update option from the system. It is safe to remove anything from [8] Windows Apps. You do not want to have a system which you cannot install updates to. This also means preferably keeping Windows Update component, but even without it you should be able to apply updates with a bit more effort. Again: the point is if that system cannot be updated (which is key when it comes to security), it is only a matter of time till it will become a problem to you (you lose or get sensitive data leaked, etc.). If you are certain you will not be impacted by this, you can do whatever you like, as there should not be any consequences. When the updates add back what you removed it only means you did put work into their removal for nothing, but at least your system will be updated.
I have just loaded up a butchered .iso and all the components are listed with "+". Are you sure this is already implemented? Or perhaps I failed to describe properly what I was looking for. If nothing else, it could be looked up at least what was touched on that specific iso.
Thanks for instant reply. I managed to combine x86 and x64 install.wim with WinAIO maker professional. if I combine Windows 7 x86/x64 or windows 10 x86/x64 this works well. but if I combine Windows 7 x86/64 & windows 10 x86/x64 together, during installation it ends with some error when windows edition screen appears.
OK, got it , but the thing is , security for me is the least of the concerns in the OS , what I was aiming for is a fully functional image rather than a secure one with defender and other stuff , So not having updates by a security stand point , I personally wouldn't really prioritize , since that wasn't the end goal , the end goal was for a very low resource , functional build with security being the least of my concerns . Updates to me are only useful for firmware updates for my device from time to time as well the drivers for some obscure devices that Windows has . And many of the items that I remove from the System tab are ones I don't use and don't want running in the background either and having updates removed or crashed would prevent them from coming back . For me , that is a feature since I (other than the issue at hand) have not encountered a single other issue with the ISO's I create instead use them on some very old hardware to give them that extra lil bit of RAM to run programs better. The thing that you mentioned about Win version 22621.525 not being supported by MSMG Toolkit though I understand is being a problem .. so where can I find the supported ISO's ? Since I generally got my ISO's straight from Microsoft's official Windows 11 ISO download page and 22621.525 is the version they have up right now .. so maybe you can point me to one of the supported ISO's download ?
Well, if you do not need to care about updates, the image you created is usable. Generally speaking I would recommend "downgrading" to Windows 10, if you have the possibility for it. For Windows 11 this is as good as it gets, I suppose, but I don't think it has anything better to offer than Windows 10. I don't know where to get the supported iso-s from, I would probably google it. There is a tool called Fido (PowerShell-based), but I cannot use it as the MS servers that it is using are not accessible from certain networks, so I cannot tell if it would work, but my guess is it would let you download official releases and not Insider releases. But again, you don't actually need it if you don't care to update the system. Keep the image that you created, and try to perform the steps I suggested, or if it is not an option to follow it exactly, do an offline installation in another way, copy the files and try if they work as soon as you go online. Based on the tests I performed, this version that you created is good enough to use those applications.
Actually , I'd love to use Windows 10 over 11 since neither do I like the aesthetics of Windows 11 nor the extra gimmicks that cost performance, I was content with the minimalism of Windows 10 but as I said , Windows 10 is out of support by Microsoft soon and developers will deprecate it as well and also that my Laptop contains a Windows 11 Home Product Key and also drivers for my PC and Laptop are created mostly for Windows 11 ( I know that they can work on each other but they are far from being seamless) so I am kinda coaxed into using this OS .. I actually have a Windows 10 image as well with similar customization .. could you try it since you are more familiar with Win 10. I created the Win 10 iso for an older PC which was seriously deficient of resources it could provide the OS .. if you could check it ,please let me know .. I understand that this might be crossing the lines on how much I can ask of you so feel free to refuse if you can't , you have already helped quite a lot and I have gained much throughout the conversation ..
Any idea what are dependencies for microsoft store on LTSC version? Without debloating, no issue to use store script afterwards but when i leave components for store from the description and debloat others store wont open afterwards.