Yes. Here it is posted. Yes, that might be true. I cannot speak for him. But whenever we find a problem he answers and tries to correct it. We just have to inform with pertinent details. About this detail of the registry entries: these are many and, for windows 11, this was one that worked for the first 22000, then it stopped working. if "%HostBuild%" geq "21996" for /f "tokens=3 delims= " %%o in ('reg.exe query "HKLM\SYSTEM\CurrentControlSet\Control\MUI\Settings" /v "PreferredUILanguages" ^| findstr.exe /I "REG_ _SZ"') do (set "HostLanguage=%%o") Well-made criticisms are constructive and bring new perspectives. New ideas are born from there. I myself don't have space to do many tests, my HDs are full. I also enlist the help of the staff here. Who has the system with the right build installed, can check and bring feedback we always appreciate it.
I don't understand this at all. Why was I wrong? Was I wrong that it doesn't work properly? Thanks for your help.
@sergey130270 , I saw that you create and during the course of the tweaks code several values are being added to the variables. But after that you don't use these variables to modify the registry, checking if they are already disabled or even without checking, simply making the services registry entries disabled. This function is missing. I looked quickly through the phone. If the function exists maybe I didn't see it. About tasks I don't know how to disable it, I never did it when making the image. Only with post install scripts. I'm away from the PC at the moment.
@sergey130270 Scripting is fun, but you should stop doing things like we were in win98 days. Just install/deploy the image in a virtual machine or in a native vhdx (or in a separate partition, speaking about old school things). Boot the system and enter in audit mode. Then add / remove whatever you like, drivers/sw/settings/tasks/services/whatever. Once you are happy with the result, syspep the image , then capture it in a new install.wim, and replace it in the iso (if you need it) Then when you install/deploy your system it will be exactly as you tailored it, since the beginning. No more time wasted debugging blindly executed scripts, no more time wasted each time you install the system, no errors went undetected and so on. Optionally you can still use some old school scripts and /or xml, but they should be kept really minimal, like to set the computer name, pass the activation serial, set the default user and alike
but if you really lazy, use external ssd for 20$ you can get 120GB ssd + Cheap adapter from uncle ALI
We have to see what his reality is. I know how to do this but if I'm going to waste that time once a month on my machine, I think it's interesting to put into practice a clean installation. If it's for use on multiple machines this might make sense... And even then, a clean install with some post install details, using my alternative to SetupComplete, in which, it detects when the user has connected to the internet and offers a list to download many details through winget. That way I avoid using an ISO with many things integrated, which I will have to waste time updating again because Winget already brings many things in its latest versions. That is, I spend 45 min to make the ISO with wim image and 1 hour to install and get everything ready. But as I do in-place update, I lose the ISO time plus half an hour. And, if everything is ok, 5 min to clean up the previous installation. There are many methods, and they all fit at some point in each one's reality.
I was thinking. It doesn't make much sense to remove many components and leave windows update, it will certainly cause a bug when there is a big update. Correct me if I'm wrong.
@inTerActionVRI I wrote above that of course not. I don't want to drag this out any longer. but I always do what I always do, but version 13.2 has these bugs, even though it would be compatible with the disk image I'm using now. the script creator is gone. Now it's fashionable
I just gave a suggestion, then is up to you. You can even write a setup in assebmler, if you prefer, no one will be hurt.
Yest that's the current scenario for W10 (except 1507/1607). Just block WU then, when you mind say each 3/4/6 months redo the image and do an in place upgrade. Your system isn't going to melt if updates aren't done exactly each month.
Not sure if you are aware how forums works, but when you ask for help there, you are asking to any users over there. Whatever I regret having wasted my time, with an upleasant/ungrateful user like you. Have a nice day.
Here is the screenshot of your problem. I said to check the issues in my specific post. Follow the tips. Or find out for yourself. Don't ask for help if you know everything. When you ask for help with a problem and we offer to help, and if you try and it doesn't work, just let us know that the problem still remains, it hasn't been resolved. What I have offered is about the resolution of this particular problem. If someone still wants to help you, Ok! I don't type anything else for you and make the above @acer-5100 words as if they were mine for you. About the author @MSMG, he is very busy and at some times of the year he is absent. He has already explained this countless times.