>the latest that has come out of Redmond. You may not even know about the latest from last week, it's the long-awaited Windows 11 24H2 general release. Among

>the latest that has come out of Redmond. You may not even know about the latest from last week, it's the long-awaited Windows 11 24H2 general release. Among other things, now you get bitlocker by default upon installation, and it automatically encrypts (not only) its own partition, plus any others within the realm of its default autoencryption settings. This can be a little bit of an ordeal to recover from even if you have a Microsoft Account. If you have already made the effort to maintain a Local User instead, it can be accomplished but naturally you wont be able to decrypt using any online credentials. You would barely notice anyway since there are no notifications about bitlocker of any kind, much less autobitlocker with a fury. So you don't actually have any decryption keys at this point either. Other popups will occur though, nothing very useful as usual. Plus when booted to the newly installed W11 24H2 you're an authorized user so you can access your C: volume and every other volume like normal. So you would never guess there's a problem until you boot that PC to some other volume, like one having up-to-date W10 installed. And it wont boot because that whole partition has been stealth encrypted and the undamaged bootfiles no longer recognize it. It can only be accessed when you are already booted to the new 24H2 volume but bitlocker is still not "complete" on any other volumes without a Microsoft Account, so on each encrypted volume there is only an option to turn bitlocker "on" not off. You can muddle through and obtain a local decryption key but it does not work in a straightforward way (and perhaps maybe never the first time), plus decryption takes a bit of time. So it ends up being faster and easier to reformat the encrypted volume and recover the contents from backup. To correct this, action needs to be taken in advance before the installation of W11 24H2 like no Windows before, you must make sure no other disk volumes are exposed and that the install setup process can only "see" the target volume you are intending to install 24H2 onto. Otherwise you really need to use the latest RUFUS app to tweak and adjust the Windows install routine so you can disable things like autobitlocker in your customized USB Windows install device. Before you subject a multipartioned PC to unbridled mayhem like never before. Not just a multibooter. This finally adds up with other creeping challenges to make the latest Windows more fiddly and in need of arcane command-line intervention more so than Linux for the first time. Not like it was since the beginning of Linux up until a week ago. And it's a big leap.