Windows 10: A look in the Registry reveals if your PC is compatible with Windows 11 version 22H2

Want to know if your Windows 10 or 11 devices are ready for the upcoming Windows 11 feature update? You may look in the Registry to find out, instead of using Microsoft's PC Health Check app, or any of the third party programs that have been created for the purpose.



While it may sometimes be necessary to run these products, for instance on machines that limit Telemetry or have not been updated in a while, checking the Registry is all that is required on most Windows machines.

Here is how this works:

1. Open the Windows Registry Editor on the PC. You may do so by opening start, typing regedit.exe and selecting the Registry Editor result from the listing. Using Windows-R to launch it from the run box is also an option.
2. Paste the following path into the address bar at the top: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators\
3. Open NI22H2 to check the compatibility of Windows 11 version 22H2. Future versions of Windows 11 will use different keys, e.g. NI23H2 for the 2023 feature update.
4. Find RedReason on the page and check it:
   1. If its value is NONE, there are no compatibility issues that prevent the upgrade to Windows 11 version 22H2.
   2. Any other value hints at compatibility issues. You may get multiple values listed, e.g., "TPM UEFISecureBoot", to indicate multiple compatibility issues.
5. The String SystemDriveTooFull hints at another potential issue. A value of 0 indicates that there is enough storage space available for the upgrade. If you get 1, storage space is not sufficient.

The Registry key should be available on most Windows 10 and Windows 11 21H2 installations. It is no longer available for Windows 11 version 22H2 machines. Windows 10 machines may show other compatibility keys, e.g., 21H2 for the upgrade to Windows 10 version 21H2 if an older version of the operating system is installed.

Closing Words


The only upgrade that is problematic from a hardware compatibility point of view, is the upgrade from Windows 10 to Windows 11. There may be edge cases, where hardware is changed or certain features are turned off, which may block the upgrades because of compatibility issues.

Now You: do you run Windows? Which version, and do you plan to upgrade to a newer version? (via Panu Saukko)

Thank you for being a Ghacks reader. The post A look in the Registry reveals if your PC is compatible with Windows 11 version 22H2 appeared first on gHacks Technology News.

read more...

 

Preview of Windows 11 version 22H2 now available

Read more: Preview of Windows 11 version 22H2 now available | Windows 11 Forum

 

Preview of Windows 11 version 22H2 now available

Consumers too?:

Windows 11 Insider Release Preview Build 22621 (ni_release) Version 22H2 - June 7 | Windows 11 Forum

 

3DMark 11 v1.0.4 Released, Now Fully Compatible with Windows 8

Futuremark updated 3DMark 11 to version 1.0.4, which makes the benchmark fully compatible with Windows 8. The update also addresses other compatibility issues and a few uncommon bugs. Benchmark scores are not affected and scores from this new version can be compared with scores from the previous version 3DMark 11 v1.0.3.





DOWNLOAD: 3DMark 11 v1.0.4
Improvements:

• Keyboard focus is no longer checked during the demo or when running the benchmark in a loop. Note that if the display switches to the desktop due to a popup window during the benchmark, the run will still be aborted as the display mode is no longer the same.
• 3DMark 11 now remembers the last custom resolution used.
• GPU count detection for multi-GPU systems is now correct even when SystemInfo is explicitly disabled.
• 3DMark 11 will now prevent Windows from entering Sleep during the test.
• The license key is now reset when the benchmark is reinstalled, allowing removal of invalid keys.

Compatibility:

• SystemInfo updated to version 4.15 for full Windows 8 compatibility.
• Updated DirectX redistributable.
• Now using static Visual C++ 2010 runtime libraries to fix rare installation issues on some systems.
• Removed dependency on EvaDotNet.dll and EvaDotNet.DirectX.dll for GPU enumeration to fix compatibility issues with some systems.

Bug Fixes:

• Fixed display initialization code that caused "SetFullscreenState failed: DXGI_ERROR_NOT_CURRENTLY_AVAILABLE" errors on some systems.
• Fixed several memory and texture leaks, improving stability during very long looping runs.
• The HUD timer no longer rolls over if a single test takes more than ten minutes. (Yes, this could happen during the Combined Test on some low end DirectX 11 cards.)

Professional Edition Only:

• Fixed submitting saved files to 3dmark.com from the command line.
• Image Quality Tool no longer gives a cryptic error if the output directory does not exist.