This issue was corrected in an update made available the night of February 20,2019. Please run updates to get the latest version.
View solution in original post
