We do not share ISOs. The tool is for you to create your own. The staff has shared some very long removal lists here. However, everyone has their own preferences. The Presets "Looks Like Windows 7", "Lite" and "Xtreme Lite" available at CustomToolkit are the closest to what I used to do (which were much more feature-breaking, heheheh). Through there you can make your list and use it whenever you need it through list removal. You select a Preset and then go to the selection menu and read what has been marked with the - sign (for removal). Check or uncheck what you want, but read the Notes that appear if there are any restrictions. Then you decide what stays and what goes to limbo. Check the option "Create a File List <...> with your Choices". You can select "Start Removing Windows Components" and the list will be created, and return to the Menu to make changes. I will leave you with a list of what I consider important components to keep in an iso made for people you don't know. This way, the system will not let you down with Work and gaming. There are some components that are possible to remove for people with more computer skills (GetHelp, Getstarted, etc...). But what I mean is that beyond this list you can remove everything. Many people remove much more than that. I don't recommend it. Spoiler: important components retaining list EdgeChromium InternetExplorer GameExplorer SnippingTool SpeechRecognition WindowsMediaPlayer WinSAT WindowsTIFFIFilter OfflineFiles OpenSSH RemoteDesktopClient RemoteDifferentialCompression SimpleTCPIPServices TelnetClient TFTPClient AssignedAccess FaceRecognition KernelDebugging LocationService PicturePassword PinEnrollment WindowsErrorReporting HomeGroup MultiPointConnector RemoteAssistance RemoteDesktopServer RemoteRegistry WorkFoldersClient Calculator DeviceLockdown EaseOfAccessThemes EasyTransfer FileHistory ManualSetup Notepad ProjFS SecurityCenter StepsRecorder StorageSpaces SystemRestore WindowsBackup WindowsFirewall WindowsSubsystemForLinux AccountsControl AddSuggestedFoldersToLibraryDialog AppResolverUX AssignedAccessLockApp AADBrokerPlugin CallingShellApp CBSPreview CapturePicker ContentDeliveryManager CredDialogHost Edge EdgeDevToolsClient WindowsReaderPDF ECApp FileExplorer FilePicker LockApp XGpuEjectDialog NcsiUwpApp OOBENetworkCaptivePortal OOBENetworkConnectionFlow ParentalControls PinningConfirmationDialog PrintDialog QuickAssist SearchApp SettingSync SmartScreen SecureAssessmentBrowser Win32WebViewHost WindowsDefender BioEnrollment WindowsMixedReality WindowsStoreClient XboxClient XboxGameCallableUI AdvertisingXaml VP9VideoExtensions HEIFImageExtension WebMediaExtensions WebpImageExtension DesktopAppInstaller GetHelp MixedRealityPortal 3DViewer NotepadApp ServicesStoreEngagement ScreenSketch StickyNotes StorePurchaseApp Terminal Getstarted SoundRecorder WindowsStoreApp XboxApp GamingApp XboxGamingOverlay XboxGameOverlay XboxIdentityProvider XboxSpeechToTextOverlay XboxTCUI
@inTerActionVRI, hello friend! EnterpriseS (SN) = Ent LTSC = "17763" (v1809) and "19044" (v21H2) Disabling the Notification Center in Windows 11 using the old tweak for Windows 10 Code: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Explorer] "DisableNotificationCenter"=dword:00000001 violates these functions. Only when using StartAllBack (enabling the classic win10 taskbar), you can safely disable the Notification Center in this way. As well as enable seconds for the tray clock: Code: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "ShowSecondsInSystemClock"=dword:00000001
@MSMG, hello! 1. Why does not the integration of CU (KB5011493) into the base image of Windows 11 (22000.1) using the WHD method? Files used: 22000.1.210604-1628.CO_RELEASE_CLIENTIOTENTERPRISE_OEMRET_X64FRE_RU-RU.ISO (uupdump.net) SSU-22000.469-x64.cab Windows10.0-KB5011493-x64.cab Windows10.0-KB5011493-x64.psf Error Message: "Creating WHD General Updates Temporary folder... Extracting .CAB Package files to Temporary folder... A file with that name already exists or was not found." I still managed to integrate KB5011493 using the Updates method, having previously converted psf + cab files into a combined Windows10.0-KB5011493-x64-full_psfx.cab using PSFX_Repack 6. Using the WHD method to integrate the combined Windows10.0-KB5011493-x64-full_psfx.cab (even with the conversion to a simpler name -> Windows10.0-KB5011493-x64.cab) is also impossible. _______________________ 2. In the template RemovePkgsList_W11_10.0.22000.txt now there is no SettingSync component. Maybe I forgot something or overlooked something... Is this how it should be?
Hey guys, I found some problems breaking the Custom Toolkit code, in the changes made to Disable and Enable Features. I am fixing these details. If you didn't have problems, OK! But if you need to use these Customizations, please wait a little while and I'll come back today or tomorrow with a fix. Thanks for your attention! EDIT: the problem was caused by the Warning about "Cleanup Source Images" that MSMG said I should add. And, that I hadn't even put yet, in the version I published, hehehehe.
This answer solved my previous question. Thanks for the answer and confirmation. It would have been very interesting if that answer from you had come about 2 days ago! It would have saved me a lot of testing time. But this time was not totally lost, because I developed a method to test more quickly these problems derived from registry tweaks. And, your answer came with some nice additions. But I haven't done Start Menu replacement since Windows 8.0.
@MSMG, I found it more interesting to add the warning within the :CleanupSources session, I think it is simpler and correctly positioned, in the code. I modified this today. But since it doesn't interfere with function, I'll post this change just in case some CustomToolkit fix is needed. It can be placed this way, in the Toolkit.
@MSMG, Hello, good greeting time... (for version In 12.1) please read following format as line number, blue is original line, pink denotes replacement line 1) line 21643 if "%ImageBuild%" equ "20348" if "%ImageInstallationType%" equ "Server" if "%SourceEdition%" equ "ServerSolution" if "%TargetEdition%" equ "ServerStandard" ( if "%ImageBuild%" equ "20348" if "%ImageInstallationType%" equ "Server" if "%TargetEdition%" equ "ServerStandard" ( 2) line 21648 set "DisplayName=Windows Server 2022 Standard ^(Desktop Experience^)" set "DisplayName=Windows Server 2022 Standard (Desktop Experience)" <~~ ^ char should be removed 3) line 21652 if "%ImageBuild%" equ "20348" if "%ImageInstallationType%" equ "Server" if "%SourceEdition%" equ "ServerStandard" if "%TargetEdition%" equ "ServerDatacenter" ( if "%ImageBuild%" equ "20348" if "%ImageInstallationType%" equ "Server" if "%TargetEdition%" equ "ServerDatacenter" ( 4) line 21657 set "DisplayName=Windows Server 2022 Datacenter ^(Desktop Experience^)" set "DisplayName=Windows Server 2022 Datacenter (Desktop Experience)" <~~ ^ char should be removed I already corrected my Script, you please update for next version.....
For Server v1809, Server 2019 and Server 2022 I have made the corrections to support the possible target editions Code: if "%ImageBuild%" equ "17763" if "%ImageInstallationType%" equ "Server Core" if "%SourceEdition%" equ "ServerStandardACor" if "%TargetEdition%" equ "ServerDatacenterACor" ( set "Flag=ServerDataCenterACor" set "Edition=ServerDatacenterACor" set "Name=Windows Server SERVERDATACENTERACORE" set "Description=Windows Server SERVERDATACENTERACORE" set "DisplayName=Windows Server Datacenter" set "DisplayDescription=^(Recommended^) This option omits most of the Windows graphical environment. Manage with a command prompt and PowerShell, or remotely with Windows Admin Center or other tools." ) if "%ImageBuild%" equ "17763" if "%ImageInstallationType%" equ "Server Core" if "%SourceEdition%" equ "ServerStandard" if "%TargetEdition%" equ "ServerDatacenter" ( set "Flag=ServerDataCenterCore" set "Edition=ServerDataCenter" set "Name=Windows Server 2019 SERVERDATACENTERCORE" set "Description=Windows Server 2019 SERVERDATACENTERCORE" set "DisplayName=Windows Server 2019 Datacenter" set "DisplayDescription=^(Recommended^) This option omits most of the Windows graphical environment. Manage with a command prompt and PowerShell, or remotely with Windows Admin Center or other tools." ) if "%ImageBuild%" equ "17763" if "%ImageInstallationType%" equ "Server" if "%SourceEdition%" equ "ServerStandard" if "%TargetEdition%" equ "ServerDatacenter" ( set "Flag=ServerDataCenter" set "Edition=ServerDataCenter" set "Name=Windows Server 2019 SERVERDATACENTER" set "Description=Windows Server 2019 SERVERDATACENTER" set "DisplayName=Windows Server 2019 Datacenter ^(Desktop Experience^)" set "DisplayDescription=This option installs the full Windows graphical environment, consuming extra drive space. It can be useful if you want to use the Windows desktop or have an app that requires it." ) if "%ImageBuild%" equ "20348" if "%ImageInstallationType%" equ "Server Core" if "%SourceEdition%" equ "ServerStandard" if "%TargetEdition%" equ "ServerDatacenter" ( set "Flag=ServerDataCenterCore" set "Edition=ServerDatacenter" set "Name=Windows Server 2022 SERVERDATACENTERCORE" set "Description=Windows Server 2022 SERVERDATACENTERCORE" set "DisplayName=Windows Server 2022 Datacenter" set "DisplayDescription=^(Recommended^) This option omits most of the Windows graphical environment. Manage with a command prompt and PowerShell, or remotely with Windows Admin Center or other tools." ) if "%ImageBuild%" equ "20348" if "%ImageInstallationType%" equ "Server" if "%SourceEdition%" equ "ServerStandard" if "%TargetEdition%" equ "ServerDatacenter" ( set "Flag=ServerDatacenter" set "Edition=ServerDatacenter" set "Name=Windows Server 2022 SERVERDATACENTER" set "Description=Windows Server 2022 SERVERDATACENTER" set "DisplayName=Windows Server 2022 Datacenter ^(Desktop Experience^)" set "DisplayDescription=This option installs the full Windows graphical environment, consuming extra drive space. It can be useful if you want to use the Windows desktop or have an app that requires it." ) The ^ character is required to avoid the script from crashing when '(' ')' used within the loops.
Hola buenas, se puede actualizar de la version "ToolKit_v8.8" a la versio "ToolKit_v12.1" DIRECTAMENTE o hay que ir una a una. Ejemplo 1: ToolKit_v8.8, ToolKit_v8.9, ToolKit_v9.0, ToolKit_v9.2, ToolKit_v9.3 etc o Ejemplo 2: ToolKit_v8.8, ToolKit_v12.1 (SERIA ASI CORRECTO)
@MSMG, Thanks for reply & kind support, I am currently using your Toolkit for Windows Server 2022, I am correcting only those lines of code which are executed for 20348 only. Please note that, your script only works successfully when Target Edition for Upgrade operation is Datacenter only, but as in my case, "Standard Evaluation" can be upgraded to "Standard Desktop" & "Datacenter Evaluation" can be upgraded to "Datacenter Desktop", so the same can be achieved by my changes, hence I mentioned it earlier. Also for ^ character, note that, we are just assigned to a variable, & trying to set it as a property of Wim file. i.e. as we are not echoing it using echo chars hence ^ character should be removed otherwise it will becoming as a part of Image Index Name
Puedes actualizar directamente, extrae la versión nueva. Es como si hicieras una instalación nueva y limpia. - You can upgrade it directly, extract the new version. It should be like a new installation. La próxima vez pregunta en inglés. - Next time ask in English. Un saludo - Greetings
@MSMG this morning was working with version 12.1 of MSMG Toolkit then after some operations appeared this warning (see image below) this never happened before what I did wrong? Thank you again for collaboration Thank you
Ok, I have updated the script to support converting Windows Server 20348 Evaluation version editions.