For unsupported hardware types.. check to see if upcoming 22H2 update will be blocked

mackie · Jun 30, 2022

I followed the Registry Editor check in the article and my pc says:

RedReason CpuFms TPM UefiSecureBoot

So the machine will not take the update... according to the article.

You can now check if your PC is compatible with Windows 11 22H2

pietcorus2 · Jun 30, 2022

mackie said:
I followed the Registry Editor check in the article and my pc says:

RedReason CpuFms TPM UefiSecureBoot

So the machine will not take the update... according to the article.

You can now check if your PC is compatible with Windows 11 22H2

Yes , my machine has the same problem !
Any idea HOW (?) to fix this upgrade to 22H2.............?

jimbo45 · Jun 30, 2022

pietcorus2 said:
Yes , my machine has the same problem !
Any idea HOW (?) to fix this upgrade to 22H2.............?

VHDX files and Dism.exe /ApplyImage followed by updating bootloader via bcdboot.exe.

If you fail on CPU simply create a VM with "Virtual CPU" that passes the tests, do your updates , save and then restore to real machine via Macrium or whatever, Update bootloader as well via bcdboot.exe

Cheers
jimbo

pietcorus2 · Jun 30, 2022

" VHDX files and Dism.exe /ApplyImage "....................??
Can you , please, explain HOW (?) this works ?

mackie · Jun 30, 2022

pietcorus2 said:
Yes , my machine has the same problem !
Any idea HOW (?) to fix this upgrade to 22H2.............?

My approach right now is to just sit tight until 22H2 actually comes out in the fall. I'm sure there will be plenty of suggestions, just like before...... some easier than others.

glasskuter · Jun 30, 2022

mackie said:
plenty of suggestions,

Hanging tight is the best approach. As always, smart folks will come up with ways to circumvent Microsoft's restrictions. But IMO, one of these days it can't be done any more. Maybe with 22H2, maybe not. The only reason the workarounds work is because MS is allowing them to work. MS can lock this OS down tighter than a jug any time they want to.

pietcorus2 · Jun 30, 2022

glasskuter said:
Hanging tight is the best approach. As always, smart folks will come up with ways to circumvent Microsoft's restrictions. But IMO, one of these days it can't be done any more. Maybe with 22H2, maybe not. The only reason the workarounds work is because MS is allowing them to work. MS can lock this OS down tighter than a jug any time they want to.

If so , my Win11-adventure is over , have to stay at the last working version...............

RFS · Jul 3, 2022

Wife's PC was not compatible for CPU so it shows RedReason as CpuFms. All other conditions met including TPM 2.0 etc. As the processor was quite old (G3450) decided to do a hardware upgrade with new MB, processor and memory. All working fine now but the registry entry still has the RedReason set. Did not do a re-install of Windows 11.

Anyone know how to correct this without doing a clean install?

glasskuter · Jul 3, 2022

@RFS If I were you I would begin a new thread about this issue in the Hardware section of the forum to get attention. IMO the reason is because you did not do a clean install using a standard iso with no altercations. The install process can see that all requirements are met for 11. This is just another reason to clean install when major components in a system are changed (and you changed a lot) The hardware guys may have a suggestion whether or not the registry value can be arbitrarily changed or if something else needs to be done.

RFS · Jul 3, 2022

glasskuter said:
@RFS If I were you I would begin a new thread about this issue in the Hardware section of the forum to get attention. IMO the reason is because you did not do a clean install using a standard iso with no altercations. The install process can see that all requirements are met for 11. This is just another reason to clean install when major components in a system are changed (and you changed a lot) The hardware guys may have a suggestion whether or not the registry value can be arbitrarily changed or if something else needs to be done.

Yeah - looks like a clean install is needed. Thought I might get away with a repair install, but when I try to mount the ISO image on the second drive, the mount itself fails with BSOD of APC_INDEX_MISMATCH.

Wonder how folks who make smaller changes to become compliant will fare. For example, increasing disk space, activating
TPM etc.

Mark Phelps · Jul 3, 2022

I mentioned in another thread that I updated my old Dell laptop using a 22621.x ISO and after the update, no Windows Updates would work anymore. So, there is more to it than just forcing the 22H2 install on an old PC.

mackie · Jul 4, 2022

Mark Phelps said:
I mentioned in another thread that I updated my old Dell laptop using a 22621.x ISO and after the update, no Windows Updates would work anymore. So, there is more to it than just forcing the 22H2 install on an old PC.

Thanks for posting that.. very informative. I'm not on an insider track, but if what you experienced on your laptop holds true across the board for other unsupported pc's trying to run 22H2, then indeed..... it doesn't bode well.

Superfly · Jul 4, 2022

mackie said:
Thanks for posting that.. very informative. I'm not on an insider track, but if what you experienced on your laptop holds true across the board for other unsupported pc's trying to run 22H2, then indeed..... it doesn't bode well.

Updates work fine on my Thinkpad T61 - no compatibilities in the hardware.

mackie · Jul 4, 2022

Superfly said:
Updates work fine on my Thinkpad T61 - no compatibilities in the hardware.

View attachment 33045

View attachment 33046

On behalf of all unsupported device owners....... thanks for posting that! :)

Bree · Jul 4, 2022

mackie said:
My approach right now is to just sit tight until 22H2 actually comes out in the fall. I'm sure there will be plenty of suggestions, just like before...... some easier than others.

I suspect 22H2 may be released sooner than you expect. My System One has already run the compatibility checks for 22H2 and populated the NI22H2 key with the results - fully compatible (same as it was for CO21H2, the initial release of Win11)

I suspect 2

Bree · Jul 4, 2022

RFS said:
Anyone know how to correct this without doing a clean install?

The NI22H2 key was not pushed to you by Microsoft, it is the results from your Windows running its own compatibility checks. If you delete the whole NI22H2 key then the checks will run again shortly, and this time it should say you are good to go.

jvickers · Jul 4, 2022

I was pretty sure I am eligible for the upgrade, but I had to check just in case. Good to go. :)

Bree · Jul 4, 2022

Mark Phelps said:
I updated my old Dell laptop using a 22621.x ISO and after the update, no Windows Updates would work anymore. So, there is more to it than just forcing the 22H2 install on an old PC.

Are you an Insider? If not that may be why you don't get updates. Once 22H2 gets a public release it should get the public updates, just as 21H2 does now on any unsupported device.

mackie said:
hanks for posting that.. very informative. I'm not on an insider track, but if what you experienced on your laptop holds true across the board for other unsupported pc's trying to run 22H2, then indeed..... it doesn't bode well.

Superfly said:
Updates work fine on my Thinkpad T61 - no compatibilities in the hardware.

I concur with Superfly. I have 22H2 running on a Lenovo Yoga 11e that fails compatibility on three counts, an old CPU, no TPM at all, and a Legacy BIOS/MBR install. You can't get more incompatible than that.....

Despite that it gets every new update through Windows Update.

I have however taken the precaution of enroling it in the Insider Beta channel.

Bree · Jul 4, 2022

Superfly said:
Updates work fine on my Thinkpad T61 - no compatibilities in the hardware.

Cumulative updates should work fine.

If you have a RedReason set in the NI22H2 key what you almost certainly won't see being offered in Windows Update on an unsupported device currently running Win11 21H2 is the Feature Update to 22H2 once it gets its public launch. If you want to upgrade then you'd have to do an in-place upgrade yourself with a workaround to get past the compatibility checks. After thast it should get all the updates as normal.

mackie · Jul 4, 2022

Thanks for clarifying things Bree. As far as performance on your Lenovo Yoga, are you seeing any difference between 22H2 and 21H2?

For unsupported hardware types.. check to see if upcoming 22H2 update will be blocked

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

aka Mama Glass

My Computers

Well-known member

My Computer

Well-known member

My Computers

aka Mama Glass

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

The lunatics have taken over the asylum

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer