This issue is fixed in an update available today, February 27, 2019. Please run program updates for the current version.
