if you are doing a clean installation you should see the following images are in Spain if you choose the old installation the fourth image Windows11 26100.1
Of course I deleted iso useless files. But I found bug in setup.exe is required this files. Restored them and finally all is okay.
26120.1350: It will break Hyper-V and it won't let you uninstall it... so you'll see. I'm going to generate the full ISO from uupdump and do a quick installation... I'll let you know...
It is unable to start existing virtual machines. The service is correct and running, it also does not allow stopping. (it has happened to me on 4 different machines) Uninstalling and reinstalling Hyper-V causes the same thing. 1350: botched job
I am having display issues using Client Remote Desktop with 24H2 26100.1301 (I suspect previous version of 24H2 have same issue). When connecting to a Windows 2008 server I see screen artifacts when moving icons and inside apps. If I use Remote Desktop App from windows store it works ok. Also using Windows 23H2 it works ok. Any ideas?
I used W10UI on the leaked 26100 install.wim (3.8gb). I added kb5040529 (LCU, 375mb) and kb5039894 (NDP35-481, 70mb). The resulting install.wim is 5.5gb, what am I doing wrong here? I am using LTSC2021 to do this, I also tried it in LTSB, but got error 800f0922 there. Is that as expected? It's been a while since I've done this sort of install.wim updating, used to use it a lot and don't remember running into these issues. I'm probably overlooking something, any hints? Thanks in advance...
I do not know if it is normal to do it with 2021 LTSC, the ISO is fattening to put the updates and I see it normal, what I do to get me the resulting ISO smaller is to edit W10UI and change Install.wim convert it to install.esd with what the resulting install has less weight. Change wim2esd =0 by wim2esd =1 so you get instead of install.wim convert it to install.esd.
Thanks for replying. It should be fine to run W10UI in LTSC 2021, I just mentioned that to indicate the difference between LTSC and LTSB (the last one didn't work, as it seems). The "fattening" of the ISO (or rather: the install.wim file) doesn't seem normal to me, that's why I asked if anyone knows what's going on here, either I'm overlooking something or things have indeed changed. Thanks for mentioning the .ESD option, but I usually don't go that route, as it's an extra step to do, and I'm not interested in a complete ISO, just an updated install.wim, that I directly apply to disk. A .wim file is easier to service, as well. And of course: a smaller install.wim would also result in a smaller .esd, so the question about the large file size still remains.
26100 already got very big LCU, dev channel updates are even more bigger with 3 LCU to install at once It's fine
Thanks for replying. It's just that (for example) Enthousiast's iso (install.wim) seems a lot smaller. Normally I don't mind being bigger that others, but in this case I prefer to be the modest one
he's using cleanup+resetbase which removes old packages, I haven't seen anything about this in your posts his full LTSC ISO with install.wim and one index is 5.46 Gb.
resetbase doesn't work 100% on w11 24h2, it leaves a lot of garbage behind, did you see the screens in my post above? curious that in old win 22h2 23h2 resetbase works normally I'm waiting for our friend or someone who knows how to make a script that automates this that can get this list from dism++ and do this task automatically.