Looks like another user had exactly the same issue back in 2018.
@hobbymaster001 did you ever find a fix for this problem?