I have the same issue and submitted feedback at https://aka.ms/AAd0x8e. I also started a discussion at https://answers.microsoft.com/en-us/insider/forum/all/windows-11-build-2200051-after-every-reboot/e0ec1a8d-3807-4069-893f-66dfe5aa8fd3.
Upvoted
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Live in W.U.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I have the same issue and submitted feedback at https://aka.ms/AAd0x8e. I also started a discussion at https://answers.microsoft.com/en-us/insider/forum/all/windows-11-build-2200051-after-every-reboot/e0ec1a8d-3807-4069-893f-66dfe5aa8fd3.
Upvoted
I have the same issue and submitted feedback at https://aka.ms/AAd0x8e. I also started a discussion at https://answers.microsoft.com/en-us/insider/forum/all/windows-11-build-2200051-after-every-reboot/e0ec1a8d-3807-4069-893f-66dfe5aa8fd3.
Same here. Someone started another thread about it.
@Eddie,
My non-compliant Dev laptop required a total clean install. Was not aware of the cutoff date at the time clean installing 21390. This device was in Dev channel for atleast 5yrs or more.
Any suggestions, please private message if necessary. Prefer not to use a forced method. It is currently stuck in RP due to the cutoff date. The VMware vm is upgrading from 21390 to 22000.51
Regards,
Hi Johnny,
Have you seen this article ? How to download and install Windows 11 Insider builds on unsupported hardware - Neowin
Regards