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.
New Packs. NET3 NET6 PowerShell7 This was the ones I realized in the repository. This NET3 will only be possible to integrate with the update for Toolkit 12.3, as the pack is in TPK format for W10 and W11. I imagine MSMG has made this pack in order to remedy the integration problem that generates "pending.xml". If this is possible, this is very good. These are just assumptions.
I don't see your actions when using Toolkit, so I can't know what you are doing wrong. And what is "Pacote Package" in your removal process? I noticed an error in your list: "Microsoft-Windows-PowerShell-ISE-FOD~31bf3856ad364e35~amd64" instead of "Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~amd64". Toolkit Menu: [3] Remove -> [3] Remove Windows Components Using Package List -> [1] Remove Windows Components Using Package List (DISM Method): Spoiler: The removal process Code: =============================================================================== MSMG ToolKit - Remove Windows Components Using Package List =============================================================================== ------------------------------------------------------------------------------- ####Starting Removing Windows Components Using Package List#################### ------------------------------------------------------------------------------- Image : Install.wim Image Index : 1 Image Architecture : x64 Image Version : 10.0.19044.1741.0 ------------------------------------------------------------------------------- ####Removing Windows Components Using Package List############################# ------------------------------------------------------------------------------- ===========================[Install.wim, Index : 1]============================ ------------------------------------------------------------------------------- Removing Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~amd64 Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.22598.1 Image Version: 10.0.19044.1741 Processing 1 of 1 - Removing package Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~amd64~~10.0.19041.1 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- Removing Microsoft-Windows-PowerShell-ISE-FOD-Package~31bf3856ad364e35~wow64 Package... ------------------------------------------------------------------------------- The specified package has already been removed... ------------------------------------------------------------------------------- Removing Microsoft-Windows-PowerShell-V2-Client-Package~31bf3856ad364e35~amd64 Package... ------------------------------------------------------------------------------- Deployment Image Servicing and Management tool Version: 10.0.22598.1 Image Version: 10.0.19044.1741 Processing 1 of 1 - Removing package Microsoft-Windows-PowerShell-V2-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.1023 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------------------------- ####Finished Removing Windows Components Using Package List#################### ------------------------------------------------------------------------------- =============================================================================== Для продолжения нажмите любую клавишу . . . ~wow64 Package - obviously is a dependent package, and is removed automatically along with ~amd64 Package, so you can make a list easier: Code: ; PowerShell-ISE-FOD Microsoft-Windows-PowerShell-ISE-FOD-Package ; PowerShell-V2 (older version) Microsoft-Windows-PowerShell-V2-Client-Package
I'm having an issue with Cumulative Windows Update (KB5013942) - it fails to install (getting an error during installation). Regular updates were installing fine Windows 10 21H2 stock installation image was customized with MSMG 12.1 - all Windows components were removed except this OfflineFiles OpenSSH RemoteDesktopClient RemoteDifferentialCompression SimpleTCPIPServices TelnetClient TFTPClient RemoteDesktopServer RemoteRegistry WorkFoldersClient ProjFS StorageSpaces MSMG ToolKit During troubleshooting - I found report that this issue could be due to missing Windows Store Apps. So I tried creating a second image that had all of the Windows Store Apps preserved. However Cumulative Update still fails. Any ideas?
Does anyone know how to remove through the Toolkit the "mip.exe" "Math Input Panel" is in Windows Accessories, appeared here in iso 19044.1739
You can remove it using the DISM method by adding to RemovePkgsList.txt the following packages: Code: ; TabletPCMath Microsoft-Windows-TabletPCMath-Package microsoft-windows-tabletpcmath-package-Wrapper
My assumption was wrong. So I think MSMG put an appropriate name, so there was no confusion. That NET3 was renamed NETCore31. And new Toolkit.cmd to support this integration. @MSMG, In today's Toolkit.cmd. In :IntWindowsSetupMediaUpdates from set "ImageDefaultLanguage=%ImageDefaultLanguage:~1,-10%" to set "ImageDefaultLanguage=!ImageDefaultLanguage:~1!"
The main thing is that before removing components, you first need to update the image to the CU version that the specific version of ToolkitHelper supports. Otherwise, you will get the same Windows Update errors when trying to install CU, as well as possible SFC errors, and just because the ToolkitHelper is "new", there will be little use.. But also need to remember that in Win10 v1903-v1909-v2004-v20H2-v21H1-21H2 and in Win11 v21H2-v22H2, after installing CU, previously removed components (except WindowsApps) are returned, this is due to the new update format. Therefore, it is worth considering whether it makes sense to update the system using an online CU installation after removing the components... If you really, really want to, you can try to create an updated image using the same presets, and then perform an "in-place update" of the Upgrade type with the preservation of user programs, files and settings. But I don't practice this option, so I can't give you a guarantee that with your list of components to be removed, such an update will be successful. Users who have such experience may tell you how successful it is.
I think adding the NETCore 3.1 package is very good and right. Since some programs require a fixed version of NETCore v3.1 LTS. Those who need this version have to install it later, or look for alternative options for integration into ISO. By the way, "NETCore 3.1" - is the right name.
@MSMG, When I was doing the tests to use Wimlib-Imagex to convert to ESD, I went on suffering by waiting for conversion to finish in this mode below. Code: echo. echo.------------------------------------------------------------------------------- echo.####Converting WIM Image to ESD Image########################################## echo.------------------------------------------------------------------------------- :: Exporting Source Image to ESD Image for %%i in (%ImageIndexNo%) do ( rem call :ExportImageIndex "%InstallWim%", %%i, "%InstallEsd%", "ESD", "No" echo. %WimlibImagex% export "%InstallWim%" %%i "%InstallEsd%" --compress=LZMS --solid echo. ) I found it better and faster, compress exported indexes with (--compress=LZX), creating a install.WIM in the Temp folder and then create the ESD with the "All" argument. Code: echo. echo.------------------------------------------------------------------------------- echo.####Converting WIM Image to ESD Image########################################## echo.------------------------------------------------------------------------------- :: Exporting Source Image to ESD Image for %%i in (%ImageIndexNo%) do ( rem call :ExportImageIndex "%InstallWim%", %%i, "%InstallEsd%", "ESD", "No" echo. %WimlibImagex% export "%InstallWim%" %%i "%Temp%\install.wim" --compress=LZX echo. ) move /y "%Temp%\install.wim" "%InstallWim%" >nul %WimlibImagex% export "%InstallWim%" all "%InstallEsd%" --compress=LZMS --solid echo. if exist "%InstallEsd%" call :RemoveFile "%InstallWim%" But it will be interesting for you to test and check if this is plusible. Maybe in your machine it happens different. Faster than in mine, I may have tested so that something went wrong. I only know that exporting the indexes directly to install.ESD, crashed everything here.