These days I use much more intuitive - and simpler - scripts. E.g. https://forums.mydigitallife.net/th...1803-1903-19h2-1909-20h1-and-ltsc-2019.80038/ For - NORMAL - users it is much more simple - not complicated - and in effect - you can get the same thing - I think.
It has recently been moved. My script started here with authorization from MSMG. There are details that serve both to innovate the Toolkit and to innovate IMCK. So I'll keep leaving my posts that are pertinent to the Toolkit here. When doubts or suggestions are brought here, they will be answered here. When they are taken there, they will be answered there. Everyone contributes one idea or another and the MSMG, in its time, brings news with these contributions. It's no different with me. And, as he is, at the moment, much more busy than I am, nothing like leaving some already worked things available to him. Someone who is looking for something here in the topic, can search and put his name to get the specific answers. You don't need to observe my activities, ignore my future answers. To understand it, people have to download, read how the main thing works. And, when it is something technical, leave it to those who will take advantage of the subject. I started without understanding about scripting, MSMG taught me a lot and I went after learning. I ended up teaching a few things to other people, and the learning they had also generated great ideas and productions on their part that brought me more knowledge. It is a double way path. In teaching, learning takes place. In learning, questioning generates knowledge for the teacher.
is there a way to do it manually with the boot.wim file to add the .reg in? detailed instructions please
The way I see it is that creating a modified image is in itself something a normal user does not even know exists. If a normal user had access to a 100% user friendly tool, they would likely make a broken image never understanding why what they removed was a problem. When I came to this forum I had a lot of experience in IT but had never once modified an install image. I was searching for a tool that could make Windows 10 be more like Windows 7 and ended up here. I think I started using the toolkit somewhere around 1703 or 1709. I've learned a lot since then and rarely install out of the box Windows 10/11 anymore.
Man, one way for you is to use rufus which is already integrated into boot.wim and send the image to the pendrive. But if you take a look here on the forum, even the friend @zbigniew59 put a link that leads to this @Enthousiast topic Remove Secure Boot And TPM Requirements From Windows 11
I recommend you to continue using: https://forums.mydigitallife.net/th...1803-1903-19h2-1909-20h1-and-ltsc-2019.80038/ and leave us here alone. Thank you for the kindness
Have you tried on another partition. Check how many Gb you have before starting the image servicing. It has to be about 30gb to be at the limit. But also, I suspect that you have to run a chkdsk c: /X /F or chkdsk c: /X /R /F
It is correct. I'm migrating from 19044 to 220000 and on to 22621. I'm confirming the integrity of my ISOs to perform an inplace update. And I think I'm going to start experiencing the problems that people are experiencing in w11. What ISO are you using? When you are doing the conversion do you close the File Explorer? I've had read/write problems simply from being open in the toolkit folder. Then the message appears that the file being serviced on is being used in another process.
19045.2311. My File Explorer is closed. Yes, but in both screenshots, I also get the message Failed to decompress data and The WIN contains invalid compressed data.
Well, I for one am certainly highly interested. Much of the stuff is too complicated for me too, but that just makes it more interesting. No one would accuse me of being "highly specialized" Don't always get answers to my questions, but I usually find a solution in the end.
invalid compressed data - may be caused by a read failure because it is being used in another process. It could also be due to data corruption. If you have already downloaded the ISO again, this possibility can be ruled out. Maybe Windows Defender up and running checking the files being worked on. When we forget anti-malware enabled... It's a disgrace. It's always a waste of time.
Yes, already downloaded the ISO again, so this possibility can be ruled out. My Windows Defender has been removed completely..!! I don't use third-party antivirus..!! I don't understand what's happen.