Wrong windows platform in About window

[Chris Elliott]

My systems are Windows 10. Specifically, my home system is "Edition: Windows 10 Pro; Version 1803; OS build 17134.112" and my work system is "Edition: Windows 10 Enterprise; Version 1709; OS Build 16299.492. Both systems report Windows 8 (build 9200) in the platform field in the About window and the version info. Here is the version info from my home computer, same as what I get on my work computer.

Application: kicad
Version: (5.0.0-rc3-dev), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

A discussion on kicad.info seems to indicate this might be a bug in wxWidgets. See https://forum.kicad.info/t/wrong-windows-platform-in-about-window/11400/3

[Nick Østergaard (nickoe)]

This becuase that is how windows works. For newer window's a so called manifest file is needed.

As mentioned in the wx API doc, it links to:
https://docs.microsoft.com/en-us/windows/desktop/SysInfo/operating-system-version

Which states:
* For applications that have been manifested for Windows 8.1 or Windows 10. Applications not manifested for Windows 8.1 or Windows 10 will return the Windows 8 OS version value (6.2). To manifest your applications for Windows 8.1 or Windows 10, refer to Targeting your application for Windows.

I don't really know how to do this with exe's not build with msvc.

[Simon Richter (sjr)]

wxWidgets have added code to get the "real" Windows version, which is also backported to the 3.0 branch, so it will be resolved when a fixed wx is released and we upgrade to it.

[Michael Kavanagh (michaelkavanagh)]

Closing this as it's a bug in wxWidgets.