That's not what we were talking about. We were talking about a full-fledged image tool, and there are 131 pages of advice on what to do and how best to do it. Maybe someone will be interested in this, but I'm not interested.
how will freddie-o script help with Code: bendeyar said: ↑ I tested the script ''24H2_GamerOS_v.6.5.0''. The operations were performed without any problems. I tested the created iso file on a virtual machine and it was installed successfully. It looks like you have some problem. There is a small problem. It does not download updates. Whether it is from the script or Windows I do not know. ???
The problem is not in the script or in the image it received. Because everything works for me and everything is updated without any questions. It is not known what he did with this reflection and then in the image, in addition to the install.wim file, there are a lot of components that affect the installation of the system and its normal operation.
The problem is on my side, for which I apologize. As I was in a hurry to test the script. I just got some commands mixed up. By the way. I only use the script of ''SunLion''
Good afternoon everyone! I'm splitting the script into two, one SLIM and one DEFAULT. I'm having trouble with Windows Installer. Some apps that use Windows Installer are very slow to install. I still don't know what's causing this. I'm attaching a screenshot of the VisualCppRedist installation from abbodi, which displays the message "preparing to install...". This takes about 3 to 5 minutes to unlock and complete the installation. If anyone has any helpful information, I'd be very grateful.
That's right, in your case, that's how it should be. If you remove all .cmd files from the $OEM$ file, the full installation will take about 5 minutes. This is because these files are executed at the final stage of OS installation. I once tried adding a .cmd file for the automatic installation of previously saved drivers. In that case, the installation took me about 10 minutes. That's why I do this operation manually, after the OS has been fully installed. That's why I leave a minimum of .cmd files in the $OEM$ folder, only those that I really need. That's why, for me personally, the OS installation takes about 5 minutes. I also use your script and don't experience any similar problems. This is because, regardless of how the install.wim image is processed, it will not affect the OS installation time. Of course, this is assuming that the install.wim image has not been corrupted by the script itself.
===================== 24H2_Integrator_12.5 ===================== - Updated the all.txt file (26100.4652 version) - The script was split into two: - 24H2_CreateDefault_12.5.cmd - 24H2_CreateSlim_12.5.cmd - Several modifications were made to the scripts for better functionality. - In the Default script, the user can choose to enable or disable some options. - Some apps and tools are not installed correctly during installation, so I chose to add WPI24H2 to the package, which contains some essential apps and tools for installation after the desktop opens. It's up to the user to install it or not. To do so, simply leave it as is (selected) or uncheck what you don't want to install. Or, close WPI and don't install anything. Please read the Changelog.txt and README.txt files before using the script. https://forums.mydigitallife.net/th...ic-legacy-windows.86552/page-120#post-1872013 Enjoy!
Just to share my thoughts on this. Two factors were interfering with the Windows Installer app installation process. 1 - The lack of DirectX installation or integration 2 - The application of the "Delete SystemApps with telemetry from InboxApplications to prevent them from getting deployed" tweak, which modifies Client.AIX, Client.CBS, and Client.CoreAI. So I added DirectX integration and removed the above tweak from the script, and everything worked fine again. Thanks for your help.
My test of the last 24H2_Integrator_12.5 script, slim version, went through on VM. no issue. on start button, I have seen apps: Copilot Store Xbox Linkedin , , , is this normal? (given slim version should remove them). So, this is a simple jump from 24H2_Integrator_10.19 to 24H2_Integrator_12.5?
Well, I don't know if integrating DirectX9c into the image at this stage will prevent the Resetbase command from being executed due to deferred operations. And what's the point of that if DirectX is installed from the Update Center immediately after installing the OS ?