Jonathan,

>It appears that the OS function needs to be updated to correctly report 
>Windows 10:

That already happened about 9 months ago. Xbase++ Build: 2.00.575, which 
was released on 02/24/2015, and all prior Xbase++ versions would report a 
Windows 10 machine as: Windows 8 06.02 Build 09200.

Starting with Xbase++ Build: 2.00.623, which was released on 08/17/2015, the 
same Windows 10 machine is reported as: Windows 10 10.00 Build 10586.

Updating to the latest official Xbase++ version, 2.00.685, released on 
04/28/2016, or any version after 2.00.575, should fix this issue for you.

The Windows 10 "Version 1511" (and "Version 1507") naming convention, which 
refers to the planned release dates of those official Windows 10 versions 
(July 2015 for the original "Threshold 1" release, and November 2015 for the 
"Threshold 2" update), is apparently not related to the OS version number. 

The latest/current release version/build of "Version 1511"/"Threshold 2" is 
(according to Wikipedia) 10.0.10586.318, and the latest preview (of the 
upcoming Windows 10 Anniversary Update "Redstone 1") is 10.0.14342.

I'm not able to test this right now, but it seems that the Xbase++ OS() 
function doesn't differentiate between the new sub-build numbers, like 
10586.0 through 10586.318, and won't report the (decimal) digits after the 
period in the build number. But I'm not sure if those digits are even of 
any significance to the average user.

Hope that helps.

Andreas

Andreas Gehrs-Pahl
Absolute Software, LLC

phone: (989) 723-9927
email: Andreas@AbsoluteSoftwareLLC.com
web:   http://www.AbsoluteSoftwareLLC.com
[F]:   https://www.facebook.com/AbsoluteSoftwareLLC