1. Robotnik247

    Robotnik247 MDL Junior Member

    Nov 21, 2012
    90
    13
    0
    is there any legit 19042.610 build out there atm or should we apply the update over .572?
     
  2. footnote_marmalade

    footnote_marmalade MDL Novice

    Oct 28, 2020
    4
    0
    0
    Hi Folks,
    Just using MSMG on Win10 20H2 right now. I delete components 1 by 1 because of the bug.
    My understanding is that it is not recommended to clean up after that, will it reinstall every deleted components ?
    Can I use my ISO even if it is not cleaned up ?
     
  3. kosta26

    kosta26 MDL Junior Member

    Jan 1, 2019
    91
    5
    0
    we do not recommend clearing the image. Updates won't come because the update is broken, the author knows. I did the tests.
    after removing the toolkit components, cumulative updates are not installed at all.
     
  4. Bokeron

    Bokeron MDL Novice

    Dec 20, 2011
    24
    7
    0
    I've reached the point where I don't know what am I doing anymore.

    First, take this into account: I aim for a very slim install. I don't care about sfc, or updates at all. I remove A LOT of functionalities more once I end working with MSMG Toolkit and keep on working on the image with other tools.
    So, my first step is MSMG Toolkit. And I am lost.

    I start downloading an image from uupdump. Feature Update 19042.610.
    The updates are launched over the bare 19041.1 once the install is finished.
    As this inteferes with component removal, I try to integrate the updates into the wim image.

    First I tried manually using DISM and ended with two packages of every feature, one for the old and one for the new... and neither could be uninstalled. Cleanupt or resetbase did nothing.

    The I used MSMG Toolkit to integrate kb4577266, kb4579305 and kb4580364. It refused to install kb4562830 but I still went ahead to test it, applied changes and rebuilt image. DISM didn't showed double packages and those I wan't removed could be removed, I did resetbase... happiness at last... but... build version wasn't showing 19042.610 but 19041.610
    "This doesn't look like a good omen", I feared.
    I used MSMG Toolkit to install the package it refused before, kb4562830, but this time it installed it. Applied, rebuilt, went to DISM to check.
    Now version build is OK, 19042.610 ... but here they are again, double invincible packages that laugh at my efforts with disdain.

    So... what am I doing? Why is this happening? What SHOULD I be doing instead? Different image version? Different download origin? Go back to Windows Millenium?

    Can someone please explain how are all of these facts connected and enlighten me with the wisdom I lack to achieve the grace of installing a working Windows 10 version before my life ends?

    Thank you.
     
  5. sergey130270

    sergey130270 MDL Senior Member

    May 15, 2014
    299
    395
    10
    Hello dear forum users! Sorry to be off-topic, help me find a tweak (reg file) that includes PhotoViewer for Windows 10.0.19042.610. Thanks.
     
  6. Tiger-1

    Tiger-1 MDL Guru

    Oct 18, 2014
    8,326
    11,604
    270
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. miketunes

    miketunes MDL Novice

    Aug 23, 2010
    41
    5
    0
    I see that file C:\msmg10.8\Bin\XMLs\w10_CustomStartMenuLayout.xml, where do I need copy it to so the 4 > 6 option will import it?
     
  8. Ace2

    Ace2 MDL Guru

    Oct 10, 2014
    2,206
    1,909
    90
    XML was applied to image before removing components, in fact all the step's in Before using ToolKitHelper_1.0.4104.0: were used / applied.;)
     
  9. ingviowarr

    ingviowarr MDL Senior Member

    Dec 14, 2009
    345
    363
    10
  10. JLT2000

    JLT2000 MDL Junior Member

    Nov 3, 2020
    69
    20
    0
    #17290 JLT2000, Nov 10, 2020
    Last edited: Nov 10, 2020
    Hey kosta.

    Did You say that new updates, dont get installed, if we remove components with toolkit.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. JLT2000

    JLT2000 MDL Junior Member

    Nov 3, 2020
    69
    20
    0
    #17291 JLT2000, Nov 10, 2020
    Last edited: Nov 10, 2020
    The bug is SolitaireCollection in RemovePkgsList, it works with RemoveAppsList, but it doesnt matter if, win update is broken after
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. kosta26

    kosta26 MDL Junior Member

    Jan 1, 2019
    91
    5
    0
  13. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    #17293 MSMG, Nov 10, 2020
    Last edited: Nov 10, 2020
    (OP)
    It is not recommended to clean up image and it is installing the updates which will restore the deleted components and not the image clean up.

    Right now you cannot install the update for 19042, better wait for next release.

     
  14. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    To integrate updates using Toolkit follow the below step

    Code:
    [E] - Integrate Windows Updates using [Integrate->Windows Updates->WHD Update Pack Menu] menu.
    
          Note: The Toolkit supports updates either in .msu/.cab format.
    
          Copy Windows Cumulative Update file to <WHD\w10\<Architecture>\Cumulative> folder (E.g. <WHD\w10\x64\Cumulative>).
          Copy Windows Defender Update files to <WHD\w10\<Architecture>\Defender> folder (E.g. <WHD\w10\x64\Defender>).
          Copy Windows Dynamic Update files to <WHD\w10\<Architecture>\Dynamic> folder (E.g. <WHD\w10\x64\Dynamic>).
          Copy Windows Enablement Update files to <WHD\w10\<Architecture>\Enablement> folder (E.g. <WHD\w10\x64\Enablement>).
          Copy Windows Flash Player Update file to <WHD\w10\<Architecture>\FlashPlayer> folder (E.g. <WHD\w10\x64\FlashPlayer>).
          Copy Windows .Net Cumulative Update file to <WHD\w10\<Architecture>\NetCumulative> folder (E.g. <WHD\w10\x64\NetCumulative>).
          Copy Windows Servicing Stack Update file to <WHD\w10\<Architecture>\ServicingStack> folder (E.g. <WHD\w10\x64\ServicingStack>).
          Copy Windows Setup Media Update files to <WHD\w10\<Architecture>\SetupMedia> folder (E.g. <WHD\w10\x64\SetupMedia>).
          Copy Windows WinPE Update files to <WHD\w10\<Architecture>\WinPE> folder (E.g. <WHD\w10\x64\WinPE>).
    

     
  15. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    Open the file C:\msmg10.8\Bin\XMLs\w10_CustomStartMenuLayout.xml with notepad and copy the new start menu layout contents to it and save it.

    Now use 4->6

     
  16. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,414
    15,627
    210
    Ok you used the same image and I see you did performed the below steps with 19042 Enablement update integrated

    dism /image:C:\mount /cleanup-image /startcomponentcleanup
    dism /image:C:\mount /cleanup-image /startcomponentcleanup /resetbase
    dism /image:C:\mount /cleanup-image /restorehealth

    But how you did it since integrating 19042 Enablement pack will creating a pending.xml which will not allow to perform the above steps.

    Did you used the Store ESD image from Microsoft which is sysprep image?

     
  17. Robotnik247

    Robotnik247 MDL Junior Member

    Nov 21, 2012
    90
    13
    0
    From what I've gathered it's not okay to clean up sources with a 19042.610 build on 10.8 atm? I used UUP dump if that matters to build my image.
     
  18. kosta26

    kosta26 MDL Junior Member

    Jan 1, 2019
    91
    5
    0
    If you clean the image, the system will not pass the sfc /scannow check
     
  19. miketunes

    miketunes MDL Novice

    Aug 23, 2010
    41
    5
    0
    Forgive my ignorance. I didn't make a "new start menu" - I thought using yours would remove the pinned items and replace it with file explorer. That's what I'd like to do, the 4 > 6 seemed to import a file, but when I loaded the iso is still had pinned junk to the start menu.
     
  20. Ace2

    Ace2 MDL Guru

    Oct 10, 2014
    2,206
    1,909
    90
    #17300 Ace2, Nov 10, 2020
    Last edited: Nov 10, 2020
    I used 19042.572.201009-1947.20h2_release_svc_refresh.esd and esd-decrypter-wimlib-56.7z to build iso, from https://forums.mydigitallife.net/threads/windows-10-esd-repository.59082/#post-992532

    PS. modded install.wim, installed and running fine.;)