Obviously bit per bit is an hyperbole that cant be taken literally. Assume you have an hypothetical windows image that includes server and client packages, you can have a "bit per bit identical" server and client images, that behave very differently depending only on the serial number. In short there is no point in comparing Enterprise LTSC and IoT (or anything else). Especially in 11 flavor they are two different SKU with their own set of kernel policies and customizations.
I tried to modify win and create install.wim and replace it in the iso so when the time comes to install the error will be new protection in the installer that does not allow the use of install.wim esd from modified windows?
There is no new link, only the one we already have for days now, nothing new has appeared. It was fine offline. https://forums.mydigitallife.net/th...nary-dev-ge-release.88220/page-4#post-1831387
Just an FYI folks, received a permanent ban on COD MW3 for using "unauthorized software and manipulation of game". There was no unauthorized software on LTSC than the normal stuff. Just giving folks a heads up.
There is a chance this is because you're running a version of Windows 11 that is still considered "dev/canary" by game and anti-cheat developers, meaning you're running a version of Windows 11 that has kernel changes and that is something they don't like.
I have a PC without TPM and Secure boot, only UEFI. I try to do a fresh install of the LTSC version using Rufus and trick to bypass TPM and secure boot. At start of setup, I got the message "You can't install on this machine". I made an IoT LTSC again with Rufus and no problem. Install complete and activate with MAS. I got all drivers, and an update for .Net 3.5.