Windows 11 kicked me out of WIP on Windows 11.

Anonymous
2021-09-01T13:08:05+00:00

Hi all.

Today I went to Settings > ... > Windows Insider Program page.

There I was asked to restart the PC.

After I restarted, I saw that I was left out of the Windows 11 Insider Program.

Now I am asked to install Windows 10 and then rejoin the Windows Insider Program Release Preview Channel.

So I understand now it is just about time to say good-bye to my Insider Colleages on Windows 11.

Windows Insider program | Program announcements and registration | Registration, enrolling, and unenrolling

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.

0 comments

107 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-09-02T20:35:10+00:00

    The CU has come through on my non compliant Dev desktop, as said it would.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-09-02T20:39:14+00:00

    The CU has come through on my non compliant Dev desktop, as said it would.

    Sorry about that. Yeah, I'm left with only one compliant device even though the CPU isn't supported.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-09-03T17:33:35+00:00

    Suggest for you to hop on the VMware or Hyper-V bandwagon. The virtual machine is Legacy on 10 yr old Legacy desktop, an i7 2600.

    Hi Johnny,

    I installed Beta Build 22000.132 on Hyper-V. UEFI install.

    I don't know where to go from here. I have a couple of questions to you.

    1. How to activate the VM install ? Do I need a new Windows 10/8/7 product key ? I had a HP notebook. It had a product key on the sticker. Can I use that ? The notebook has no longer the pre-installed Windows build on it. Not used.
    2. Can I use my Microsoft account info here in VM as well ?

    If you have opinions on above questions, I appreciate your opinions.

    Regards

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-09-03T17:54:55+00:00

    Later tonight when watching movies, will see what happens with the non-compliant laptop using that script if it takes through WU.

    Hi Sibro,

    WU did come through with the upgrade using script. Once it checked PC, blocked due to no TPM, CPU and Secure Boot were listed. I could bypass the TPM and CPU in different HKEY_LOCAL_MACHINE key but could not get around the Secure Boot yet with WU. Have to work on this one, MS changed something here.

    ""BypassSecureBootCheck"=dword:00000001" in LabConfig key does not bypass with 22449.

    Ended up using the ISO for in-place upgrade. Had to copy the setup files to SSD and rename the Sources dll file to .bak to get it to upgrade. This non-compliant laptop is running 22449.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-09-03T20:17:20+00:00

    Later tonight when watching movies, will see what happens with the non-compliant laptop using that script if it takes through WU.

    Hi Sibro,

    WU did come through with the upgrade using script. Once it checked PC, blocked due to no TPM, CPU and Secure Boot were listed. I could bypass the TPM and CPU in different HKEY_LOCAL_MACHINE key but could not get around the Secure Boot yet with WU. Have to work on this one, MS changed something here.

    ""BypassSecureBootCheck"=dword:00000001" in LabConfig key does not bypass with 22449.

    Ended up using the ISO for in-place upgrade. Had to copy the setup files to SSD and rename the Sources dll file to .bak to get it to upgrade. This non-compliant laptop is running 22449.

    Hi Johnny, hope you enjoyed your movies.

    dword should be just 1 without zeros. I also ended up using an ISO to update the Raspberry, all ok.

    After 3 failed attempts the Laptop was struck by the taskbar fiasco, restore .168 backup, waited a bit and finally updated to 22449, is the only amd64 device I have left on Dev

    Was this answer helpful?

    0 comments