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?
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.
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
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?
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
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.
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.
Hi, maybe asking before, but did not found the answer. Question: What are the components not to remove in order not to break windows update for windows Iot 10 21h2 ? I would like to remove as much I don't need . Thanks.
I tried to use another toolkit from this forum called DISMTools but I had no luck in removing as much as I could with MSMG Toolkit. Today I found UnattendedWinstall which uses autounattended.xml to remove components and set settings. But can it make windows install better/same as MSMG or does toolkit add some scripts or other tricks that for example prevent removed components from reinstall action or allow to login with local account not Microsoft (I know that toolkit does that) that autounattended.xml don't have? Thanks for answer.
Thank you so much for effort you put in explaining it all. I will most likely try it. I'm using windows defender and windows update for security and stability reasons, but appart from that, I debloat all I can. I was just thinking about updating to 24h2 from 22h2 which I debloated with MSMG. It worked perfectly for a long time but recently I was getting error 0x80070490 from DeviceSetupManager and my mouse was disconnecting 2-3 times a day due to problems with installing drivers. I checked everything and only after changing Device Installation Settings to "No" it fixed it somehow that I don't get errors in Event Viewer, but it still does disconnects one or twice a week at random. I figured it might to do something with how debloated windows is with msmg and even though I kept Windows updated and driver updates, it somehow fails. So I thought debloating 24h2 with something else will help. Thanks again for help.
Or your mouse or Bluetooth is failing I'm too on 22h2 22621.2283 been trying 24h2 pro and iot ltsc but 22h2 is just lighter you can remove disable tweak whatever you like and it works better vs 24h2.
@ @MSMG Why does the application version target limited Windows builds? Would it be difficult to make this generic and scan the packages in the ISO and remove them accordingly?