@OSVersion And Windows 10

[anonymous]

Been asked to add this so it gets added to Autoit before Windows 10 arrives
Will we be having a reference for Developer Preview as well as Normal Windows 10

ie
WIN_10
WIN_10_DP

[TicketCleanup]

Automatic ticket cleanup.

[anonymous]

also see RtlGetVersion to avoid the requirement of manifestation - as proposed in ​http://www.autoitscript.com/forum/topic/166932-os-version/

[anonymous]

in the same context it would be nice to introduce a new macro "@OSVersionNT" that returns a numeric value the mirosoft way: ​https://msdn.microsoft.com/en-us/library/aa370556.aspx
(e.g. windows 2000 = 500; windows xp = 501; windows 7 = 601; windows 8.0 = 602)

[BrewManNH]

In a follow up to comment #3, why would you want that returned? It's a very untrustworthy way of determining the OS version. Using that you'd never know if you were running Win 7 or Server 2008, for an example, unless you further checked to see if the OS is a server or not.

[anonymous]

as reply to BrewManNH's question in comment no3:
that's the "microsoft way". the underlying "core" (or kernel) is identical for certain client and server os.
601 = win 7 / 2008 R2; 602 = win 8.0 / 2012.

and that's exactly what we developers are interested in - the underlying "core".

it's the information we need to add in our log files (e.g. "Log("OsVersion: " + @OSVersionNT)" and also the information we may use for conditional code execution (e.g. "If(@OSVersionNT > 603)".

[BrewManNH]

You could always just run FileGetVersion("Winver.exe") and get the same basic information. On my Windows 7 SP1 system it return 6.1.7600.16385. The 6.1 corresponds to the 601 in the table, the 7600 is the build number.

[guinness]

This is set to complete for the part where WIN_10 was added to @OSVersion macro.

[TicketCleanup]

Automatic ticket cleanup.