WAD ver /r does not detect Win 10B10166

[fromano]

running TCMD x64 on Windows 10

[C:\Program Files\JPSoft\TCMD18_x64]ver /r & cmd /cver

TCC 18.00.27 x64 Windows 8.1 [Version 6.3.10166]
TCC Build 27 Windows 8.1 Build 10166
Registered to Federico Romano

Microsoft Windows [Version 10.0.10166]

[C:\Program Files\JPSoft\TCMD18_x64]

 

[Charles Dye]

Not surprised; the code to detect Windows 10 and display an appropriate string ain't there until Rex writes it.

 

[fromano]

Not surprised; the code to detect Windows 10 and display an appropriate string ain't there until Rex writes it.

https://jpsoft.com/forums/threads/windows-10-support.6766/#post-39052

 

[rconn]

running TCMD x64 on Windows 10

[C:\Program Files\JPSoft\TCMD18_x64]ver /r & cmd /cver

TCC 18.00.27 x64 Windows 8.1 [Version 6.3.10166]
TCC Build 27 Windows 8.1 Build 10166
Registered to Federico Romano

Microsoft Windows [Version 10.0.10166]

[C:\Program Files\JPSoft\TCMD18_x64]

Microsoft bug -- they broke the API in the recent Windows 10 builds. Not sure if this was deliberate, or if there's a workaround. (Microsoft introduced new version APIs in Windows 8, but they hadn't broken the older ones until now.)

 

[Charles Dye]

https://jpsoft.com/forums/threads/windows-10-support.6766/#post-39052

Ah. I hadn't realized that that had ever worked; sorry.

 

[RogerB]

I've just taken advantage of the free upgrade to Windows 10 Pro which seems to have developed a split personality when I use ver /r

TCC  18.00.29 x64   Windows 10 [Version 6.3.10240]
TCC Build 29   Windows 8.1 Build 10240