hxxps://blogs.windows.com/windows-insider/2025/11/07/announcing-windows-11-insider-preview-build-28000-canary-channel/ I found this pretty interesting about Win 11 28000
As @Enthousiast has already pointed out there is not any x86 version of Windows 11 non-LTSC or LTSC. And there won't a new LTSC release until 2027.
It can be installed Windows 11 IoT Enterprise LTSC 2024 on a desktop motherboard socket 775 (ASUS P5G41T-M LX)? It has BIOS/Legacy mode boot, i think.Thx
I use the following to install winget/App Installer on first boot of a fresh install: Code: Add-AppxPackage -Path "./Microsoft.VCLibs.140.00_14.0.33519.0_x64.appx" Add-AppxPackage -Path "./Microsoft.VCLibs.140.00.UWPDesktop_14.0.33728.0_x64.appx" Add-AppxPackage -Path "./Microsoft.WindowsAppRuntime.1.8_8000.616.304.0_x64.appx" Add-AppxPackage -Path "./Microsoft.UI.Xaml.2.8.appx" Add-AppxPackage -Path "./Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" Add-AppxProvisionedPackage -Online -PackagePath "./Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle" -LicensePath "./e53e159d00e04f729cc2180cffd1c02e_License1.xml" Is it possible to integrate all this when making an updated ISO using W10UI?
W10UpdateIntegrator, not apps it will not be hard to add them to install.wim using Dism (or Add-AppxProvisionedPackage -Path)
Gents, I'm thinking of getting WinGet to use but was surprised (I know I shouldn't be) with this on the GitHub page: "The winget.exe client is instrumented to collect usage and diagnostic (error) data and sends it to Microsoft to help improve the product." I'm guessing MS can't help but get everything to send data home. I did see "If you build the client yourself the instrumentation will not be enabled and no data will be sent to Microsoft." so I'm wondering if you've created a clean batch file for this or do you just turn off data collection under Settings? I did see the post about WinGet before but the batch file installed other stuff along with WinGet. It's been ages since I wrote a batch file. I guess I've gotten rusty.
OK, let me end the debate on whether we should install 25H2 eKB (KB5054156) on (IoT) LTSC 2024 (N). We know that 22H2 eKB (KB5015684) can't be installed on (IoT) LTSC 2021 (N) directly, but there are some guys who have such a strong will that they modified KB5015684 so that it can be forced to install on LTSC 2021 and upgrade it to 22H2. I installed LTSC 2021 on a VM and used that modified eKB to upgrad it to 22H2. It did get October's CUs, but today, it can't get any newer CU even though I checked updates several times in the Windows Update. However, other machines and VMs installed LTSC 2021 or 22H2 with ESU can still get today's (cumulative) updates. So it's obvious that if you use eKB(s) to upgrade LTSC to a higher version, it'll actually shrink its support time to its corresponding GAC (It's not that possible one LTSC version can be upgraded to next LTSC version simply using eKBs in the future). But you can still download packages and install the updates manually (I don't think this can be called "in official support" beacuse the latest updates are not pushed to it automatically). If you do not believe me, you can try it on your own mechines or VMs. I'll keep updating my 25H2-upgraded LTSC 2024 VM till Nov. 2028 Update released.
The main difference here is that you don't need a "modified" eKB to install 25H2 on IoT LTSC 2024, you can just pick the official one and it will work (as IoT LTSC is still officially included in its applicability list) along with all subsequent CUs being offered normally via WU, so in theory you shouldn't have any change to official support period as this time this is not a "frankenbuild".
Now we have learned that installing the 22H2 EP mum files on 2021 LTSC will lead to no ESU updates (and we have been telling people that there can and will be problems with this for ages, but still....) WU doesn't offer the 25H2 EP on 2024 LTSC Windows Update, for the reason that it never should get feature updates (upgrades), whether fake or not. Keep in mind that it always are certain people promoting to do it anyway.
For updated ISO of LTSC IoT, do I need everything in the first post - OOBE, or everything in the second post?
The first post are the monthly patch tuesday released updates, the second post will be the full Updates Overview.