Hey, really appreciate the response, Now to answer your questions, I am using the default powershell version 5.1 and have also tried PowerShell 7.xx, and have been trying this out since toolkit version 12.xx on Windows 10 22H2 as well as Windows 11 22H2 and have been encountering the similar issue , I haven't used the "Force .NET programs to use newest .NET Framework" tweak neither have I integrated .NETv3.5 or .NET v5+ and no , both of the registry entries that you mentioned are missing in the OS
Hey, appreciate the reply, Sadly as I mentioned , the github projects that I use are pre-compiled and do not actually open a powershell window, they are integrated executables and do not have an option to change the parser by me and honestly, I don't have the knowledge necessary for it. And as I mentioned before , I keep the networking components sections untouched and also leave IE11 and edge legacy just to prevent the parsing issues but it still doesn't fix the issue apparently for me ..
So you are using closed source programs that you are having issues with? Can you not debug it with the maintainer? It would make more sense, since they know what they are doing there. Are these projects available for the public? I (or we) could give it a try, since the systems in use should be similar to yours. Also, are you sure you don't have anything for .NET v4 Framework in the Registry? By default it should look like this: gci "HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full Name Property ---- -------- 1033 CBS : 1 Install : 1 Release : 528372 Servicing : 0 TargetVersion : 4.0.0 Version : 4.8.04084 This is from 19044.1288 deployment where I removed pretty much everything that the Toolkit allowed me to. As you may know, PowerShell is heavily based on the .NET "ecosystem", and this is where the error that you showed was originating from as well, which by default is not an issue. If you do not have .NET available, this could be a problem, however, the Toolkit should not remove it.
Feel free to share the ISO you have created. Based on what you described, WinToolkit could have been the issue, but if you are not even using it, then most be something else. I am working with VirtualBox, so testing will not be a problem in any way. Just so you know, even though the Toolkit will let you work with any .iso pretty much, only certain build numbers are supported to create a stable system apparently. I thought I was using a supported version myself, but it turned out to be a disaster after the component removal - I would not be surprised if this would be the case for you as well. Seems to be a hot topic in recent days.
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 ?