We have experienced the issue that the D365 version is never updated in LCS after updating to a newer version from within the machine (as the update failed through LCS), the version never gets displayed correctly from LCS. This was handled in case 119100221000812 and the only suggested option was to re-apply the same version update through LCS in order to get the display correct.
As there is a "Lifecycle Services Diagnostics Service" running on the machine, it should be quite easy to make this service aware of the version and update it in LCS.