Tha'ts precisely my point. Today, even the weakest machines (think slow, dual-core, soldered-in Intel Atom with just 1GB of RAM) are x86-64. Even most ARM devices now are 64-bit. As for there being 32-bit Win11 builds on Microsoft's internal servers, that doesn't mean those will be distributed to the public. However of course I may be squarely wrong here. I'm just a Windows enthusiast.
For example, I'm sure there were 32-bit internal builds of Windows Server 2008 R2... However they never saw the outside of Microsoft. (Unless a few of them got leaked of course...)
I have been running this build ever since it was first leaked. I found the link here ~15 min after it was posted. I installed and as always linked to my MS account. I have never had a problem. On my MS account it lists my build number correctly, but my OS is listed as Windows 10.
I'd imagine they want Insiders who are running 21996.1 to upgrade to the latest build once it comes out. So I don't think they are going to do anything.
I didn't had an MS account but created one specifically for recording a video review of this leaked build, so far no problems with the account.
Currently on dev build 21996.1, with BitLocker enabled on main OS drive. Do I have to disable the encryption prior to upgrading to 22000 once that drops on thursday?
Same reg location but just change the UseCompactMode to 1 - if not already answered, I'm catching up on posts.. Edit: Guess my vm was having a moment, it wouldn't change with the TaskbarSi entry and only did so when compact was enabled - but now it works with just taskbarsi :/