There is an "AutoUnattend - ReadMe.txt" file. In it you find info about customizing the file. It will not remove anything, it will only answer the questions from the installation.
Oh, I didn't know this option is located there, because placing it in Tools menu doesn't make any sense. This should be available during Applying & Saving changes to Source Image as final option for format output (WIM or ESD).
You can try. But I believe there are some more topics for this to work during the installation. It has been a long time since I made and left as complete as possible, made some reviews to remove unnecessary parts and to make specific autounattend.xml files for some Windows builds. It is up to you to test. Start the installation and see if you get to the selection of editions without any question. When you get it. Follow with the installation to see if the questions about User will be answered or not, and if the bypass will occur for parts of the telemetry options. The way I left, you only choose Edition and partitions. So after coffee, you'll already be on the logon screen. All related to Wim Files, for images that are not in service or after Save Source, is in this menu.
Yeah I know, but for "average Joe" that is using tool for the first time or doesn't have enough knowledge about Windows Imaging Formats, this is counter-intuitive for placing it in separate menu for use after saving changes to source image and de-mounting image. Most users hit "Apply" and next "Target > Make a DVD ISO Image" option without knowledge, that there is option to decrease final size of image in additional menu by converting it to ESD. For example, Nuhi added option in NTLite to select Image Format before finalizing entire process of saving changes to the image/creating ISO. Which makes more sense for end user. So option of selecting Windows Imaging Format (WIM or ESD) during "Apply & Save Changes to Source Images" menu or "Make a DVD ISO Image" menu is better. Image could be automatically converted to ESD after Applying & Save Changes to Source Image process + de-mount or before Making a DVD ISO Image process, if user selected ESD option. + There could be a descriptions in parentheses to indicate that ESD provides smaller size and is read only, WIM has bigger size and write & read availability.
In the old days this conversion was in another position. Yes, it is possible to put before Save Source, better option. Just one opinion of mine: I do not have this concern to decrease the size of the image, it only takes too long to close the image. I use 8GB or 16GB pendrive if I need it. But 4GB, no longer serves, nor for ESD format. Anyway...
Have fixed the issue with CU integration for Windows 11, its working with cab + psx format. Setting Sync : There's no package file to detect Settings Sync component, I was using one of the setting sync file to check or detect the component, since the MS had removed the specific file in Windows 11 and so it was not getting detected by the ToolKitHelper program, now have changed the detection method and it's working now.
A bit of a side question, @MSMG , for windows 10 image customization, is it possible to add a "hide cortana" and "hide search bar" options in the tweaks?
Hi @MSMG, You probably missed my post, is it possible to check the dx9x integration? Currently it is broken. Cheers.
I have uploaded a new DirectX9c pack based on abbodi1406 pack, do checkout the next version of Toolkit which is almost ready to be released.
@MSMG ye but that disables cortana as a whole, if I'm not mistaken. What I meant was "hide cortana button" which does the same thing as hiding taks view/search/news&interests.
As the TPK file was splited, the "%PackageIndex%" for "Directx9c_w11.tpk" x64 will remains equal to Windows 7, 8.1 and 10 that have both architectures? Or for Windows 11 will have to be corrected to "%PackageIndex%" equ "1"? Maybe we have to apply this correction. And even check other TPK packages that have "%PackageIndex%" to see if this fixes some integration incompatibility with Windows 11. from: Code: :: Setting Package Index and Architecture if "%ImageArchitecture%" equ "x86" ( set "PackageIndex=1" set "PackageArchitecture=x86" ) if "%ImageArchitecture%" equ "x64" ( set "PackageIndex=2" set "PackageArchitecture=amd64" ) to: Code: :: Setting Package Index and Architecture if "%ImageArchitecture%" equ "x86" ( set "PackageIndex=1" set "PackageArchitecture=x86" ) if /i "%ImageArchitecture%" equ "x64" ( if "%SelectedSourceOS%" neq "w11" set "PackageIndex=2" if "%SelectedSourceOS%" equ "w11" set "PackageIndex=1" set "PackageArchitecture=amd64" ) Or provisionally add to code block on label :IntDirectX9c if "%SelectedSourceOS%" equ "w11" set "PackageIndex=1" and not apply the previous suggestion.
I asked this, because according to the PackageIndex code for x64 will be set with the value 2. Since you add an empty index this avoids this problem. You had already spoken something about it earlier, I who had not understood right.
@MSMG, In the 3 labels below, :ExtractSourceStoreESD :ExtractSourceMCT :ExtractSourceESD This part below, in which the image capture occurs, it is performed, and then the capture folder is removed before any action is performed. Is it not used, or did not I understand the process? Code: :: Creating Temporary Boot and Install Images call :RemoveFolder "%Temp%\ESD" call :CreateFolder "%Temp%\ESD" call :CaptureImage "%InstallWim%", "%Temp%\ESD", "InstallWim", "InstallWim", "No" >nul call :RemoveFolder "%Temp%\ESD" Since this is a bootable image, should the last argument be "yes"? from: call :CaptureImage "%BootWim%", "%_TMP%\ESD", "BootWim", "BootWim", "No" >nul to: call :CaptureImage "%BootWim%", "%_TMP%\ESD", "BootWim", "BootWim", "Yes" >nul Note: This part is new to me. I'm entering a field that had not yet studied (image capture).