This unexpected behavior has been addressed in a program update available May 6, 2021.
View solution in original post
