I would imagine that once the Microsoft Windows 10 product becomes more stable (less of a preview, and more of a pre-release beta), IBM will release a new IEM client that correctly identifies the new OS.
I’ve read that the actual version was finally going to break the 2-digit limit and internally known as “10.0” or somesuch, but that a shim was going to be provided such that executables that do not mark a particular compatibility flag in their manifest would see a “compatible” version instead of the actual OS version.
Sounded like a repeat of their “Fix DLL Hell via WinSxS” solution - add more layers so application developers can be undisciplined.
My understanding is that Windows 10 returns version 6.4 to legacy applications, and version 10 to non-legacy applications that are using newer APIs or something like that.
Actually its worse. The 6.4 WINVER was in older revisions of the previews for Windows 10 but its now 10.0.
As of 8.1 (WINVER 6.3) Microsoft decided that the GetVersionEx function ( https://msdn.microsoft.com/en-us/library/windows/desktop/ms724451(v=vs.85).aspx ) would no longer return you the correct value if you didn’t have an appropriate manifest with the executable saying you ran on that platform. This is problematic for us and the function basically never returns the right result after Windows 8 anymore so we went around it the same way as many others online did (easy to search for ways around it) as we need to have agents try and return the right values so that we don’t have a new OS showing up as Windows 8. That being said something else seems to have changed or broken in Windows 10 so we had to refine that.