@Castorix31 , API or not that distinction doesn't matter in this case. There is no reason to believe that the major/minor is being misreported by some parts of the OS in this case.
While some APIs can lie to you (like GetVersionEx), all Microsoft's tools that display major/minor version agree including WMI (Win32_OperatingSystem object), winver, and msinfo. More importantly, Microsoft's own download sites also agree the major/minor is 10.0 for build 22000. When you download the Windows 11 Insider SDK it is listed as something like 10.0.22000.168-preview. You can view version info on the 'Details' tab of C:\windows\System32\kernel32.dll and see it clearly reports a 10.0.22000.x version for Beta channel (track scheduled for Oct 5th release).
22000 is supposed to be major/minor 10.0 at this point based on all those data points above. The questions are:
* Will 10.0 be used for the October 5th Gold release based on build 22000 (seems likely at this point)?
* Will Win32 developers be given a documented way to differentiate between Windows 10 and 11, or report compatibility through the manifest?
* Will content in the Windows 11 registry be updated to reflect the OS is actually Windows 11 instead of Windows 10?
Ideally Win32 developers don't have to scrape strings from WMI objects, call into Windows Runtime Libraries, spawn a process and scrape text, or other heavier weight options to clearly identify what OS we are running in. At this point it seems like checking build >= 22000 is the only light-weight option we've been given, and it's not clear to me if that is a future-proof solution.