1. Jingzin

    Jingzin MDL Addicted

    Nov 10, 2021
    666
    536
    30
    Tried msmg toolkit against 24h2 iot ltsc. Many different combinations. Removing packages does work like for example defender and security,
    Couldn't remove only sechealthui
    Some package names in toolkits preset folders do exists others don't like edge for example.
    The main problem with the ToolKit is that no matter what I removed using it WU will refuse to install updates. Not sure if there's some policy that needs some kind of mod or what but as things are now better not to use toolkit against 24h2.
    If you're interested in 24h2 best option to tweak 24h2 I found and safest one is dark dinosaur script or ntlite
     
  2. mhussain

    mhussain MDL Senior Member

    Oct 1, 2012
    384
    161
    10
  3. megaborg

    megaborg MDL Novice

    Nov 14, 2009
    16
    5
    0
    Sorry Jingzin where can i find dark dinosaur script....i would like to test it....:p
     
  4. chev7

    chev7 MDL Novice

    Dec 7, 2019
    22
    2
    0
    #27104 chev7, Jul 6, 2024
    Last edited: Jul 6, 2024
    Good afternoon guys, tell me why I get this message, even though the image is already old Win 10 22h2 19045.2965 and Toolkit 13.7. I've read the README.txt, but it's not clear how to use Dism. I thought the version was already old and I’m worried that not everything that I choose will be removed from the image. Below is the toolkit message:
    The selected source image build does not support custom component removal,
    However it supports DISM component removal. For component removal, use Remove
    Windows Components using Package List (DISM Method) menu.
    Do you want to continue ? ['Y'es/'N'o] :
     
  5. graver.x

    graver.x MDL Senior Member

    Jan 18, 2020
    349
    486
    10
    Windows 7-11 Tweak Script
     
  6. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,770
    3,601
    60
    This is a known issue regarding removing components via ToolkiHelper in builds not listed as supported.
    MSMG itself says that removing components in unsupported builds may have a problem with Windows Update.

    I discovered that the removal of CEIP, starting from 22621, causes problems with DISM when trying to enable some features after its removal.
    Considering this... We can assume that the problems with Windows Update may be related to this.
    Only with tests maintaining the CEIP to know if positive results occur.

    This doesn't cause any problems for me, as I do Inplace Upgrade when I want to update. And for this reason I always have my Windows Update turned off.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. Jingzin

    Jingzin MDL Addicted

    Nov 10, 2021
    666
    536
    30
  8. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,770
    3,601
    60
    This is good to know, I use Pro Edition.
    But what's the problem with inPlace Upgrade at LTSC?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. Jingzin

    Jingzin MDL Addicted

    Nov 10, 2021
    666
    536
    30
    Theres no newer iso to download for iot ltsc unless pro can be used to upgrade ltsc? not sure. Also if WU won't let you install updates due to whatever removed packages issue would in place upgrade even work?
     
  10. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,770
    3,601
    60
    No, I didn't mean to say that I use the Pro to do InPlace at LTSC. I don't use LTSC. I only use the Pro, so I do InPlace Upgrade.

    I'm asking what problem is encountered in trying the InPlace Upgrade with LTSC, as it is normally possible to integrate the updates into the ISO and do the InPlace even with disabled Windows Update.


    This would need testing.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. mhussain

    mhussain MDL Senior Member

    Oct 1, 2012
    384
    161
    10
    an in-place upgrade simply replaces os installation files
    before doing so, it moves your user data to windows.old?
    then back after the new os has been applied.
    if i'm wrong correct me
     
  12. Jingzin

    Jingzin MDL Addicted

    Nov 10, 2021
    666
    536
    30
    You could probably add updates to iso and then try to whatever just not sure if that would work even if that's long the long way and settings data could be deleted right?
     
  13. Yanta

    Yanta MDL Senior Member

    May 21, 2017
    491
    284
    10
    #27115 Yanta, Jul 8, 2024
    Last edited: Jul 8, 2024
    Maybe I'm doing something wrong, but I can reliably wreck a system every time by doing an in place upgrade with LTSC
    Perhaps it's the combination of thingsI remove. Never bothered trying to track it down. Just stick to scratch install every time.
    Only takes an hour from start to finish to get back to where I was before starting.(all apps installed etc).

    Create image from toolkit with current CU
    When new CU is released create new image from scratch from toolkit.
    Do in place upgrade and system will be totally messed up

    Always making sure that all removals and additions are the same
    I think I posted about this a couple of years ago... I went through the side effects of the upgrade... stopped looking for problems after getting to 40.

    Actually, it was only last september; My how time flies;
    https://forums.mydigitallife.net/threads/msmg-toolkit.50572/page-1319#post-1807653
     
  14. chev7

    chev7 MDL Novice

    Dec 7, 2019
    22
    2
    0
    thank you very much for your time
     
  15. inTerActionVRI

    inTerActionVRI MDL Expert

    Sep 23, 2009
    1,770
    3,601
    60
    I never lost the settings made in ISO. Maybe you do a lot of post-installation configuration. And, for this reason, it makes a lot of difference in your final configuration.


    For me, an installation from scratch takes me around 8 hours, but I don't waste the 8 hours linearly, I use the system as I get it right. Even so, if you calculate it linearly, it takes about 4 hours (without considering the creation of the personalized ISO).
    Regarding the preparation of the ISO, I don't consider it a waste of time, as I put it to be created, without any objective or concern about using it on the same day I am preparing it. After all, if I had this concern I wouldn't postpone updates by disabling Windows Update, in favor of creating an ISO to perform the InPlace Upgrade.
    Letting Windows Update integrate updates, at inopportune times, and still returning removed functionality, is considered by me to be the biggest headache of Windows Update. With Inplace Upgrade I better control this, I never have resources removed, being reintegrated and/or reactivated.


    When you talk like that, it sounds like some very worrying problem is occurring. But what you already mentioned was something regarding the duplication of details in the system registry. But regarding the rest, once you have a fully configured ISO, these are only benefits, as I waste 30 to 40 minutes, then I just use the Windows cleaner to remove previous installations. And, Inplace Upgrade is the best temp and cache cleaner out there. Each time it cleans 20 gigs of junk.


    Yes, I remember that, as it was crucial for me to decide whether to keep my way or not. But the times I've had to perform clean installs, I've observed what I report above.
    So, I still consider using Inplace Upgrade to be very beneficial, "IN MY CASE".

    But several configs items from your list, are confirmed with me too. It is up to everyone to decide there ways to update.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Yanta

    Yanta MDL Senior Member

    May 21, 2017
    491
    284
    10
    I agree 100%

    I am very grateful for the work you, MSMG and others that have contributed to the toolkit. I'm sure i"m not exploiting all of the features, and preparing an ISO is about 20 minutes of work. Like you, I've done it so many times I'm sure we could probably do it with our eyes closed.

    I've spent many hours over the last 5-6 year perfecting my "setup-complete" type script now there is virtually nothing that I have to do manually. Install Windows, run a couple of scripts and pick up where I left off - with a full fresh install. Life is good :)

    It's good that there are many ways to skin a cat and get the outcomes we desire.
     
  17. Ace2

    Ace2 MDL Guru

    Oct 10, 2014
    2,206
    1,909
    90
    @MSMG Looking forward to ToolKit update.:good3: