Upcoming 23H2 update.

If Microsoft does not allow non compliant users to upgrade to 23H2, then why would they put this code on THEIR website? Microsoft doesn't mention anything on this page about updates. Maybe there is a reason for that... I am prepared to go back to Windows 10 but I prefer Windows 11. Any thoughts on their code and updates?

If you choose to install Windows 11 on a device that does not meet these requirements, and you acknowledge and understand the risks, you can create the following registry key values and bypass the check for TPM 2.0 (at least TPM 1.2 is required) and the CPU family and model.

Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup

Name: AllowUpgradesWithUnsupportedTPMOrCPU
Type: REG_DWORD
Value: 1

Upcoming 23H2 update.

asl93e said:

If Microsoft does not allow non compliant users to upgrade to 23H2, then why would they put this code on THEIR website? Microsoft doesn't mention anything on this page about updates. Maybe there is a reason for that... I am prepared to go back to Windows 10 but I prefer Windows 11. Any thoughts on their code and updates?

Click to expand...

Welcome to Eleven Forum.

An unsupported device gets all all the normal updates through Windows Update, except that it won't be offered the feature update to the next version. For that you'll need to do an in-place upgrade with an ISO with the workarounds to skip checks, as I had to do for my System Two to upgrade from 21H2 to 22H2.

I'm also able to run all the latest Insider builds (now saying they are '23H2') on another unsupported device, so it looks like that will continue to be possible when 23H2 get its public release. Unlike the public build, the Insider builds do get feature updates in Windows Update. The Canary build gets a new one almost every week, though they won't install without employing a workaround.

Easier to DL from Microsoft then use Rufus to create a USB with the remove TPM stuff

Bree said:

Welcome to Eleven Forum.

An unsupported device gets all all the normal updates through Windows Update, except that it won't be offered the feature update to the next version. For that you'll need to do an in-place upgrade with an ISO with the workarounds to skip checks, as I had to do for my System Two to upgrade from 21H2 to 22H2.

I'm also able to run all the latest Insider builds (now saying they are '23H2') on another unsupported device, so it looks like that will continue to be possible when 23H2 get its public release. Unlike the public build, the Insider builds do get feature updates in Windows Update. The Canary build gets a new one almost every week, though they won't install without employing a workaround.

Click to expand...

I was under the impression upgrading from 22H2 to 23H2 will be installed via a simple and quick Enablement Package?

Windows 11, version 23H2 will be available as an enablement package​

The upcoming Windows 11, version 23H2 shares the same servicing branch and code base as Windows 11, version 22H2. What does it mean for you? If you're running Windows 11, version 22H2, it will be a simple update to version 23H2 via a small enablement package (eKB). Do you remember updating from Windows 10, version 1903 to 1909? Or how you've managed recent updates beginning with Windows 10, version 20H2 through 22H2? It will be that simple. Moreover, since both versions share the same source code, you don't need to worry about application or device compatibility between the versions.

Dirtyflash said:

I was under the impression upgrading from 22H2 to 23H2 will be installed via a simple and quick Enablement Package?

Windows 11, version 23H2 will be available as an enablement package​

The upcoming Windows 11, version 23H2 shares the same servicing branch and code base as Windows 11, version 22H2. What does it mean for you? If you're running Windows 11, version 22H2, it will be a simple update to version 23H2 via a small enablement package (eKB). Do you remember updating from Windows 10, version 1903 to 1909? Or how you've managed recent updates beginning with Windows 10, version 20H2 through 22H2? It will be that simple. Moreover, since both versions share the same source code, you don't need to worry about application or device compatibility between the versions.

Windows client roadmap update: July 2023

Get the latest lifecycle updates for Windows 11, version 23H2 and Windows 10 IoT Enterprise LTSC 2021.

techcommunity.microsoft.com

Click to expand...

That's what MS are saying, and enablement packages install just like a CU so there should be no workaround needed.

Whether it gets offered in Windows Update on an unsupported device is another matter. Windows Update runs its own compatibility checks in advance of the release of each new version, whether a full feature update or by enablement package. This is stored in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators. If there is anything other than 'none' in the RedReason then WU will not offer the update to the next version.



Fortunately Brink usually finds a direct download link for the Enablement Package, so we should still be able to install it.

Bree said:

That's what MS are saying, and enablement packages install just like a CU so there should be no workaround needed.

Whether it gets offered in Windows Update on an unsupported device is another matter. Windows Update runs its own compatibility checks in advance of the release of each new version, whether a full feature update or by enablement package. This is stored in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators. If there is anything other than 'none' in the RedReason then WU will not offer the update to the next version.

View attachment 69502

Fortunately Brink usually finds a direct download link for the Enablement Package, so we should still be able to install it.

Click to expand...

Mine has 'TPM' in the RedReason. If necessary I'll just enable it in BIOS to do the 23H2 upgrade (assuming it won't allow the enablement package).

Bree said:

Welcome to Eleven Forum.

An unsupported device gets all all the normal updates through Windows Update, except that it won't be offered the feature update to the next version. For that you'll need to do an in-place upgrade with an ISO with the workarounds to skip checks, as I had to do for my System Two to upgrade from 21H2 to 22H2.

I'm also able to run all the latest Insider builds (now saying they are '23H2') on another unsupported device, so it looks like that will continue to be possible when 23H2 get its public release. Unlike the public build, the Insider builds do get feature updates in Windows Update. The Canary build gets a new one almost every week, though they won't install without employing a workaround.

Click to expand...

With apologies to the OP for going off topic slightly.

@Bree On a CPU incompatible HP laptop we were originally allowed to upgrade from Win 10 Dev to Win 11 Dev to Canary. I'm still getting the updates through WU without having to do anything. Maybe a reg setting? I don't know. Interesting though.

BrianInEngland said:

Mine has 'TPM' in the RedReason. If necessary I'll just enable it in BIOS to do the 23H2 upgrade (assuming it won't allow the enablement package).

Click to expand...

Mine has CpuFms. Ryzen 7 1800X.

Bree said:

That's what MS are saying, and enablement packages install just like a CU so there should be no workaround needed.

Whether it gets offered in Windows Update on an unsupported device is another matter. Windows Update runs its own compatibility checks in advance of the release of each new version, whether a full feature update or by enablement package. This is stored in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators. If there is anything other than 'none' in the RedReason then WU will not offer the update to the next version.

View attachment 69502

Fortunately Brink usually finds a direct download link for the Enablement Package, so we should still be able to install it.

Click to expand...

I'm curious, can the RedReason registry key data be modified/edited to indicate " none "?

Dirtyflash said:

I'm curious, can the RedReason registry key data be modified/edited to indicate " none "?

Click to expand...

The RedReason is just the most easily recognisable of the items in that key. There are 37 items in my compatible machine's NI22H2 key, at least seven of which seem to be related to 'yes/no' upgrade compatibility tests. Then there are at least three different timestamps. I'm not sure if it would be possible to make all the right changes without corrupting the key (and very likely triggering a re-run of the tests).

Bree said:

The RedReason is just the most easily recognisable of the items in that key. There are 37 items in my compatible machine's NI22H2 key, at least seven of which seem to be related to 'yes/no' upgrade compatibility tests. Then there are at least three different timestamps. I'm not sure if it would be possible to make all the right changes without corrupting the key (and very likely triggering a re-run of the tests).

Click to expand...

I have the Dell 5675 motherboard that only supports up to Ryzen 7 1800X cpu. My wifes computer is a 5676 which supports Ryzen 7 2700X which of course is compliant. I cloned her Windows 11 drive and put it in my computer as they were identical except for the CPU. It works fine, but Microsoft has already made the changes to reflect non compliance in the NI22H2 key in my computer.

asl93e said:

I have the Dell 5675 motherboard that only supports up to Ryzen 7 1800X cpu. My wifes computer is a 5676 which supports Ryzen 7 2700X which of course is compliant. I cloned her Windows 11 drive and put it in my computer as they were identical except for the CPU. It works fine, but Microsoft has already made the changes to reflect non compliance in the NI22H2 key in my computer.

Click to expand...

A RedReason in the ...\TargetVersionUpgradeExperienceIndicators\NI22H2 key doesn't prevent you from upgrading with an ISO and a workaround, it only stops you being offered the upgrade through Windows Update. You should have no problems with the cloned 11 on your PC, it will get all the same cumulative updates as your wife's supported device.

Microsoft to force-push 23H2/22H2 update as Windows 11 21H2 end of support date nears​

Wolfzz said:

Microsoft to force-push 23H2/22H2 update as Windows 11 21H2 end of support date nears​

Microsoft to force-push 23H2/22H2 update as Windows 11 21H2 end of support date nears

Microsoft has issued a reminder today about the upcoming end-of-support date for Windows 11 21H2. Alongside that, the company has also stated that it will force push 22H2 or 23H2 on such PCs.

www.neowin.net

Click to expand...

There's nothing new in that. It has been the way for every edition of Windows 10 since the first version 1507 reached its end of support. It's usually about two to three months after end of support, see my post here for an example:

Bree said:

I have deliberately kept a Windows 10 Pro VM on 21H2 to see just how long it would be before Microsoft would force the 22H2 update. Last week it was still showing as an optional update.... Today it has become a mandatory update.

Click to expand...

Windows 10 version 21H2 end of servicing on June 13, 2023 - post #4

I enabled the TPM in BIOS, rebooted and the RedReason still shows as 'Tpm'
Guessing that's because it hasn't tried to validate again for a new build?

BrianInEngland said:

I enabled the TPM in BIOS, rebooted and the RedReason still shows as 'Tpm'
Guessing that's because it hasn't tried to validate again for a new build?

Click to expand...

What happens if you type TPM.MSC into a search box?

Senecio said:

What happens if you type TPM.MSC into a search box?

Click to expand...

TPM is working. I did a Check for Updates and the RedReason has changed to None now. Just needed to re-validate I guess.
Interesting that 22H2 has an 'expiry' date of October 14th, could be the 23H2 release date