after an advanced search timebomb was hardcoded ( switching server insider certificate with server 2022 rtm ) used nsudo and the slmgr.vbs -rilc features
The expiration date writing doesn't matter, the permanent activation popup doesn't matter, the only way to really check is running with a future date and see what happens, like I did three months ago https://forums.mydigitallife.net/threads/server-ip-ltsc-builds.84158/page-13#post-1753931
That's a different matter. Such old builds, when expired won't boot at all. All relevant files are (were) signed with a certificate that expired on the expiration date. Later builds (say Server 2016 TP4) will boot even in 2040, but retain the timebomb, there is just matter of using my "SKUwitch" technique. Server 11 looks different again, it's the same as above, but looks like the expiration date is hardcoded somewhere, so SKUwitch is enough to run it indefinitely, but not to clear the expiration date, just a cosmetic thing. Windows is a moving target, never think that 10 or 20 years of experience is enough to settle the matter.
Code: expired... Preparing the SVF(SFX) REPO + VHDX/FOD Mirror! Added all checksums: https://forums.mydigitallife.net/threads/server-ip-ltsc-builds.84158/page-16#post-1768790