Suggestion: The OS version might be a good info to show. In case of Windows, this should be the output of WINVER, like "Windows 10 Version 1903 (OS Build 18362.720)" or some form of it to show the version/build numbers 6.2.1903.18362.720, instead of the generic 6.2 I see in the cached log; this might be impossible if FAH is not collecting this info on the host down to the build number.
Response: I'm bound to the OS version reported by the FAHClient. So perhaps better detection is something I can push on their developer. I agree. It would be better to have the actual version rather than 6.2. I'm somewhat familiar with how/why that is returned in certain cases by Windows. Don't know why microsoft decided to go down that road, but I'm sure they have their reasons.
From our Google Groups thread: https://groups.google.com/d/msg/hfm-net/u_aJBM3DayI/ivBfzFWAAQAJ
Suggestion: The OS version might be a good info to show. In case of Windows, this should be the output of WINVER, like "Windows 10 Version 1903 (OS Build 18362.720)" or some form of it to show the version/build numbers 6.2.1903.18362.720, instead of the generic 6.2 I see in the cached log; this might be impossible if FAH is not collecting this info on the host down to the build number.
Response: I'm bound to the OS version reported by the FAHClient. So perhaps better detection is something I can push on their developer. I agree. It would be better to have the actual version rather than 6.2. I'm somewhat familiar with how/why that is returned in certain cases by Windows. Don't know why microsoft decided to go down that road, but I'm sure they have their reasons.