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