Hi, Is it safe to use the Insider Preview ISO and consider the 26100.1150 build as official "final" release, ..even though it will be officially released later on in 24H2 with a different build 2600.XXXX? In other words, the Insider preview build is stable enough to use with ongoing updates and will be classed as "General Availability" later in 2024?
It is not reallty at Insider preview level, MSFT just keeps naming them IP till it goes public, consider these 26100.xxxx "IP" ISOs early access ISOs, the ISO that will go public will just contain later LCU/Updates. Real Insider Preview ISOs like canary channel, will enroll you to the insider channels, these 26100.xxxx ISOs don't and for ARM64 devices it is already public and the updates are on catalog (MSFT never put IP level updates on catalog) and WU (without IP enrollment).
Thanks for great explanation i guess they disabled removal of RTM packages / components to solve 0x800F0989 / 0x800F081F errors mostly
Is 26120 dead in the water now? Windows thinks the last 2 CUs are compatible but they fail to install. You can build 26120.1150 but if you try to upgrade to it, the installer wont let you keep anything.
@Enthousiast do you have time to help.? am trying to figure out, what causes my lockscreen to glitch. when windows boots and when i press enter when i click enter . i assume you have a fest pc. so want to ask if you could run some test.?
For me, once you enable WMIC via FOD, it sticks after doing monthly LCU installs. Apparently It is disabled on clean installs. Aug. will be clean install for me, so we'll see if the FOD can be installed. See here.
i removed it from my second pc, its way to vanilla for me, running beta on both pc's lacks features that im used to and the new features in 24h2 i have no use for HDR isnt my thing ...i like true to life colors
Can the TPM requirement be somehow enforced so that common workarounds like the option in Rufus won't work ?
You mean MSFT fixed the bypass method? For upgrades they make it harder and harder but for boot UFWS and labconfig boot.wim reg still works, for upgrades we are working on a new working method for the Win 11 Boot And Upgrade FiX KiT