I I uninstalled that junk before it uninstalled itself on Beta Channel. It’s like breaking up with your GF before she does. Little self respect earned. Haha
I believe Android Apps will not be available in the final release of Windows 11. It will become available in the next update of Windows 11.
Not sure if this is the place to ask but does anyone know why TPM2.0 isn't enabled by default if it has been around for 5 years? I have a brand new Gigabyte motherboard and Ryzen 7. Had to go into BIOS to flip it. Not something your average user wants to do- and shouldn't BIOS is scary.
I don't see why they wouldn't. Of course they will have a focus shift with whatever build is newest with changing around ui and apps. They will shift bug fixing updates to the ones on the beta channel. It's hard not to sound like I'm making definitive predictions. I'm still just making educated guesses.
So now that this build's RTM debate is over by the announcement of future builds, what can we expect to see in a build when we actually have an RTM build pushed to an insider ring? Well for one thing all of the keys will be Win11 keys. Your old win10 keys won't work. It will probably use the default win11 key for whatever sku is installed and rely on the person's ms account permission. When this comes out we will start to look at KMS activation. I'm not saying it will definitely be updated, but it could. Direct Storage will be a feature that will be able to be used although there probably won't be any actual games that support it yet. Any attempt to use dism on these builds will probably require a new ADK dism tools. This one is like kms in that it is not definite. It depends if they added any feature or changed anything. All of the file dates will have the same build date. The registry will no longer refer to Windows 10 and will instead refer to Windows 11 Am I saying that I think they won't release this without any CU at all? No that's not what I'm saying. They just have a habit of keeping it minimal when they do, especially on a new OS. They're using the Insider program as intended for free advertising and help deciding ui features. If they do release it with a cu it will be the lowest common denominator that fixes the issue in question. They won't just keep patching an old build forever and starting from a build that is fundamentally unsuited for release.
MS seems to be playing hardball now, I had Offline Enroll installed into the Beta program. WU found 22000.100 and downloaded it, when it went to install, it crapped out with "No TPM 2.0 module found" or something like that. My MB has a TPM slot and a Ryzen 7 CPU but I'm not paying $200 for a $10 chip so I'm stuck on Windows 10 I guess.
This is only when you go from 21996.1 or lower to 22000.xxx. Try to use this registry mod by @abbodi1406 https://forums.mydigitallife.net/th...fications-overview.83744/page-13#post-1677184 And rerun WU. Or create a fixed 22000.100 ISO and upgrade by ISO.
No offence, but there's no need to further insist with your idea at this point. 22000.100 shifted from Dev to Beta, with Dev Channel now moving to "very early builds" once again (probably co_refresh branch instead of co_release) which won't be "aligned" to what users will receive with initial Windows 11 release of this fall anymore (those are official words by Microsoft, not mine). This just means 22000.xxx is the final full compiled build for Windows 11 release (as both Beta and RP Channels won't receive new full builds) and where .xxx will just be a specific CU which will be released for everyone on launch day in October (installing it on top of a clean installed 22000.1 or just clean installing 22000.xxx with .xxx integrated into the ISO will be the same identical thing in the end). Now, you can call 22000.1 or 22000.xxx RTM or not as you prefer, but that's what's gonna happen for sure now, so better deal with it rather than being delusional waiting for another full build for Windows 11 initial release.
I tried to manually install the .100 update on top of a fresh 22000.1 install and it crapped out, wouldn't let me install it..
DISM can't handle psf+cab updates, use W10UI_10.5+ With PSF support. Put the psf and cab file next to the cmd and run.
Let it go. It's not the RTM build and never was. This idea that they would patch it into the eventual RTM version was just an idea. It was not based on any evidence.
OT: @murphy78 are you "enough old" to remember the name of leaker of Windows 8 KMS? I remember many of his posts where sometimes he shown the new builds stuff. P.S: In truth I remember also when when, one day, he called me cancer.