It looks like this issue should be corrected in the upcoming SP3 release for 2018.    VB-147433