MSMG ToolKit

Yes, updated Toolkit. cmd from 05.08.2021, was downloaded from MEGA.

 

All right, I'll get started.

 

How soon will support for removing packets using RemovePkgsList.txt (DISM) be enabled for WINDOWS 11 INSIDER PREVIEW 10.0.22000.132?
What to change in Toolkit.cmd so that only RemovePkgsList.txt can be seen? Ready to test. thanks

 

You need to login to view this posts content.

 

Tested the integration of NET Framework 3.5 into the image 19043.1200 with Toolkit.cmd of 20.08.2021 . WMR works. Looking forward to fixing Win32Calc.

 

of course

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Yes, the final image size will certainly be larger, precisely because you skipped cleaning the replaced components.
But now you have a clean sfc without errors. This is what you wanted. I suggested it to you so that you can see how it happens. It is better to see for yourself 1 time and make sure than to hear it 100 times
(I noticed that it is very difficult for some Toolkit users to understand this)

In fact, the errors of the sfc after clearing the component storage are a Microsoft bug, and this is observed only with images of Win 10 v2004-v20H2-v21H1-v21H2.
This is not observed with LTSC v1809 images and other versions of Windows.
By the way, the images of Windowws 11 are also devoid of this drawback.

And now it's up to you to decide what is more important for you - the absence of sfc errors after installation, or the final ISO size.
But you should remember that after installing OC, we usually run the command anyway Dism.exe /Online /Cleanup-Image /StartComponentCleanup (/ResetBase), and then cleaning in the online system will cause sfc errors in the same way. Based on this, decide what to do.
And yet-do not worry, these errors are not critical, and they are easily corrected with the help of an sfc/scannow scan.

Why then skip cleaning the image during processing in the Toolkit, if after cleaning in the installed system we get the same sfc errors again? - perhaps you may ask.
And in order to get a clean image, for example, we can see whether the work was done correctly ToolkitHealper.exe, and so on. (moreover, not everyone is well versed in the subtleties of reading CBS. log)

 

Yes, in order to get a fully updated ISO, it is better to use Feature Updates from uupdump.net. These sets, in addition to Cumulative Updates, include updated files for the Windows installer (DU for Sources) and updates for WinPE.

 

Allô @MSMG, Errors here to rebuild VCRUNTIME from images 7/81/10

Verification ;

Code:

mistake ;

for %%i in (Certificados, VC_2005, VC_2008, VC_2010, VC_2012, VC_2013, VC_2022, VC_Legacy) faça (
    if not exist "%VCRuntime% \ %%i_%ImageArchitecture%.reg" (
        echo.Microsoft Visual C++ Runtime Pack file "%%i_%ImageArchitecture%.reg" not found...
        echo.
        echo.Please copy the above file to ^<Packs\VCRuntime\%SelectedSourceOS%^> folder...
        goto :Stop
    )
)

to ;

if "% SelectedSourceOS%" neq "w10" (
    for %% i in (Certificados, VC_2005, VC_2008, VC_2010, VC_2012, VC_2013, VC_2019, VC_Legacy) faça (
        if not exist "% VCRuntime% \ %% i_% ImageArchitecture% .reg" (
            echo.Microsoft Visual C++ Runtime Pack file "%%i_%ImageArchitecture%.reg" not found...
            echo.
            echo.Please copy the above file to ^<Packs\VCRuntime\%SelectedSourceOS%^> folder...
            goto :Stop
        )
    )
) else (
    for %%i in (Certificates, VC_2005, VC_2008, VC_2010, VC_2012, VC_2013, VC_2022, VC_Legacy) do (
        if not exist "%VCRuntime%\%%i_%ImageArchitecture%.reg" (
            echo.Microsoft Visual C++ Runtime Pack file "%%i_%ImageArchitecture%.reg" not found...
            echo.
            echo.Please copy the above file to ^<Packs\VCRuntime\%SelectedSourceOS%^> folder...
            goto :Stop
        )
    )
)

Installation ;

mistake ;

for %%i in (Certificates, VC_2005, VC_2008, VC_2010, VC_2012, VC_2013, VC_2022, VC_Legacy) do (
    call :ImportRegistry2Image "%VCRuntime%\%%i_%ImageArchitecture%.reg"
)

to ;

if "%SelectedSourceOS%" neq "w10" (
    for %%i in (Certificates, VC_2005, VC_2008, VC_2010, VC_2012, VC_2013, VC_2019, VC_Legacy) do (
        chamar: ImportRegistry2Image "%VCRuntime%\%%i_%ImageArchitecture%.reg"
    )
) else (
    for %%i in (Certificados, VC_2005, VC_2008, VC_2010, VC_2012, VC_2013, VC_2022, VC_Legacy) faça (
        chamar: ImportRegistry2Image "%VCRuntime%\%%i_%ImageArchitecture%.reg"
    )
)

 

You need to login to view this posts content.

 

@MSMG While I was integrating PortableDevices to a W10 19043 image Toolkit throwed this error. Could you please investigate? I'm using the latest Toolkit from Mega link.

 

Thanks a lot buddy.

Even in ltsc 1809 also when i serviced the iso with msmg 11.7 I got sfc errors. Only in msmg 9.8 I didn't get sfc errors though the iso underwent the component cleaning step.

So now I want to download version 1809 with the upto date feature update from uupdump.
In this case should i exclude or include cleaning Component storage in the download script and msmg 11.7 to get rid of sfc errors ?

 

@tosgaba Just so I don't come across as rude, I assume said file is actually missing from said directory? Like I suppose you actually downloaded the relevant files from the mega folder and put them into... well... Packs\PortableDevices\10.0.19041, instead of just saying "here's an error, fix it".

 

Yes, precisely the said files have been downloaded from the Mega link and put where they belong to.

 

Let me test it on my end real quick and get back to you.

 

Thank you, waiting for your return.

 

Code:

Volume in drive D has no label.
Volume Serial Number is 7CA9-F7A5
Directory of D:\wMSMG\Packs\PortableDevices\10.0.19041

21.08.2021 г.  15:20    <DIR>          .
21.08.2021 г.  15:20    <DIR>          ..
02.03.2020 г.  09:46            35 153 Microsoft-Windows-Portable-Devices-Package~31bf3856ad364e35~amd64~bg-BG~10.0.19041.1.cab
02.03.2020 г.  09:46            32 987 Microsoft-Windows-Portable-Devices-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1.cab
02.03.2020 г.  09:46         2 271 199 Microsoft-Windows-Portable-Devices-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cab
02.03.2020 г.  09:46            36 860 Microsoft-Windows-Portable-Devices-Package~31bf3856ad364e35~x86~bg-BG~10.0.19041.1.cab
02.03.2020 г.  09:46            34 812 Microsoft-Windows-Portable-Devices-Package~31bf3856ad364e35~x86~en-US~10.0.19041.1.cab
02.03.2020 г.  09:46         2 038 811 Microsoft-Windows-Portable-Devices-Package~31bf3856ad364e35~x86~~10.0.19041.1.cab
02.03.2020 г.  09:47            12 326 Microsoft-Windows-Portable-Devices-WOW64-Package~31bf3856ad364e35~amd64~bg-BG~10.0.19041.1.cab
02.03.2020 г.  09:47            13 070 Microsoft-Windows-Portable-Devices-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1.cab
02.03.2020 г.  09:47           681 225 Microsoft-Windows-Portable-Devices-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1.cab
               9 File(s)      5 156 443 bytes
               2 Dir(s)  675 917 627 392 bytes free

Code:

Deployment Image Servicing and Management tool
Version: 10.0.19041.746
Details for image : install.wim

Index : 1
Name : Windows 10 Home
Description : Windows 10 Home
Size : 16 439 396 167 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.19044
ServicePack Build : 1165
ServicePack Level : 0
Edition : Core
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 29050
Files : 108145
Created : 7.12.2019 г. - 13:33:21
Modified : 21.8.2021 г. - 15:31:17
Languages :
        bg-BG
        en-US (Default)
The operation completed successfully.

I got the same error as you.
Notice how the WOW64 cabs have amd64 in them, where the error says wow64. So I replaced amd64 with wow64 in my 3 WOW64 cabs. This is what I got:

Code:

===============================================================================
             MSMG ToolKit - Integrate Windows Portable Devices
===============================================================================
-------------------------------------------------------------------------------
####Starting Integrating Windows Portable Devices##############################
-------------------------------------------------------------------------------
    Image                    : Install.wim
    Image Index              : 1
    Image Architecture       : x64
    Image Version            : 10.0.19044.1165.0
-------------------------------------------------------------------------------
####Integrating Windows Portable Devices#######################################
-------------------------------------------------------------------------------
===========================[Install.wim, Index : 1]============================
-------------------------------------------------------------------------------
####Finished Integrating Windows Portable Devices##############################
-------------------------------------------------------------------------------
===============================================================================
Press any key to continue . . .

Now the only thing I don't really know is if anything actually got integrated or not. I see the Integrating... and Finished integrating... signs, but there's nothing under install.wim, Index : 1, so I can't really know for sure myself.
This is where we need @MSMG I guess.