[Question] Expiration Date and timebomb mehanism in Windows 11 24H2 build 26100.1
Can we know exact expiration date of this build since if there is no expiration date told for this build, insiders could easly end up with unbootable device due to expired build of non-production build of Windows. And is this security mehanism still active or it's turned off for these builds so that insiders who joined Dev/Canary channels to test 24H2 version will be able to migrate to more stable channels in the future or even if they want, to decide to wait for final production release and upgrade to that version while perserving all settings, user data and apps since upgrading to the current build number and higher build numbers are possible with this option - it's only impossible from higher to lower builds without clean installation of WindowsWindows 11 24H2 issues that needs to be known and be fixed before it gets released officialy to RTM
The build 26100.1 that was supposed to be released to RTM first (after some little workout) it doesn't work with all apps and games yet - it requires more fixes before this version gets published to the air - for example, Roblox when gets executed it shows only white screen as soon the game has been opened and doesn't do anything - it doesn't even crash the app - it stays opened but with white color on the whole screen of the app so fixes are not yet fully applied for some issues in 24H2 build. It should get more extended time for better fixes and development before it gets released to RTM and in public I will provide logs as an example of how Roblox reacted in this build (it could be useful for enginners to work on it before it gets released to users and RTMs) Thanks in advance for your kind and good work and I appreciate the time spend in testing 24H2 build to the end of it's development cycle (that means that I'm not leaving before it gets finished completely)