I’m using the same computer.
Edition Windows 11 Home
Version 22H2
Installed on 10/13/2022
OS build 22621.963
Experience Windows Feature Experience Pack 1000.22638.1000.0
As a test right now using a different mission, if I use the Missions Export as KML 3D Path option, the download text file altitude values are correct and looks right in Google Earth Pro …
<name>Start Point</name>
<styleUrl>#startpin-style</styleUrl>
<Point>
<altitudeMode>absolute</altitudeMode>
<gx:drawOrder>1</gx:drawOrder>
<coordinates>-93.1240527313689,45.16872624820793,278.54803705215454</coordinates>
</Point>
But if I Extract as VLM the altitude is not correct in the download text file and therefore does not look right in Google Earth Pro …
<gx:FlyTo>
<gx:duration>0</gx:duration>
<gx:flyToMode>smooth</gx:flyToMode>
<Camera>
<latitude>45.16872624820793</latitude>
<longitude>-93.1240527313689</longitude>
<altitude>3.0480369592503744</altitude>
<heading>135.0</heading>
<tilt>90.0</tilt>
<roll>0</roll>
<altitudeMode>absolute</altitudeMode>
<gx:horizFov>48.808874951732385</gx:horizFov>
</Camera>
</gx:FlyTo>