When creating the base image 22621.1, I tried to apply the CustomList =1 parameter for ConvertConfig.ini by selecting in CustomAppsList.txt only the applications I need for integration. And I found this option very convenient, for which I am grateful to everyone who is working on the development of the project uupdump.net! Spoiler: ConvertConfig.ini [convert-UUP] AutoStart =1 AddUpdates =0 Cleanup =0 ResetBase =0 NetFx3 =0 StartVirtual =1 wim2esd =0 SkipISO =1 SkipWinRE =1 LCUwinre =0 UpdtBootFiles=0 ForceDism =0 RefESD =0 SkipEdge =0 AutoExit =0 [Store_Apps] SkipApps =0 AppsLevel =0 CustomList =1 [create_virtual_editions] vAutoStart =1 vDeleteSource=1 vPreserve =0 vwim2esd =0 vSkipISO =0 vAutoEditions=IoTEnterprise Spoiler: CustomAppsList.txt ### UWP Store applications, for integration into builds 22563 and later ### Choose the wanted apps from below by removing # prefix ### Common Apps / Client editions all Microsoft.WindowsStore_8wekyb3d8bbwe # Microsoft.StorePurchaseApp_8wekyb3d8bbwe # Microsoft.SecHealthUI_8wekyb3d8bbwe Microsoft.VCLibs.140.00_8wekyb3d8bbwe Microsoft.Windows.Photos_8wekyb3d8bbwe # Microsoft.WindowsCamera_8wekyb3d8bbwe # Microsoft.WindowsNotepad_8wekyb3d8bbwe # Microsoft.Paint_8wekyb3d8bbwe # Microsoft.WindowsTerminal_8wekyb3d8bbwe # Microsoft.DesktopAppInstaller_8wekyb3d8bbwe # MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy # Microsoft.WindowsAlarms_8wekyb3d8bbwe Microsoft.WindowsCalculator_8wekyb3d8bbwe # Microsoft.WindowsMaps_8wekyb3d8bbwe # Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe # Microsoft.ScreenSketch_8wekyb3d8bbwe # microsoft.windowscommunicationsapps_8wekyb3d8bbwe # Microsoft.People_8wekyb3d8bbwe # Microsoft.BingNews_8wekyb3d8bbwe Microsoft.BingWeather_8wekyb3d8bbwe # Microsoft.MicrosoftSolitaireCollection_8wekyb3d8bbwe # Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe # Microsoft.WindowsFeedbackHub_8wekyb3d8bbwe # Microsoft.GetHelp_8wekyb3d8bbwe # Microsoft.Getstarted_8wekyb3d8bbwe # Microsoft.Todos_8wekyb3d8bbwe # Microsoft.XboxSpeechToTextOverlay_8wekyb3d8bbwe # Microsoft.XboxGameOverlay_8wekyb3d8bbwe # Microsoft.XboxIdentityProvider_8wekyb3d8bbwe # Microsoft.PowerAutomateDesktop_8wekyb3d8bbwe # Microsoft.549981C3F5F10_8wekyb3d8bbwe # MicrosoftCorporationII.QuickAssist_8wekyb3d8bbwe # MicrosoftCorporationII.MicrosoftFamily_8wekyb3d8bbwe ### Media Apps / Client non-N editions # Microsoft.ZuneMusic_8wekyb3d8bbwe # Microsoft.ZuneVideo_8wekyb3d8bbwe # Microsoft.YourPhone_8wekyb3d8bbwe # Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe # Microsoft.GamingApp_8wekyb3d8bbwe # Microsoft.XboxGamingOverlay_8wekyb3d8bbwe # Microsoft.Xbox.TCUI_8wekyb3d8bbwe # Clipchamp.Clipchamp_yxz26nhyzhsrt ### Media Codecs / Client non-N editions, Team edition Microsoft.WebMediaExtensions_8wekyb3d8bbwe Microsoft.RawImageExtension_8wekyb3d8bbwe Microsoft.HEIFImageExtension_8wekyb3d8bbwe Microsoft.HEVCVideoExtension_8wekyb3d8bbwe Microsoft.VP9VideoExtensions_8wekyb3d8bbwe Microsoft.WebpImageExtension_8wekyb3d8bbwe ### Surface Hub Apps / Team edition # Microsoft.Whiteboard_8wekyb3d8bbwe # microsoft.microsoftskydrive_8wekyb3d8bbwe # Microsoft.MicrosoftTeamsforSurfaceHub_8wekyb3d8bbwe # MicrosoftCorporationII.MailforSurfaceHub_8wekyb3d8bbwe # Microsoft.MicrosoftPowerBIForWindows_8wekyb3d8bbwe # Microsoft.SkypeApp_kzf8qxf38zg5c # Microsoft.Office.Excel_8wekyb3d8bbwe # Microsoft.Office.PowerPoint_8wekyb3d8bbwe # Microsoft.Office.Word_8wekyb3d8bbwe
This is not in Toolkit. I made this code to Toolkit and its folder structure. I would need this part of your code, responsible for (Copy Patch Network Printing), so I could help you with something. Use Toolkit's nsudo is in the most current version. Check the path for the nSudo in your script folder structure. As always said, use well shortened paths.
Cool, I just tried to make a contribution while I took some simple technical doubts, with Abbodi. We really have to be grateful to their huge work at UUPDump Project, like MSMG for the development of Toolkit. Below is a compilation of the posts that generated the idea of creating the CustomList for Builds from 22563. Spoiler: From where the Custom List started But besides that, it originated in the MSMG list of lists. So that was the initial source for me. Which provided me with the application of what I have been learning in those 2 years.
@MSMG, In :IntWindowsSetupMediaUpdates , just to optimize the code. from: Code: for /f "tokens=* delims=" %%a in ('%DISM% /Get-WimInfo /WimFile:"%BootWim%" /Index:2 ^| findstr /i Default') do ( set ImageDefaultLanguage=%%a ) to: Code: for /f "tokens=1 delims= " %%a in ('%DISM% /Get-WimInfo /WimFile:"%BootWim%" /Index:2 ^| findstr /i "Default"') do (set "ImageDefaultLanguage=%%a") It should be done with these too: from: Code: for /f "tokens=* delims=" %%j in ('%DISM% /Get-ImageInfo /ImageFile:"%~1" /Index:%~2 ^| findstr /i Default') do (set ImageDefaultLanguage=%%j) to: Code: for /f "tokens=1 delims= " %%j in ('%DISM% /Get-ImageInfo /ImageFile:"%~1" /Index:%~2 ^| findstr /i "Default"') do (set "ImageDefaultLanguage=%%j") Note "tokens=1" and "delims= " with space. then all from: Code: set ImageDefaultLanguage=!ImageDefaultLanguage:~1,-10! to: Code: set "ImageDefaultLanguage=!ImageDefaultLanguage:~1!" Note this ,-10 was removed.
could someone please tell me how to remove "Windows PowerShell ISE" and "Windows PowerShell", native to Windows using Toolkit?? Please!!
Provide the text of the description of the stop code. As a rule, @MSMG checks the removal of all components available for ToolkitHelper, and tests the subsequent installation of the system. The reason may not be in remote applications, but in something else. For example, in the applied custom registry tweaks, which could contain "CurrentControlSet" in the keys. Have you applied your custom registry files to the image? If yes, then check, and all "CurrentControlSet" should be replaced with "ControlSet001". This is one of the most common causes of a blue screen.
Judging by the pictures, in your case it is completely impossible to install the system. I think you need to describe in detail your actions (steps) to configure the image, and provide a list of the components you are removing for @MSMG.
No, I'm not deleting the main version of PowerShell installed on the system. I just showed how this can be done using NTLite by answering @bala1's question. I am removing only the old version of PowerShell-V2 from my system. Apparently, it is only needed for compatibility with older versions of scripts. I don't need it. To be honest, I am not a great expert in the field of PowerShell, and I do not do it professionally, like you. Earlier I tried to integrate PS v7 into the system, but some common simple commands did not work in it, therefore, for those few rare tasks related mainly to system maintenance, the version supplied with the system is quite enough for me.
Yes, that's why I asked. I also had this problem with V7. I prefer to keep the native version. I don't make professional use, no.