Windows Insider Dev Channel and Builds

[ChristopherW23]

Regarding the latest build 22458.1000.
Seems like this is the first build that requires the TPM hardware option.
I have not added this to the virtual machine until now and the install did not progress like previous updates.
Once I installed the TPM Chip to the VM all was well again.

Also I don't have any option at present to move from the DEV channel to Beta or Release Preview.
Any suggestions about where this is going with Microsoft once the full windows 11 upgrade is pushed to windows 10 users?

Comments welcome.

 

[ChristopherW23]

You're right that this is the first build that requires TPM even in virtual machines. The same is true for the latest Beta Channel build, though it seems like it will only affect you if you update from a pre-22000.xxx build. Cumulative updates still seem to work without TPM.
This is what Microsoft wrote in the blog posts announcing the new builds: „This build includes a change that aligns the enforcement of the Windows 11 system requirements on Virtual Machines (VMs) to be the same as it is for physical PCs. Previously created VMs running Insider Preview builds may not update to the latest preview builds. In Hyper-V, VMs need to be created as a Generation 2 VM. Running Windows 11 in VMs in other virtualization products from vendors such as VMware and Oracle will continue to work as long as the hardware requirements are met. For more details on the Windows 11 system requirements - see this blog post here."

The good thing about this is that MS still doesn't seem to enforce an officially supported processor. Having to use TPM is annoying when moving a VM to a new Mac, but otherwise no big deal.

You can't move to the Beta Channel because the Dev Channel builds are higher. There are options, though. You could create a new VM with a 22000.xxx build and join the Beta Channel or you can use the offline enroll script.

Thanks for the information, I guess the question is what is the end game here.

Running Windows 11 on a M1 Mac under parallels may require DEV channel level of support or will changing out to regular builds provide the same support?

I am not sure which is the best way to progress. I am thinking of sticking with the DEV channel until the public release of Windows and upgrade an older saved VM version of windows 10, then see how it goes.

The good thing about parallels is that you can have these saved versions of Windows and update as required. Have a DEV version and Full public version of windows.

 

[BradB7]

I have the TPM enabled and have been happily sitting in the Beta channel vs the Dev channel since the 17.0.1 update allowed the ability to get back into the Insider Preview and switch from Dev to Beta. No issues here other than what MS has said about not "supporting" Windows on Apple Silicon. My question is a bit different. Since I'm running with a Windows Pro license I bought specifically for 10 ARM (then 11) on my M1 MBP, will MS be rolling Insider Previews the ability to change to the standard release, or will we have to reinstall Win 11 from an ISO? (I mean this apart from where MS lets us currently run on an M1). I'm talking in general. Is this how Insider Previews have worked in the past for upgrading to the release candidates?

 

[BradB7]

In the Beta and Release Preview Channels you can choose to stop getting Insider builds and that should let you update to the final release once it will be available. At least in theory. We were never able to do that with Windows 10 because we needed the Dev Channel builds.

Have you switched over to the Release Preview Channel from the Dev or Beta yet? (I've been sitting in the 'stable' beta with only minor updates (like MS Store apps or MS Defender) since a couple weeks ago. I'm curious if anyone on build 22000.194 has switched to Release Preview Channel and received the notification about Windows 11 upgrade (e.g. How to get the free Windows 11 upgrade early - The Verge ) ? Since we are "not in a supported scenario" (at least from MS), has anyone seen this? BTW...I "am" aware that build 22000.194 is likely that being released in several days.

 

[SWANDY]

I just switched to the Release Preview Channel and didn't see that message. That might be because I'm already running a Windows 11 build from the Beta Channel, though. You probably need to run Windows 10 to see it.

I did the same thing - though I also had to first turn off receiving developer updates and then switch off the BETA channel. But I also did not see the option screen shown in the article. I agree it's probably because we are in Windows 11 already.
Almost tempted to find my backup of the Windows 10 VM before it updated itself to Windows 11 and see if it will work. But have a feeling because we are dealing with the ARM versions of Windows, don't know if it is worth the effort. Anyone who is still running Window 10 for ARM able to get the update to the release version of Windows 11 for ARM?

 

[BradB7]

I just switched to the Release Preview Channel and didn't see that message. That might be because I'm already running a Windows 11 build from the Beta Channel, though. You probably need to run Windows 10 to see it.

@MichaelH63 That's what I was thinking. If we are on the build that will be used for the release, we won't see the "popup" notification.

 

[BradB7]

@MichaelH63 and @SWANDY I noticed how the Windows Update says "Windows 10" too when you switch to the Release Preview Channel. But, yeah, we're already *in* Windows 11. I guess just a few more days to wait folks and see what happens come Oct. 5?