1. zero cool root

    zero cool root MDL Senior Member

    Jun 17, 2011
    376
    161
    10
  2. Feartamixg

    Feartamixg MDL Addicted

    May 15, 2016
    767
    616
    30
    I have realised something while testing the Toolkit for sfc errors. The message box error that I reported previously in this thread (link to post) does not appear when working with 17763.1 images. Also these are the same images that do not give sfc errors. Perhaps this is linked, perhaps not.

    But why would 17763.1 not give errors and refreshed images, such as 17763.253, give errors?
     
  3. This issue has been covered before by others but isn't fully confirmed. It's because Toolkit is not compatible after v17763.107, and thing above this version will not work right. So just download 17763.107, use Toolkit v9.2 then update through Windows Updates afterwards. Work like a charm!
     
  4. Supern00b

    Supern00b MDL Addicted

    Dec 30, 2010
    728
    540
    30
  5. Supern00b

    Supern00b MDL Addicted

    Dec 30, 2010
    728
    540
    30
    Good, but it is certainly possible to integrate updates in the same process. I've seen the CBS.log and there are way to many errors, that's not normal.
    Can you describe your workflow?
    Do you use WHD updates and integrate them before removing stuff?

    Cheers.
     
  6. Supern00b

    Supern00b MDL Addicted

    Dec 30, 2010
    728
    540
    30
    The main reason MSMG does not support 1903 images is because of the (possible) changes that may go in before it is released.
    There would be no point in investing a lot of time to support 1903, only to find out that some stuff has changed when it goes final.

    Cheers.
     
  7. Feartamixg

    Feartamixg MDL Addicted

    May 15, 2016
    767
    616
    30
    For now I shall work only with 17763.1 as I know from testing that this doesn't give me any sfc errors.
     
  8. Feartamixg

    Feartamixg MDL Addicted

    May 15, 2016
    767
    616
    30
    ISO: 17763.1.180914-1434.RS5_RELEASE_CLIENTENTERPRISE_VOL_X86FRE_EN-GB.ISO
    SSU: windows10.0-kb4493510-x86_9e3f2ba44fbf4f486ee3d57427b735c736459873.msu
    CU: windows10.0-kb4493509-x86_47af6f3f17da14a289340b880c88eeb27723c7ec.msu
    Extract ISO (1 > 3)

    Select source (1 > 1) (also mount boot and recovery images)

    Integrate Win32 calculator (3 > 3 > B)

    Apply updates (3 > 4 > 2 > 1 > 3)

    Cleanup (6 > 1)

    Remove all metro apps (4 > 1 > 1 > 8)

    Remove Onedrive, People, Connect, Skype (4 > 1 > 2 > H/J/K/P)

    Remove Store, Xbox, Game bar, Xbox ID (4 > 1 > 3 > 1/5/6/7)

    Cleanup (6 > 1)

    Tweaks for Task View, App Downloads, Photo Viewer (5 > 5 > 2/4/7)

    Apply changes to image (6 > 2)

    Rebuild (6 > 1)

    Convert WIM to ESD (2 > 4)

    Make ISO (7 > 1)
    The step in red is where I would normally integrate updates. But I follow these steps in the same order each time.
     
  9. biatche

    biatche MDL Addicted

    Nov 14, 2009
    569
    143
    30
    msmg: are you able to do up a version without the removal of defender, edge and other breaking removals.. and keep simple easy-to-work removals for 1903? and then slowly add support for those?

    that way, we can continue building without waiting for those... as those may take a lot of time.
    \
    sorry if its rude to ask that
     
  10. endbase

    endbase MDL Guru

    Aug 12, 2012
    4,673
    1,709
    150
    I did use NTLite and MSMG toolkit to remove stuff from 1903 but it's better to wait for full support on 1903 cause in my case WU got broken with updating the latest CU
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. petok

    petok MDL Senior Member

    May 4, 2009
    340
    187
    10
    Problem is when remove Holographic packages and then no working WU updating system auto and manual install updates.
     
  12. Ingibjörg

    Ingibjörg MDL Novice

    Oct 18, 2018
    4
    1
    0
    I want to create a windows to go usb. Im going to use windows 10 pro iso, do i have to integrate windows to go or is it already included in the iso ?

    Thanks
     
  13. endbase

    endbase MDL Guru

    Aug 12, 2012
    4,673
    1,709
    150
    So you are saying if I don't remove the Holographic package WU does work ?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. ne

    ne MDL Novice

    Sep 1, 2013
    13
    3
    0
    i used ntlite to remove stuff from 1903 and i got this error 0x800f081f When i try to install the update KB4495666 from windows update .
     
  15. endbase

    endbase MDL Guru

    Aug 12, 2012
    4,673
    1,709
    150
    Yeah working on that myself to find the culprit ;)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. ne

    ne MDL Novice

    Sep 1, 2013
    13
    3
    0
    ok. thanks. i am trying without remove the holographic package.
     
  17. endbase

    endbase MDL Guru

    Aug 12, 2012
    4,673
    1,709
    150
    Oke let me know if it works I'm also testing right now with different settings removed
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,411
    15,486
    210
    I have updated and tested the ToolKit to support Windows 10/Server v1903 and as expected it's working properly with all updated packs.

    Windows 10 v1903 component removal will be added in due time once the Windows 10 v1809 component removal is fixed, I have fixed shared component removal issues and now I'm testing the images with updates pre-integrated.

    Hope to release an update in this week.
     
  19. endbase

    endbase MDL Guru

    Aug 12, 2012
    4,673
    1,709
    150
    Great news ! :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...